Clean Code: Eternal Practices
summary
Claim: clean code is emergent from clean architecture and a clear model. Live code builds an e‑scooter system with Reservation, Scooter, Demand and Maintenance repos, shows race conditions and test bloat when services coordinate three datasources, and then replaces that with an Availability aggregate exposing take/release API so reservation, maintenance and demand adjust to availability not each other, simplifying tests and removing logical coupling. Second demo implements Prisoner’s Dilemma strategies, an interaction model and a tournament/evolution layer; it runs and shows surprising winners (mean and a “good memory” variant).
AI-written summary · about
chapters (8)
- 0:00Introduction and setup
- 3:15Clean code is emergent
- 17:25Problems with naive design
- 24:51Spot the missing behavior
- 31:51Refactoring to availability model
- 42:43Separating domain and application logic
- 50:29Building higher abstractions
- 56:54Q&A and closing
related talks
25mIs clean code dead?
39mClean, Concise, Collaborative Code
53mIntentional Code - Minimalism in a World of Dogmatic Design
02h 42mClean Code: The Next Chapter
25mBest Practices for Writing Clean and Maintainable Codes
56mClean Code, Two Decades Later
45m'Writing code that lasts'...or writing code you won't hate tomorrow
30mHot Garbage: Clean Code is Dead