Geeks With Blogs
Chris Falter .NET Design and Best Practices February 2008 Entries
Make Magic Strings Easy to Understand and Type Safe
As organizations pass data back and forth, they often use codes to represent the data. For example, a marital status of divorced might be represented as "D", married as "M", and so forth. You have to solve three problems when you are dealing with magic strings: When you write logic to handle the data, things can get chaotic on a hurry if you are not careful; the use of literal magic strings in your source code can make it incomprehensible. You can get into trouble by passing a string that is not ......

Posted On Wednesday, February 27, 2008 1:40 AM

"New" Statement Considered Harmful

Just by calling a class' constructor, you are tying your code to some implementation details of the class. Since good software uses loose coupling, though, you should develop the habit of providing a static construction method and hiding a class constructor. There are exceptions that prove the rule, however, as noted both in this article and in the comments. Read on to learn how to develop the good habit, and when you should consider breaking it....

Posted On Friday, February 15, 2008 2:59 PM

Agile Software Development: A "Value-Up" Approach

Sam Guckenheimer, the group product planner for Microsoft's Visual Studio Team System, has written an excellent book entitled "Software Engineering with Microsoft Visual Studio Team System." The first chapter compares and contrasts Agile methods with the traditional Software Development Lifecycle (SDLC, or waterfall) approach. In this little essay, I summarize Guckenheimer's findings, and sprinkle in some thoughts about how our organization might consider using Agile methods.

Posted On Wednesday, February 13, 2008 3:22 PM

Why You Should Consider Using FIT

Have you ever had difficulty translating a set of requirements into a set of tests? Do you find regression testing to be a major bottleneck whenever you implement changes in your system? (Or do you have quality issues because you forgo regression testing?) Does your development team ever dump complex functionality into a "smart UI" that becomes difficult to maintain and extend? If you answered yes to any of these questions, you should check out FIT (the Framework for Integrated Testing).

Posted On Tuesday, February 5, 2008 4:12 PM

Copyright © Chris Falter | Powered by: