Rust for Pythonistas
summary
A Python developer joins a Rust codebase for a blockchain company and learns by rebuilding the environment from scratch: using rustup and cargo for toolchains, cargo.lock, cargo vendor for reproducible deps, and rust-analyzer plus autoformatting for IDE support. Ownership and borrowing become the core mental model—ownership and borrowing plus stack/heap explanations explain why memory is safe without a GC. Enums like Result/Option exhaustiveness force handling errors, Substrate examples initially look illegible, and Rust eventually enables reliable SDKs and WASM builds that actually work.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:53It's okay to need to start at the beginning
- 6:59Dependency management doesn't have to suck
- 9:38Good intentions don't negate bad code
- 13:53Code without type annotations makes your IDE feel broken
related talks
26mPiecing together Rust: It is more than just writing code
50mConfessions of a Rusty Java developer
27mHow to (not) introduce Rust at your workplace - a tale
01h 04mRust-ifying Your C# Codebase: A Tale of Adventure and Transformation
01h 42mIntroduction to Rust (for people who have never used a compiler)
32mBuilding and Maintaining Rust at Scale
58mRust for The Curious C++ Developers
21mRust - Cargo Cult?