Yeah regardless of time taken the study plan for Rust already exists (https://doc.rust-lang.org/book/). You don't need ChatGPT to regurgitate it to you.
The book is great but its not really helpful for teaching.
To get to a reasonably proficient level in rust I did the following.
1. Use the book as the reference.
2. Angela Yu's 100 days of python has a 100 projects to help you learn python (highly recommended if you want to learn python). Tried creating those projects from scratch in Rust.
3. I'd use the book as a reference, then chatGPT to explain more details why my code is not working, or which is the best approach.
The key points that helped me, besides correlating sections to the corresponding chapters in the book, are the proposal of certain exercises every week to cover the topics we've seen and the encouragement to write small articles around the lessons.
I've already completed the Rustlings independently before this but it left me kind of lopsided and wanted to make this knowledge as full as possible.
I would say you have to be familiar with a large part of the standard library, de facto standard crates, and most language features, plus have the experience to write code and deal with compiler errors effectively. No way anyone is doing that in a couple of weeks by reading one book. At least for Rust.
Maybe for something a lot simpler like Go it's plausible, but even then I doubt it. You're not going to know about any of the common gotchas for example.
Yeah regardless of time taken the study plan for Rust already exists (https://doc.rust-lang.org/book/). You don't need ChatGPT to regurgitate it to you.
The book is great but its not really helpful for teaching.
To get to a reasonably proficient level in rust I did the following.
1. Use the book as the reference.
2. Angela Yu's 100 days of python has a 100 projects to help you learn python (highly recommended if you want to learn python). Tried creating those projects from scratch in Rust.
3. I'd use the book as a reference, then chatGPT to explain more details why my code is not working, or which is the best approach.
The key points that helped me, besides correlating sections to the corresponding chapters in the book, are the proposal of certain exercises every week to cover the topics we've seen and the encouragement to write small articles around the lessons. I've already completed the Rustlings independently before this but it left me kind of lopsided and wanted to make this knowledge as full as possible.
But I agree though, I am getting insane value out of LLMs.
Doubtful. Unless you have very low standards of "learn".
What are your standards of learn?
I would say you have to be familiar with a large part of the standard library, de facto standard crates, and most language features, plus have the experience to write code and deal with compiler errors effectively. No way anyone is doing that in a couple of weeks by reading one book. At least for Rust.
Maybe for something a lot simpler like Go it's plausible, but even then I doubt it. You're not going to know about any of the common gotchas for example.