Bonds, Loans and Credits — What Do You Owe Your Code?
summary
Talk explains technical debt: what causes it, when and how it accumulates, and why it should be repaid. It describes practical techniques for managing and repaying debt in software projects, based on the speaker’s hands-on experience delivering business value while keeping code maintainable.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:18Tech vs financial debt
- 8:38Enterprise system analogies
- 10:44Developer role in debt
- 13:17Fowler's debt types
- 15:45Symptoms in system
- 18:54Debt repayment strategies
- 21:43Practical repayment modes
- 24:58Regular debt prevention
- 27:25DORA metrics and quality
- 31:42Business awareness
- 35:09Team collaboration
- 37:20Dependency updates
- 39:27Non-technical communication
- 42:14Refactor vs new system
- 44:23Code optimization vs value
- 45:06Summary & Q&A
related talks
45mA developer always pays his debts
35mTechnical Debt. A guide for developers and IT managers
25mDemystifying Technical Debt
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It
45mTechnical Debt: Taking back control when it's already messed up
45mYou Thought Technical Debt Was the Worst? Meet Design Debt!
15mThe Truth About Technical Debt
36mPrioritizing Technical Debt as if Time & Money Matters