Learning Rust the wrong way.
summary
Shows that learning Rust requires deep, varied practice not tutorials alone: converting real C++ projects exposes borrow/mutability walls (mutable and immutable borrows conflict at compile time) and the fix is design changes like extracting just the needed field (damage) instead of borrowing whole objects. Demonstrates a Pokemon grid simulator and a WebAssembly Sudoku that work faster after rewriting, uses rustlings exercises, and cites learning studies with surprising results such as 56.7% improvement for random practice versus blocked practice. Emphasizes spacing, interleaving and desirable difficulty.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:36Talk philosophy
- 5:02Learning Rust the wrong way
- 11:55Borrowing and mutability
- 12:18Baseball batting averages
- 17:54Casual learning fails
- 26:11Spaced vs. massed learning
- 31:49Effective learning strategies
- 40:02Desirable difficulty
- 42:28Q&A
related talks
52mLearning Rust the wrong way
29mLearning Rust by accident
59mRust for C++ developers - What you need to know to get rolling with crates
56mReady for Rust
27mHow Rust taught me to think about systems
01h 04mRust-ifying Your C# Codebase: A Tale of Adventure and Transformation
28mLearning Rust with Humility and in Three Steps
18mLearning Systems Programming with Rust