Dealing with Technical Debt
summary
Claims that average developers spend 42% of their time on technical debt and that orgs who actively manage it ship at least 50% faster. Describes a Git integration built with strategy and factory patterns plus an adapter class that works technically but gets abandoned because it outlasts actual needs. Recommends pragmatic MVPs, track intentional debt in the backlog, fix small issues as part of tickets, allocate repointing time (separate refactor team or scheduled refactor hours), and watch for bugs duplicate code and slow performance as concrete signs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:07What is Technical Debt
- 4:27The Approach
- 7:10Lean Development
- 11:30Questions to ask yourself
- 12:53When does technical debt come back
- 15:13How to look for technical debt
- 19:12How to manage technical debt
- 22:36How to approach mediumsized technical debt
- 27:30How to avoid technical debt
related talks
35mTechnical Debt. A guide for developers and IT managers
06mManage your tech debt like a mortgage
01h 12mBuilding a Technical Credibility to Fight Technical Debt
01h 01mThe Technical Debt Prevention Clinic
34mThe Technical Debt Trap
28mTechnical Debt: Why it'll ruin your software
25mDemystifying Technical Debt
33mTackling Tech Debt on Android