3 ms·
Training internally makes a lot of sense, but it's also a huge hurdle and expense if your developers don't already have rust experience. What was the process o
by cjpearson 5y ago
Training internally makes a lot of sense, but it's also a huge hurdle and expense if your developers don't already have rust experience.
What was the process of proposing rust and getting buy-in like?
- cjg 5y agoWe initially used it on a small project that had the requirement that the chances of a crash / failure should be very low because it would be used as a remote control process for a wider system. We had good success there and so the company was keen to use it in more places. It's now formally "adopt" on our technology roadmap. We've actually bootstrapped relatively easily. We have a some developers who have picked it up quite easily, perhaps with some pairing. We run an hour session every week where all the Rust developers get together to share production code and present on Rust topics. The discussion focusing on Rust production code has been particularly helpful.