Opinion: Goals should shape tool choice, not the other way around.

As several thousand developers head for Orlando to attend this week's IBM Rational Software Development Conference, I'm trying to get used to the idea of an IBM Web site using a turn of phrase like "cranking the volume up to 11, so you can hear what's shaking." It's hard to believe that this is the company that used to promise us things like "a conceptual model that describes software structure in a generic way and provides a coherent organization of function." I'm not entirely sure that the company's new groove is an improvement.

On the other hand, IBM is probably entitled to express itself to developers in whatever way it prefers: Despite the high profile of Microsoft among mass-market software developers, IBM claims to have led the tools market in revenue for five straight years, with Microsoft in second place at half of IBM's tool revenues.

Of course, Microsoft may not judge its success in tools by how much money those tools bring in, but rather by their success in attracting talent to the Microsoft platform. I once asked Microsoft research manager and genuine development guru Jim Gray if Microsoft's tools were expected to generate the same kind of margins as other Microsoft products, or if the tools group was merely expected to cover its overhead while serving strategic developer engagement goals. "That's a good question," he replied, but that's as far as his answer went.

I vented in a recent blog post on the subject of whether taxpayer-funded software development should make a point of using only standards-based tools for nonproprietary platforms: This led to some dialogue among our blog's readers on whether I was (i) taking a cheap shot at a government agency that had made a rational choice of a productive tool set or (ii) accurately identifying the political nature of the process by which tools are chosen. I'll admit that I'm of two minds myself. Ideologically, I want to see school kids with Macs or Linux boxes being just as able to use a NASA-developed learning application as students in Windows-equipped classrooms. Practically, and as I acknowledged on the 20th anniversary of Windows late last year, I've seen technical tasks dramatically aided by the availability of useful and free applications that might never have been written without the leverage of inexpensive tools for a ubiquitous desktop client.

To argue against myself, though, I've also taken a good hard look at how the world of end-user computing might have evolved if Windows had been less effectively marketed, and if broadly licensed standards from many vendors or open standards created by the community had instead become the definers of how we develop and deliver. I believe it's possible, and smart, to choose development tools and practices that reflect the common subset of technology that's available to almost every user: a "subset" that is today an enormous superset of what we once thought was pretty darn good.

Tell me how you make these choices at peter_coffee@ziffdavis.com.

Click here for an archive of Peter Coffee's columns.

This article was originally published on eWEEK.com.

Discuss Is Developers' Tool Choice Rational(ized)?   >>> Be the FIRST to comment on this article!

>>> More Add Ons Articles          >>> More By Peter Coffee