Tilting at Windmills, or How to Live with Technical Debt
summary
Talk discusses handling technical debt in long-lived JavaScript projects (legacy code). It covers practical ways to improve such projects that have existed for over a year, focusing on techniques and practices to make them better rather than rewriting from scratch.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:10Technical debt as windmills
- 8:16What is technical debt
- 11:27Justified vs reckless debt
- 15:42Why debt can't be defeated
- 17:26Automated debt detection
- 23:09Code complexity limits
- 28:51Quantitative programming metrics
- 30:55Tactical fixes and hidden knowledge
- 33:53Debt assessment and decisions
- 36:27Refactoring planning
- 38:56Tools for managing debt
- 41:29Conclusion and tips
- 42:51Q&A
related talks
53mRewrite or Not? Life with Technical Debt
45mTechnical Debt: Taking back control when it's already messed up
35mTechnical Debt. A guide for developers and IT managers
31mDealing with Technical Debt
57mPutting an end to "technical debt"
28mTechnical Debt: Why it'll ruin your software
34mThe Technical Debt Trap
31mTech Debt: Leverage for velocity acceleration