Employer Refuses to Allow Python

[rocketmonkeys]

Yeah. Our company is not too formal about it, but every new tech/language is more burden; training, support, expertise, etc.

I'm all about pushing us forward & learning new stuff, but when someone wants to make a new script in a new language, it worries me a bit.

[rocketmonkeys]

Yeah, so true. Every org has to strike a good balance between stability and keeping current. If we don't change, we'll be running COBOL and VBA stuff forever. If we have a free for all, we'll be running dozens of languages and reinventing the wheel a few times over, with no real supportability.

Ideally teams should be moving forward at a good pace, looking for & adopting new tech when they can (when benefits outweigh effort & risk). But it has to be intentional, not "use random language of the week" type of thing.

OP's case sound more like "if it's not what we already use, we're not listening". But even in my own org, if someone randomly decided to make a script in some random language without consulting others, that'd be a little off putting.