Hot Garbage: Clean Code is Dead
summary
Argues that strict “clean code” rules hurt changeability and recommends pragmatic, composable components instead. Shows a real React/Flow login chooser refactor where three files (app button, app dropdown, chooser) collapse into one component, causing unit test failures that get replaced by higher‑level integration/feature tests. Recommends using hot-garbage components for uncertain domains, enforcing formatting with Prettier, and marking shortcuts with a debt comment linked to a Trello card so code evolves without speculative overengineering.
AI-written summary · about
chapters (9)
- 0:00Transformation and growth
- 3:04Stagnation vs. change
- 5:35Contextual code quality
- 11:01Challenges in modern code
- 15:24Signs of deathly code
- 19:51Testing for change
- 22:14The impact of formatting
- 24:12Noble obstacles and debt
- 28:47Code as farming
related talks
30mHot Garbage: Clean Code is Dead
42mClean Code vs. Dirty Code: React Best Practices
30mClean coding with React in a nutshell
25mIs clean code dead?
28mVerbosity, Maybe the Key to Better Code
53mIntentional Code - Minimalism in a World of Dogmatic Design
31mThe Importance of Clean Code
39mClean, Concise, Collaborative Code