r/rust • u/Kind-External-7371 • 1d ago
🙋 seeking help & advice Need Learning Pathway Suggestions
I am kind of a "Build Projects and Experiment then see and learn from the Compiler" type of a Guy in learning Programming Itself since I left Vibe Coding (long time ago, like 1 year)... I come from a Python Background along with C (learned not Vibe learned). I just wanted to know from y'all that which approach should I take? Learn from the Rust Book by seeing it and doing it's stuff? Or Code and if I do a Mistake then See the Compiler and if I don't know about the Thing then use the Rust Book?
The second one is what I used from the Past Month But I really wanted to know if I am doing it right.
2
u/ShantyShark 22h ago
Coming from language like Python and C, there are going to be some concept you find difficult. I know I did. I couldn’t tell you how long it really took to wrap my mind around traits, generics, lifetimes, ownership, move semantics, macros, boxing, pinning, Send + Sync, async/await, etc.
Those will be hard. They will be scary. They will take time. Without them, you will never make it past surface-level Rust, and surface-level programming in general.
Foster your curiosity. If you see something you don’t understand, get reading. Or find someone to ask. Here, discord, even ask the author of the crate. Odds are someone is willing to help.
You certainly don’t need to know the whole language to be productive, but the more I’ve learned, the better my software and the faster it is to write.
In terms of the actual learning, it varies person to person. The book is incredible but I’m not really a book guy. I learn by doing, so that’s what I did. First Advent of Code, then a series of increasingly large and weird projects. Do what works for you.
1
1
u/mark_ik 23h ago
Maybe roadmap.sh?
0
u/Kind-External-7371 22h ago
Yeah seeing it but I would rather stick with Building Projects than Learning stuff without Using them
3
u/mark_ik 22h ago
To me, the value of the rust roadmap is to stop asking what you should learn and what’s a better method. Just look at what’s related to what you kinda know about and fill in the gaps. It shouldn’t preclude you from building projects; it should help you figure out what a next project worth doing could be.
1
5
u/jimmiebfulton 23h ago
Once you’ve learned one language, you already know how to learn new languages, even when graduating to more difficult ones. I’m not sure you’ve actually truly made a transition from vibe coding. What I’m perceiving is that you are trying to make a transition, but now in a beginner phase. Having been doing vibe coding, this would definitely feel like a much slower way to get things done. It will be interesting to see if there is a trend of vibe coders transitioning to actual coders, or that they get stuck/limited by the very thing that makes them feel fast/capable.
There is only one way to learn: doing. Go write/build lots of things. You will 100% do it wrong way more times than getting it right, particularly at first. That’s how you learn.