4 ms·
God I feel like I’m taking crazy pills when I read these threads. Can I hire 1000 Rust devs at the drop of a hat off the street? Well, no. Have I ever struggle
by FridgeSeal 2y ago
God I feel like I’m taking crazy pills when I read these threads.
Can I hire 1000 Rust devs at the drop of a hat off the street? Well, no. Have I ever struggled to find competent Rust devs, or high level people who were happy to learn? Nope.
I would absolutely not be afraid to use it because of “hiring concerns”. If your current devs can’t or won’t learn anything new, they’re not very good at their job. If you can’t or won’t hire because you can’t find a super-senior at the drop of a hat, well, your hiring process is broken and no language will really help there.
- sfn42 2y agoI work in a team where we use C# for our backends and React/TS for our frontends. And of course a lot of other stuff, like Docker, Terraform, Azure etc. I would very strongly encourage anyone who suggested introducing different tools in our project, not to do that. Not because I don't enjoy learning, but because it's a waste of time. I don't need to learn Rust, C# works fine. I don't need to learn Vue, React works fine. I don't see any value in learning yet another tool to do the same job, I'd much rather spend my time getting actual work done and getting better at using the tools we're already using.
- jcgrillo 2y agoThe underlying (absurd) assumption is that the sum total potential of a developer you hire to do a job is statically determined by their past experience at interview time. This is the problem with "Human Resources" thinking, it fails to account for all the, well, human stuff. Case in point from the article: > it is not viable (for us) to retrain a C developer to Rust What? Why the hell not?