For the last couple of year’s I’ve had a weird relationship with Rust. I’ve always wanted to learn it; not because Go or Python have been bad for me or I’ve hit some insurmountable walls there but simply because I’m curious about the language, its eco-system, and in what ways it might influence my problem-solving approaches. It certainly also helps that the community from the outside gives me the same vibes as the Python community 😅
The one thing that always kills me, though, is on the technical side: Whenever I have to deal with lifetimes annotations I somehow loose it. I simply haven’t reached the point where that and the rest of the language clicks with me. But that doesn’t keep me from trying! Last time I entered around Programming Rust by Jim Blandy and Jason Orendorff. This time I want to use the Rust track on Exercism in combination with VSCode. This way I will hopefully not waste too much time on configuring my editor and tooling around the language and be able to focus on coding.
So far, the Rust track had a nice learning curve and I didn’t have to deal with lifetimes too much 😅 Sadly, the mentors might be slightly understaffed but perhaps I’ll be able to help out once I’ve grown more comfortable with the language. I just hope I’ll make it this far this time around!
In the meantime, I’ve switched from mentor to practice mode. While getting high-quality code review is awesome, at first I want to stay motivated and therefore want to make my way as fast as possible from problem to problem. So… on to the next exercise 😀
Do you want to give me feedback about this article in private? Please send it to comments@zerokspot.com.
Alternatively, this website also supports Webmentions. If you write a post on a blog that supports this technique, I should get notified about your link 🙂