When the only tool you have is a hammer...

Posted by Nicholas Blumhardt | May 26, 2007 20:19

Platform and language monoculture is a big issue in established software companies today. Perhaps a lack of it is one of the defining factors identifying the new ‘agile’ development outfits that have popped up so far this decade.

The Java- and Microsoft-only shops are the best examples - companies that are willing, through principles of economy, to put all of their eggs in the one technological basket.

I recently overheard: “we can’t adopt application X because that would require training someone in Java.” Perhaps that is the reason that training is so often only given lip service and is considered to be of little real value? Training in a new facet of a platform you already know doesn’t really take you anywhere new. Significant insights most often come to me when I step back from my own work and see how other people are tackling the same problems.

Familiarity with multiple platforms and tools can give you a lead over the competition. NUnit, CruiseControl.NET and NHibernate have been being used effectively for quite a while now, by the .NET developers who looked over the fence and saw the advantages being enjoyed in Java-land. Microsoft have finally come to the party with Team Foundation Server and Linq to Entities - but now the competitive advantage is gone and a new set of not-so-secret weapons is needed to stay ahead.

The rationale for keeping the set of technologies in use in any one development team small is a sound one, but I think that taking this wisdom without a healthy grain of salt can lead to mediocre systems built using sub-optimal tools.

Disclaimer: These articles represent the opinions of the authors and may not match the official position of Ubik Systems Pty. Ltd. Confirmation should be sought on all matters involving professional advice.