Hot Garbage Clean Code is Dead
summary
Argues that clean code is dead and proposes practical “hot garbage architecture”: build small React components, prefer pliable over speculative generality, favor composability, measure churn vs complexity, and design for disposability. Cites React, Rails, CSS‑in‑JS, lint/format robots and the painful no‑multi‑component rule as tools that helped and hurt. Shows concrete tradeoffs (when readability loses to performance or stability) and reports happier teams and fewer fights after shipping iterating then refactoring.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:10Blackjack App
- 3:44Who Has Ever Lied on a Resume
- 21:12Four Tenets of Hot Garbage
- 22:50The no Multicomponent Rule
- 29:05Disposability
related talks
30mHot Garbage: Clean Code is Dead
42mClean Code vs. Dirty Code: React Best Practices
50mIntentional Code - Minimalism in a World of Dogmatic Design
30mClean coding with React in a nutshell
20mSacrificial Architecture in modern web development
27mHuman React
23mWorse is Better: The Upside of JavaScript Fatigue
38mGOOD CODE MYTHS