Anticlue

Bringing clarity to the which language to use decision

I've got to say a large thank you to Sean for pointing out the TIOBE Programming Index. Determining which tool to use for future development, without cutting oneself on the bleeding edge is not an easy task. Especially, since I'm among the risk adverse managerial club.

I think the problem is larger than just choosing a single language to do-it all. My view is that there are certain languages which excel for a certain task at hand. The trick to the mix is choosing the right tool that will help to provide the best technical solution to the business problem at hand. I've been of the opinion for a while that it isn't a good practice to restrict a shop to a language, just because everyone else needs to know it. If you want to bring a tool or technology in house, show others how to utlize it and its benefits to certain situations. Also analyze it across the business. Having flash forms is really nice, but is it worth having to have an individual update locked down workstations for the next six months?

One just really needs to have a good set of the basics in play for any business solution..

People working as a team.
A standardized source control mechanism is a must. The key here is ensuring everyone understands it.
A specification or set of requirements is needed next.
A centralized issues database is a pretty much must have.
Happy programmers and application analyst with the desire to learn new skills.
A reusable testing plan with lessons learned from all previous tests.
Tester comprising the people who will use the application, system, and/or tool.

After that the technology, which is alway changing, isn't about choosing only one. It become about using the best tool to get the job at hand completed.