You Aren’t Going To Need It - How To Stop Writing Code That We Don’t Need
summary
A real bug arises from a memory leak in a third‑party library that crashes embedded devices; the problematic code supports a feature that is deleted because no customers use it, so all prior design, tests and integration work is wasted. The central claim is simple: apply YAGNI and build only when needed to avoid the cost of carry plus costs of building, delay and repair. Practical steps include keeping code minimal, easy to change, and habitually asking why.
AI-written summary · about
chapters (4)
related talks
30mDoes Your Code Hurt?
01h 01mGuide to Destroying Codebases the Demise of Clever Code
56mThe art of keeping your project from falling apart
18mWriting Quality Code
42mThe art of clean code
51mReasons and Ways to Improve Code Quality
47mHow To Build Future Proofed Applications
39mYou should stop writing code