Bob Belderbos3 things I wish I knew before learning Rust as a Python developer.
< Tip 1: Map, don't translate >
Don't ask "how do I write Python feature x in Rust?" Ask "what problem does Python feature x solve — and how does Rust solve it?"
• Error Handling: try/except -> Result<T, E> (errors must be handled)
• Logic & Data: class (inheritance) -> struct + impl (focus on composition, and data layout)
• Memory Management: GC -> Ownership & Borrowing (focus on who "owns" the data, enforced by the compiler)
• Logic & Data: class (inheritance) -> struct + impl (focus on composition, and data layout)
• Memory Management: GC -> Ownership & Borrowing (focus on who "owns" the data, enforced by the compiler)
< Tip 2: The compiler is your pair programmer >
Python tells you what broke at runtime (or dev if tooling is set up). Rust tells you what would break before you even run it (compile time).
Stop fighting the compiler. Read its error messages — they're the best in any language. It's teaching you something.
< Tip 3: Write Python first, then Rust-ify it >
When stuck, sketch the logic in Python. Then translate it step by step.
You already know how to think about the problem, which removes a lot of cognitive overload.
You just have to learn a new way to express it.
Don't get me wrong, the learning curve is real!
However Python devs have a head start — you already think in types, you already care about elegance + clean code.
Which tip would've helped you most? Or any other ones?
I'm building exercises that do exactly this — map Python patterns to Rust.
Free Python→Rust 10 intro exercises → rustplatform.com/via/bob
Feedback:
> "I like the Python to Rust mapping structure in the lessons. I found that really helpful."
Free Python→Rust 10 intro exercises → rustplatform.com/via/bob
Feedback:
> "I like the Python to Rust mapping structure in the lessons. I found that really helpful."
dr 🛠️🛰️📡🎧
> However Python devs have a head start — you already think in types...
Not only do I not do this one of the explicity reasons I use python is so that I don't have to.
laund@bbelderbos If you haven't written strictly type-checked Python yet, do so where you can, its surprisingly similar thought process wise. static typing for duck-typing through ABCs and Protocol translates surprisingly well to Rusts Traits
@laund yep it's nice how they translate, and yes type hint as much as you can, it's at least an approximation.