The Uncomfortable Truth of Bad Code
summary
Argues that most awful code isn’t malice but missing why documentation, shows a 20‑year mess that still worked but cost more in incidents than a rewrite, describes a data transfer implemented with 2,000+ lines across PL/SQL, custom queue tables, Oracle Advanced Queue, Windows batch scripts and FTP, traces systems with nine layers of duplicated logic, and claims measurable business costs were ignored; recommends recording concrete reasons, tests or comments that force needed complexity and comparing incident costs to rewrite estimates.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:27Refactoring gone wrong
- 2:20Writing for the future
- 3:38Defining bad code
- 4:56Overcomplicating solutions
- 6:20Architecture misconceptions
- 7:40Documenting intention
- 8:51Impact vs. stupidity
- 10:41Case study of bad code
- 14:16Conclusion
related talks
30mDoes Your Code Hurt?
37mWe Hate Code - The !joy of Maintaining Dead Code
46mYour Code Base as a Crime Scene
36mWhy programming is fiendishly difficult and what we can do about it
01h 11mClean Coders Hate What Happens to Your Code When You Use These Enterprise Programming Tricks
39mYou should stop writing code
43mGo Ahead, Make a Mess
59mCode?