rather different to my
While they should get wider buy-in first then if the choice is technically justified within reason, its perfectly appropriate
> No competent dev will accept their skills atrophying due to overly rigid political/tech choices.
Competent dev to me is one that delivers value. I say that as a dev but I'm pretty sure stakeholders would agree.
It's perfectly reasonable to hone your skills outside of paying hours if you chose to expand to new technology outside of your employer's stack.
I would probably concede that it depends on context - for devs paid at the top of the market to simply churn stuff out factory-style there is less justification for self-improvement on work time.
For the majority though there is always give and take between responsible employees and employers, and building skills as discussed is normal.
If anything, companies expecting employees to know their specific tech stack on day 1 of the job is much less common an expectation outside of Software engineering.
And I say that as an employee.
There's some flexibility to choose tooling but with autonomy comes responsibility.
Replacing a bunch of working Python scripts with Rust is not just irresponsible, it's disrespectful and isolating towards coworkers.