How to deal with technical debt in fast-paced environment
summary
Argues that tech debt is manageable without pausing feature delivery by enforcing a team definition of quality and using two tactics: an organic refactor with feature work and scheduled refactor days. Gives concrete wins: migrated a legacy Backbone codebase to React + TypeScript, and decommissioned four of six Node.js apps for a six-developer team. Uses ADRs beside code, prefers integration tests over expensive E2E where suitable, and follows the Boy Scout rule to steadily raise quality.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:00Defining technical debt
- 5:11Technical debt impact
- 7:20Three-pillar assessment
- 9:30Team quality standards
- 11:41Tackling debt with features
- 14:29Dedicated debt time
- 15:13Debt as evolution
- 16:43Team standards benefits
related talks
11mRefactoring: Managing technical debt before it blows up in your face
28mLessons in Managing Technical Debt
48mTechnical Debt Trap
46mStop calling it technical debt and listen to your engineers
26mTackling tech debt
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
28mSome small steps for code, One giant leap for quality
15mFix your broken windows managing technical debt