Probably an obvious question, but have you read the book? Even if you feel your experience with other languages should be enough to let you skip “beginner” cont

Probably an obvious question, but have you read the book? Even if you feel your experience with other languages should be enough to let you skip “beginner” content, I cannot recommend the book enough. Going through every chapter and doing the exercises should get you in a place where you can write rust relatively comfortably. From there I think Rust in Action is another good source of introductory material. I also don’t know what you’re using for your dev environment, but whatever it is, make sure you’re using the rust-analyzer language server. The excellent and immediate inline warnings and errors are immensely helpful, even now with several years of rust experience under my belt. I think it’s also really helpful to do a couple of small projects with limited scope, e.g. a single-threaded, literal match grep CLI, or `du` clone or whatever. As Klonoar pointed out, also don’t beat yourself up over writing “good” rust, at least not initially. Don’t worry about cloning and unwrapping, and throw stuff behind an Arc and/or Mutex whenever shared access or mutation gets hairy. Taking that route, Rust isn’t more difficult to write than any of the other languages you know, and it’s fine while you build familiarity. Also don’t hesitate to reach out on Rust’s zulip or discord, or the unofficial community on reddit. People tend to be very helpful.