> And, compounding the issue is the fact that those minding the programmers were and remain (in the best cases) mostly behind the curve -- they're in meetings all day, after all -- and are simply not in a position to authoritatively smack down "let's use X!" enthusiasms. (In the general case, they are entirely clueless.)
I don't think them smacking the "let's use x" is a good idea since it's the Devs who'll be writing the code.
The org needs a framework that answers:
1. How easy is it to train someone to use this stack? How long would it take for someone to start writing good code
2. How much time would it save us when building something new?
3. How easy is it for someone completely new to the codebase to start contributing?
I don't think them smacking the "let's use x" is a good idea since it's the Devs who'll be writing the code.
The org needs a framework that answers: 1. How easy is it to train someone to use this stack? How long would it take for someone to start writing good code 2. How much time would it save us when building something new? 3. How easy is it for someone completely new to the codebase to start contributing?
1 and 2 can be easily measured within the org
You can use OSS as a proxy for 3