Ø
summary
Claims that codebase complexity often outpaces domain complexity, shifting from an ideal pancake model to a problematic cello model that produces a persistent big ball of mud. Argues a corollary: a random engineer has ~90% chance of producing poor code in such environments. Uses conceptual models and industry anecdotes rather than tools or metrics. Proposes concrete tactics: avoid coding-first instincts, prefer reuse or deletion, and sometimes intentionally do nothing to prevent adding entropy.
AI-written summary · about
chapters (6)
- 0:00Professor's advice
- 0:37Domain and product complexity
- 1:32The reality of bad code
- 2:33Big ball of mud syndrome
- 3:22Redefining the conjecture
- 4:17The power of doing nothing
related talks
56mKicking the Complexity Habit
34mHow do our ideas about coding affect the software we create?
58mDon't Walk Away From Complexity, Run
43mGo Ahead, Make a Mess
01h 08mMidnote: For the Sake of Complexity
02mThe architecture of uncertainty
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
32mKeeping your code strong