I am, somewhat regrettably, not a professional Rust programmer - I mostly do a mix of c++ and Python in my day job. And at this point in my career I doubt I will accumulate the necessary artisanal programming experience for a truly competent Rust developer (I do masquerade as one occasionally behind an agent).
However, I encounter a fair share of devs with some Rust experience, mostly when they contribute to C++ codebases. And so far my experience of such interactions have been overwhelmingly positive. They consistently produce code that passes a quality bar way above their experience would otherwise suggest. Why is that?
My sense is that Rust enforces a certain kind of mindset on the programmer. Namely, to be explicit about “effects” like unsafeness and thread safety, to favor local reasoning, to be precise in expressing concepts (no overloads), to make code unsurprising to users. Additionally, Rust has a great ecosystem of crates with excellent design and a vibrant community, making Rust programmers generally more aware of the “goodies” the technical world has to offer, so to speak.
These are all good ways to cultivate taste in programming. Programmers from other language may need years of experience to arrive at the same inclinations. Large parts of Google’s style guides can be boiled down to “write boring but efficient code”. While Rust teaches these principles just from compiling user code and emitting warnings and errors.
So, if you haven’t learned Rust before, I encourage you to try, if only to see what’s out there.