This is great advice. Because while the Rust book is good, certainly can't fault it, I hate reading about programming languages. It doesn't work for me. If it does for you, great.
If not, then just write Rust. Remember: no matter how bad or non-idiomatic the code you write, it's still better than not doing it.
If you don't have a project you'd like to do, you can port something to Rust. I think a thousand lines is terrific advice. Writing Rust really helped me solidly remember many "how do i do X in rust" things. Crib liberally from other codebases. Ripgrep is perfect for getting inspired with Rust idioms, such a good codebase (obviously don't port that :D).
I'm at 15k lines now. It gets better! You'll learn to appreciate cargo and the build system. It just works. No more makefiles, pom.xml, requirements.txt. Rust-analyzer is great for IDE hints in a lot of IDEs, but easiest to set up in VSCode. If you end up shipping a CLI program/giving it to friends, you'll appreciate zero-dependency binaries (well, except some libc dep).
If all those things don't matter to you, then re-evaluate. Programming languages are a tool; nothing more and nothing less. What are you trying to achieve? Honestly, you might be better off spending your time on focussing on your career, no matter what the language. You don't say why you want to learn Rust, so I'm not going to guess. But you don't need to know Rust to be a good programmer. Rust will be there in a few years, too.
If not, then just write Rust. Remember: no matter how bad or non-idiomatic the code you write, it's still better than not doing it.
If you don't have a project you'd like to do, you can port something to Rust. I think a thousand lines is terrific advice. Writing Rust really helped me solidly remember many "how do i do X in rust" things. Crib liberally from other codebases. Ripgrep is perfect for getting inspired with Rust idioms, such a good codebase (obviously don't port that :D).
I'm at 15k lines now. It gets better! You'll learn to appreciate cargo and the build system. It just works. No more makefiles, pom.xml, requirements.txt. Rust-analyzer is great for IDE hints in a lot of IDEs, but easiest to set up in VSCode. If you end up shipping a CLI program/giving it to friends, you'll appreciate zero-dependency binaries (well, except some libc dep).
If all those things don't matter to you, then re-evaluate. Programming languages are a tool; nothing more and nothing less. What are you trying to achieve? Honestly, you might be better off spending your time on focussing on your career, no matter what the language. You don't say why you want to learn Rust, so I'm not going to guess. But you don't need to know Rust to be a good programmer. Rust will be there in a few years, too.