Addressing Tech Debt without Killing Quality

Matt Eland
Oct 5, 2019 · 9 min read

So you’re going to start fixing some of your technical debt? Great! Just remember the one cardinal rule: Don’t break the application.

Think about it — when we get to take on technical debt the business paying an opportunity cost for us to refactor code instead of making new features or even fixing existing bugs. That’s okay and necessary and there are ways of telling the business how important this activity is, but the one thing you can’t do is this:

When paying down technical debt, you can’t cause new bugs.