There was a time when all you had to learn was Java or C++ or (language or tool here). Somehow, this time when we standardize, it will be different.
= be usable, and
= provide a set of data structures that an educated programmer *expects to find when scripting*.
Python literally sucked less than the alternatives.Can you say the same about your solution?
WTF? Unless your system is originally written in a proprietary language that literally no one outside your company knows, I'll say it's a good sign that you need to change team (or change job). Don't work under a director like that.
Better luck with the next one!
I've probed several times, and the most senior SWEs have no reason for this choice other than some personal issue with anything new, which to me sounds like a job security thing. Over time, they've resisted other new tooling to the point where management has ended up forcing things, but they're still holding onto C++. Some lower-grade, lower-ego engineers armed with higher-level tools would replace everything in a more maintainable way for a lot less money.
This week our Director ordered a total rewrite of two years of work in Python. His rationale: it's what everyone else uses in this space. No reason specific to our use case, just simply to follow the herd. I realise that a large community translates into easy hiring and rich ecosystems, but I despise the mentality as it promotes a monoculture.