Architectural mood swings

We all did it: adding a parameter like “bool useCachedConnection” to a method. When using the method it will look like this:


C#:

1	DoSomething(true);

While the method works, one day your collegue (or yourself) will come across this function and needs to digg into the definition to understand what the boolean implies, or worse, needs to adjust the method interface due to the fact that there are three options, instead of using or not using the cached connections. I’ve seen it several times and it saves a hell of a lot time if boolean parameters were to be avoided. A better way to do it:


C#:

1 2 3 4 5 6 7 8 9 10 11 12

enum ConnectionOptions {     CachedConnection,     NewConnection } void DoSomething(ConnectionOptions options) {     // } DoSomething(ConnectionOptions.CachedConnection);

Now it’s possible to add options without having to change the methods’ interface. After a while you’ll have a nice collection of enums which can be reused by other projects. And don’t forget that the .NET Framework holds his own collection of enums which can be reused. When working with languages like T-SQL you don’t have a choice, but with .NET you have. Please make use of it. It’ll brighten up my day….. and yours. ;-)