If you've been around these parts for a while you've probably heard the above reply to common feature requests. Many times these requests are at odds between several groups of users. So their typical solution to this impasse is the ever so simple, “Well, then just make it an option.” I'm sure there have been those who've scoffed at my response and put me in the “closed-minded-dolt” category ;-). Well it seems I may have gained a little vindication. Apparently “Joel on Software” seems to agree. One could certainly argue that development tools are targeted at a different level of user than Windows itself or your typical word processor or spreadsheet application. To that I say, why? Why do development tools have to have a million and one little options for this and that? We already have different and keybindings, tabs on, tabs off, auto indent on/off, code completion on/off, etc... There are a lot of end user reasons to limit the options as Joel so deftly does in a somewhat comical fashion to that faceless team of individuals working on the “start menu.”
However, there are also a lot of practical development side reasons to limit the choices as well. Many times, just the simple act of adding a single on/off boolean option actually can double your testing efforts! Ok, that was probably a bit of hyperbole, but it will double a portion of your testing effort. So now you have to test everything related to that option with it on and with it off. Add another option, and you're quadrupling the effort. Think binary here. In practice there are plenty of relatively safe testing “shortcuts” and ways to minimize that impact. My point here is that glibbly introducing an optional new feature because “those 5 people I talked with last week said it was a good idea,” is probably not the most responsible thing to do. Sure, for smaller applications targeting smaller markets, you do have to try and cater to as many as you can. However, I've seen many, many cases where a better and workable, non-optional solution to a problem (or more appropriately a class of problems) is born out of a whole aggregated class of similar problems.
So when you're asked to “just add this little new feature,” and are inclined to make it optional, just step back and consider whether or not there are other problems within this particular class. Is this new option worth the extra testing burden? Is the feature useful to a wider cross-section of your customer base, so maybe it shouldn't be optional but always enabled? Don't use the option as a “get out of jail free card.” Sure, if customer X says they just can't stand that feature and you can reply with a simple, “Just turn it off.” You sure dodged that bullet... or did you? What if there was some use-case that that customer brought to the table that you had not considered? Adding an option should not be used as an excuse to not have to thoroughly think through a problem. Consciously or not, many times that is what is happening.
So for now, I'll still hold that “Optionitis can kill if left untreated.” Now... at some point we still have to add that error message, “Programmer expected...”