[maximente]

nah, this is just the brilliant hacker type mentality (individual over team, parachute in and rewrite everything in today's cool language) type stuff that gets really annoying once you're responsible for a set of interconnected components of software that matter.

it's critical to root out these hero types lest they ruin your organization with hand grenades wrapped up as "refactored" projects using the latest language. seniors won't put up with this, and rightfully so: it basically raises a middle finger to the organization's previous culture/work, and they are now responsible for doing it... again. it's disrepectful and ought to be a fireable offense, ideally rooted out in the first few weeks when the new team member is given some slightly autonomous tasks.

[ngz00]

It seems to me that the real problem is hiring engineers who only know one language and rest on that language choice for their entire career. If you build an organization of engineers with a versatile set of skills then there is no such thing as a wrong language choice.

Mandate the standardization of interfaces rather than languages and you empower all types of developers in your organization.

[ubu7737]

This is ridiculous language. The horrible stink of authoritarianism in this thread!

Good thing for you, that excellent software is always written at the bark of a sadly decomposing mind. You're making wherever great again, I suppose.