Declare Bankruptcy on Technical Debt
summary
Argues that unchecked shortcuts turn small features into a messy contact form full of inline styles, dead classes and brittle hacks, and cites a Carnegie Mellon survey of 1831 developers naming architectural choices then inadequate testing and missing docs as top contributors. Recommends concrete practices: write unit tests, file JIRA cleanup tickets, prefer vetted open‑source libs on GitHub, and cites an organizational migration to Ember as a real example of standardizing work and reducing repeated rewrite pain.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:25What is technical debt
- 9:13How debt accumulates
- 15:40Advocating for refactoring
- 22:30Documentation and planning
- 25:45Ownership and accountability
- 31:42Explaining debt to stakeholders
- 38:43Tracking and prioritizing debt
- 40:13Q&A
related talks
28mTechnical Debt: Why it'll ruin your software
35mTechnical Debt. A guide for developers and IT managers
53mThe Technical Debt Trap
15mFix your broken windows managing technical debt
39mStop Focusing on Tech Debt
17mHow to deal with technical debt in fast-paced environment
48mTechnical Debt Trap
46mStop calling it technical debt and listen to your engineers