Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Developing Trends: One Tool Doesn't Cut It: Page 2 of 3

Twisted Logic

I understand the perceived benefit of limiting the number of languages used in an IT organization. The consistency makes for more mobility between projects and reduces costs for application-development tools. But it also binds your hands and forces your developers into a rut. With a single language, it's easy to say, "We always do it this way--no ifs, ands or buts." It's also easy to say, "We can't buy that product; the programming API doesn't speak our language."

But that approach isn't in the best interest of the organization as a whole. As specialists in application development, it's our job to offer the best possible solutions to our clients' business needs. And as managers, it's our responsibility to be sure our staffs are equipped to follow through. We must give current employees the opportunity to learn and use additional skills, or we must hire new people with broader skill sets, or both. Anything less and we're putting our own jobs in jeopardy.

Given the growing number of platform and application options, attempting to use a single programming language for every development project is as productive as trying to use a Sawzall for every
carpentry job.

Don Macvittie is an applied technologist at WPS Resources. Write to him at [email protected].