Rust Learning Path from Novice to Mastery
11–20 of 26 posts
Re: Rust Learning Path from Novice to Mastery
#12I 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
True. But nowadays, zig is the new rust!
Re: Rust Learning Path from Novice to Mastery
#13I 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
The only avenue that it has yet to penetrate is gaming. No other language has achieved this yet, and rust is the closest.
Re: Rust Learning Path from Novice to Mastery
#14I 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 tri…
Re: Rust Learning Path from Novice to Mastery
#15I 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 tri…
Coming from a C++ background, learning Python required a trial-and-error process similar to what you've described. However, learning Groovy while knowing Python and Java took only a single pass through the Groovy docs - just to figure out what exact elements of Python and Java has Groovy incorporated in what way.
In context of tutorials, a lot of people write them "for themselves" without realizing it - there's just too much implicit knowledge assumed. And it's hard work to expand on all of it, without going down the rabbit hole and ending up explaining the concept of Turing Machines.
Re: Rust Learning Path from Novice to Mastery
#16At 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
Rust is sufficiently complex that you have to do projects to encounter every nook and cranny of even the core language. Other language like python expertise in the language often involves knowing the libraries.
Re: Rust Learning Path from Novice to Mastery
#17Not to hijack the thread, but does anyone have links to similarly opinionated book lists for other languages? Like Python, C, or golang.
Re: Rust Learning Path from Novice to Mastery
#18Not to hijack the thread, but does anyone have links to similarly opinionated book lists for other languages? Like Python, C, or golang.
Re: Rust Learning Path from Novice to Mastery
#19I 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 tri…
That's exactly what "Zero To Production" is about. Actually most of what makes Rust intro material good is that you are building things, not just going on about syntax and language particulars.
For example, "The Book" (what we call "The Rust Programming Language") ends with building a multi-threaded web-server.
Re: Rust Learning Path from Novice to Mastery
#20Earlier quoted context omitted.
True. But nowadays, zig is the new rust!
As I am completely and unapologetically biased, Zig hits me the wrong way when in it's default help output it mentions "exe" and "dll". barf.