Learning Rust the wrong way
summary
Argues that mastering Rust takes spaced and interleaved practice over time, not one-hour lectures, cites experiments where random practice outperforms blocked practice and painting studies favor spacing, and recommends active generation (make your own problems). Demonstrates problems encountered when converting a decade-old C++ Pokemon simulation to Rust: the borrow checker rejects simultaneous mutable and shared borrows, lifetimes block naive JS callbacks from WebAssembly, and the fix is to extract primitive values. Suggests using rustlings exercises and porting real projects to learn.
AI-written summary · about
chapters (36)
- 0:00Intro
- 2:17Quiz
- 2:55Van Gogh
- 3:42Introduction
- 3:54Turtlesec
- 4:10Good Stuff
- 4:42Talk Structure
- 5:18Wrong Ways to Learn Rust
- 6:12What is Rust
- 8:05Borrowing
- 10:13Mutability
- 12:31Baseball
- 14:04Baseball Study
- 15:16Results
- 17:00Why Rust
- 17:38This is not a jab
- 19:30Pokemon
- 20:42GIF
- 21:03C
- 22:09Rush
- 22:30Pokemons
- 23:39Battles
- 26:18Paintings
- 27:35Experiment results
- 29:41Study results
- 30:34desirable difficulty
- 32:38study done 1978
- 34:38programming in 10 days
- 35:02remembering
- 36:38errorless learning
- 37:16quiz people
- 39:25block of code
- 40:33the wrong way
- 41:10the rusty key
- 41:57the one hour lecture
- 43:23some improvements
