2009-08-17

Tool or toolsmith?

I am really tired of poorly designed software development tools.

The primary reason for creating a tool is to solve a problem. Or a set of problems. Or make some problem domain half way bearable. If at all possible without creating new problems. Or failing that, at least without creating new problems that are more severe than the problems the tools claim to solve.

Having spent more time than I care to contemplate trying to make poorly made developer tools work, I am considering becoming consistently unpleasant to annoyingly incompetent toolsmiths whenever the opportunity presents itself.

The same goes for authors of books on relatively generic technologies who first promise to focus on the matter at hand and not favor any particular implementation of said technology, and then proceed to prattle on about some useless toolset that they happen to like and which renders the book half useless unless you adopt their particular flavor of crazy.

There are some times when an idiot is just an idiot, and one would be doing society a favor by pointing this out vigorously and with enough blunt verbal force to deflect the trajectory of their career to a more suitable one. Possibly one in carbonizing roadkill oozing with saturated fats in places where I am not likely to dine (the amount of negative karma generated remaining constant, but at least without inflicting their software on people who deserve better).

No comments:

Post a Comment