Technical Debt is a Social Problem
summary
Argues that technical debt is primarily a social problem, not just coding, showing debt breaks into communication (docs, tests, style) and consideration (robustness, dependencies), and that payback fails because of biases like status quo, the IKEA effect and the parenting effect. Recommends a three-step roadmap: pick a small beachhead (works for teams of 4–5 but fails at 25–30), build CI and code review, separate users and maintainers, and empathize with the debtor while replacing pieces like database access or packaging.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:23Technical Debt is a Social Problem
- 2:07Communication
- 3:01Consideration
- 6:24Parenting Effect
- 7:33Build delightful products
- 8:371 Find the right beachhead
- 12:54Being a good maintainer • Responsible for delight • Product responsibility • Product authority
- 13:41Being a good user • Define delight
- 15:10Can you add this function?
- 17:06Empathize with the Debtor
- 17:49Thank your code
related talks
01h 12mBuilding a Technical Credibility to Fight Technical Debt
44mThe socio technical developer
30mLet's talk about Collaboration Debt
47mThe Psychology of Software Teams
19mHalt and Don’t Catch Fire
01h 00mTackling Socio-technical Complexity in the Heart of Your Team
51mCommon pitfalls in technical teams and how to avoid them
14mIt's Like Coding in the Dark: the Need for Learning Culture in Engineering Teams