3 ms·
The only reason these tools were written in Rust was because the dev wanted to learn Rust (a big but common mistake). While they should get wider buy-in first
by mellosouls 2y ago
The only reason these tools were written in Rust was because the dev wanted to learn Rust (a big but common mistake).
While they should get wider buy-in first then if the choice is technically justified within reason, its perfectly appropriate (and normal) for devs to pick up new languages in this way when existing expertise is not available on staff. No competent dev will accept their skills atrophying due to overly rigid political/tech choices.
That's how skills are built, its always been thus in such environments, and thats ok.
- hu3 2y agoSorry but employees are not entitled to get paid to learn whatever technology they want during work. 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.
- givemeethekeys 2y agoNo one has the "right", as you put it. The learning of and using Rust was approved by the employee's superiors. 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.
- mellosouls 2y agoSorry but employees are not entitled to get paid to learn whatever technology they want during work, in their own special ivory towers. rather different to my While they should get wider buy-in first then if the choice is technically justified within reason, its perfectly appropriate
- hu3 2y agoMy point is about this: > 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.
- mellosouls 2y agoFairer, but that's probably the point and tone you should have quoted with then. ;) 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.
- deleted 2y ago[deleted]
- whatshisface 2y agoYou're not likely to be paid top of the market at a firm whose biggest concern is that you might be more flexible and a faster learner than anyone else they were able to hire.
- deleted 2y ago[deleted]