Publication Date: 3/15/2012 6:40:24 AM
One of my customers LOVES to ask for configuration options. Often when I ask “do you want that implemented as “a” or “b” he will reply “can you make it something we can change later?” It isn’t that he wants to make my job harder (although sometimes it feels that way.) The problem is that he understands their environment, and he knows change is likely.
But making everything “flexible” adds cost, not only in initial development, but also in testing and maintenance. It can even be dangerous. When options are infrequently used, it is easy to forget how they work. This can lead to unexpected settings that can break things.
A better approach is to be more thoughtful. Is this likely to change more than once? If so, then making it a configuration option makes sense. But if you are just trying to avoid a decision now, that is not a good reason to clutter up the configuration table.
Your URL (optional):
Type the code shown
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle is a talented expert in her field. She has blended well with our team and built applications that we are proud to deploy to our associates. Her talents helped us execute a vision expediently and with quality. If we could do it all over again, we wouldn’t change a thing.
Peter Edstrom @ Renewal by Andersen
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS