---
title: "Comment by Faisal Arshed on \"Learning Rust in 2023: A Call For Discussion\" | Hashnode"
description: "I started learning it it last year. Here's my approach: Read and took my time understanding the first eight or nine chapters of The Book. This took me aroun"
url: "https://hashnode.com/posts/learning-rust-in-2023-a-call-for-discussion/63af6447a56a4023c181bd02/comment/63fc1b8542967b0d40d37c0f"
---

[Discussion](https://hashnode.com/posts/learning-rust-in-2023-a-call-for-discussion/63af6447a56a4023c181bd02)

Comment [Learning Rust in 2023: A Call For Discussion](https://hashnode.com/posts/learning-rust-in-2023-a-call-for-discussion/63af6447a56a4023c181bd02)

[Faisal Arshed](https://hashnode.com/@farshed)

[Feb 27, 2023](https://hashnode.com/posts/learning-rust-in-2023-a-call-for-discussion/63af6447a56a4023c181bd02/comment/63fc1b8542967b0d40d37c0f)

I started learning it it last year. Here's my approach:

-   Read and took my time understanding the first eight or nine chapters of The Book. This took me around two weeks
    
-   I thought that gave me good enough foundation to begin a project so I started building one
    
-   I worked on the project for about six months. During that time, I revisited The Book multiple times to learn about different parts of Rust as I needed them. I also generously employed other resources like blogs and studying code from other Rust projects.
    
-   I'd say it took me about two months to feel productive working with it but way longer to feel confident about the code that I was writing. Actually no, I'm still not confident that my code looks anything like idiomatic Rust. Anyhow, I love Rust and it's now usually my first choice when considering a personal project.
    

TL;DR: Building projects and picking up things along the way as the project grows in complexity works best for me.