Rewrite or Not? Life with Technical Debt
summary
A retrospective on managing technical debt in a production system, describing practical changes made: removing VPN to improve developer ergonomics, introducing CI and end-to-end tests, building an Updater for deployments, and delegating work to other teams via plugins. The talk emphasizes maintaining a product roadmap and vision while balancing refactoring versus incremental improvements.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:18What is technical debt
- 3:21Solving technical debt
- 6:11Convincing business
- 9:02Case study: Dashboard
- 13:04Case study: Commerce solution
- 21:25Rewriting from scratch
- 27:11Convincing the team
- 31:04Technical debt in new projects
- 34:20Challenges and mistakes
- 37:55Results and achievements
- 39:38Managing technical debt
- 41:02Q&A
related talks
48mTilting at Windmills, or How to Live with Technical Debt
45mTechnical Debt: Taking back control when it's already messed up
31mDealing with Technical Debt
35mTechnical Debt. A guide for developers and IT managers
46mStop calling it technical debt and listen to your engineers
34mThe Technical Debt Trap
26mTech debt as innovation, reframing this forever problem as an opportunity
57mPutting an end to "technical debt"
