Keep It Local
summary
Argues that shrinking the radius of what must be understood makes code reliable: specific claims include that declaring variables where they’re used makes extracting a loop trivial, Rust's ownership system enforces a single owner and the borrow checker prevents shared mutable surprises, encapsulation and small interfaces confine what can change, the Ember Octane autotracking model isolates reactivity and prevents observer-driven infinite loops, and the actor model localizes failure and recovery.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:42Pure Function
- 5:10Immutability
- 6:32Referential Transparency
- 15:58Avoid Global Mutable State
- 16:58Encapsulation
- 18:01Single Responsibility Principle
- 19:13Interface Segregation Principle
- 19:47Dependency Inversion Principle
- 23:16Auto Tracking
- 27:17Control over Reactivity
related talks
32mBuilding and Maintaining Rust at Scale
28mYou Don't Own Me
35mLet’s Talk About Rust
40mRust’s approach of getting things right
21m“Fearless Refactoring & the Art of Argument-Free Rust”
40mAgainst Borrowing: Own the forest, not the trees!
01h 05mKeynote - Rust: confident, productive systems programming
54mMemory Safety with Rust