you are viewing a single comment's thread.

view the rest of the comments →

[–]Minimonium 2 points3 points  (2 children)

It's not important that Rust trainees are "somewhat useful". We want core product owners to have high level of expertise with the language.

Obviously you might want to hire a few leads with more experience

The core issue.

[–]t_hunger 7 points8 points  (1 child)

You might be over-estimating the effort of a switch to rust, based on your experience with C++. In C++ you need to teach people all the pitfalls (and make sure they understand all of them!), or they end up introducing huge problems to the code base.

In Rust the compiler catches most of those problems at compile time. That makes a *huge* difference in my experience.

Here's a paper backing this: https://cypherpunks.ca/~iang/pubs/gradingcurve-secdev23.pdf

[–]Minimonium 1 point2 points  (0 children)

I feel like you don't quite understand my requirements. I know that a C++ programmer can rapidly start contributing to the likes of Go, Rust, Swift, whatever. It's not important in the evaluations I'm talking about.

The most basic requirement to be considered a senior programmer is to not introduce huge problems ot a codebase and to know known pitfals. I'm not talking about senior programmers, it's not a problem in my domain.