Putting an end to "technical debt"
summary
Examines the concept of “technical debt” (as coined by Ward Cunningham) and argues the term has become misleading; the talk analyzes how most development teams suffer rather than intentionally incur such debt and claims the label fails to clarify the real problem. Proposes to develop an alternative model and vocabulary to better describe and discuss nonconforming or low-quality solutions so teams can open a productive dialogue and improve those systems.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:06Processes and state of the art
- 8:34Technical debt definition
- 13:09Three mistakes on technical debt
- 21:32Technical debt as illusion
- 27:04New model: conflicting processes
- 37:20Analyzing conflicts in state of the art
- 43:14Misconceptions on conflicts
- 49:26Tools and conflict resolution
- 50:32Q&A
related talks
34mThe Technical Debt Trap
23mCan We Please Stop Talking About Tech Debt?
25mDemystifying Technical Debt
18mTechnical Debt: How to Communicate to Teams, Beyond the Tech
35mTechnical Debt. A guide for developers and IT managers
39mTechnical debt isn't technical
01h 01mThe Technical Debt Prevention Clinic
28mTechnical Debt: Why it'll ruin your software