This past week, while discussing our core web application at work, another programmer and I were complaining about how every time we added a new feature (nearly always at the request of one of the departments) some other department would then complain about it and want the opposite. If we build a form to insert things, we have to build one to delete things (well, appear to be deleted, we never really delete anything). If we build an option to start a process, we have to build an option to re-start the process. That sort of deal.
Well, in talking about this phenomenon I blurted out, “It’s like for every feature we have to have the antifeature.” My partner in programming like it and for the last few days we’ve been using it quite a bit. We’ve already had a few more requests for antifeatures since then and now we use the term when planning new features, like: ‘That’s great, engineering will love it. But where’s the antifeature, you know design will want it?”
You know, building web apps would be much easier if it wasn’t for those darn ‘end users’ 
