Technical Debt as Theory Building and Practice
summary
Argues that treating technical debt like housework metaphor gives concrete handles: map the shape, pick bite-sized pieces, and craft a clear narrative. Gives concrete outcomes: replaced bespoke Jenkins pipelines with code-driven Chef deployments and delivered customer-facing package repos that users loved; ETS built a deployator GUI to separate painful backend work from a usable frontend; an accidentally misused Helm chart required a year-long migration and Solaris 10U1 support forces telemetry, trade-offs, and explicit decisions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:56Tech debt metaphors matter
- 9:34Origins and definitions
- 13:13Tech debt as social concept
- 17:53Housework metaphor
- 23:46Infrastructure similarities
- 26:33Real-world examples
- 32:51Path dependence and legacy
- 37:45Incremental fixes
- 42:41Prioritizing tech debt
- 45:37Theory building for tech debt
- 49:04Closing thoughts
related talks
35mTechnical Debt. A guide for developers and IT managers
45mTechnical Debt: Taking back control when it's already messed up
15mThe Truth About Technical Debt
25mDemystifying Technical Debt
28mManaging Technical Debt at Scale
41mA Bluffer's Guide to Technical Debt for Other People
45mYou Thought Technical Debt Was the Worst? Meet Design Debt!
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It