Live data from Hacker News

Rust Learning Path from Novice to Mastery

nativebyx.dev

1–10 of 26 posts

Re: Rust Learning Path from Novice to Mastery

#5

I love how culty the Rust sphere is. I don't have many opportunities to use it but I always stop to watch tutorials/read articles because of how enthusiastic people are about the language

I am still trying to figure out how to jump on that bandwagon. I used to be a C++ super geek but lately it’s mostly C# and Python. They are way more practical and productive but for some reason I like complex languages.

Re: Rust Learning Path from Novice to Mastery

#7
post #6

At what point would you suggest switching from tutorials to building a toy project? Finding it hard to judge. Sooner seems better but at risk of missing major understanding pieces which could end up being slower in total

Not OP but imho as soon as possible; whatever major understanding pieces you are lacking you will have to learn while making the project.

There are also language concepts that will not make much sense when learning without context from a book, but will make much more sense after attempting to write something without using that first.

Re: Rust Learning Path from Novice to Mastery

#9

I love how culty the Rust sphere is. I don't have many opportunities to use it but I always stop to watch tutorials/read articles because of how enthusiastic people are about the language

To quote Maria Bamford, "Sure I'll join your cult!"

The world needs languages that try to be both safe and high performance. Rust is taking a shot at it. I'm not actually using it myself, but when I see people getting excited about it, I'm not laughing at them. I'm thinking that I get where they're coming from.

Re: Rust Learning Path from Novice to Mastery

#10
I keep seeing "how to learn X" and a series of tutorials, exercises, or courses. Maybe it's me, but each time I learned something, it was by doing projects. Usually, starting with modifying someone's code (while seeing a language for the first time) and then reading a tutorial to understand what's going on.

It gave two things - a context of an actual project (especially as usually ecosystem is more important, and tricky, than the language itself) and motivation. Otherwise, I either stop learning (which often is a good thing because it turns out I don't need this language or tech) or don't internalize the most important things.

Post reply on HN