Skip the washing-up tonight and it's fine. Skip it all week and cooking anything becomes a nightmare.
You’re tired, so you leave the dishes in the sink. One night is fine. But leave them every night for a week and the kitchen grinds to a halt: no clean pans, no space to cook, everything takes twice as long.
Technical debt is that pile of dishes. It’s the extra work that builds up when software is built with shortcuts. Each shortcut saves time now but makes every future change slower and riskier.
Where it comes from
- rushing to hit a deadline
- quick patches that were never tidied up
- building for today without thinking about tomorrow
- old code that nobody understands any more
Why “debt”?
Like borrowing money, a shortcut gets you something now. But you pay interest: every later change takes longer, until you pay it back by fixing things properly.
What it isn’t
It isn’t always bad. Taking on some debt to launch on time can be the right call, as long as you plan to pay it back.
Where the comparison breaks down
You can see a pile of dishes. Technical debt is invisible to everyone but the developers, which is why it’s often ignored until something breaks.
How the words fit together
Quick patches add technical debt. Refactoring pays it back. Too much of it means more bugs.
Some technical debt is a sensible trade-off, like launching sooner. The trouble starts when nobody plans time to pay it back.

When you'll hear it
“That's a lot of tech debt.” The code is full of old shortcuts, so changes are slow and things break easily.
“We need to pay down the debt.” We need to spend time tidying up instead of only adding new features.
“It's legacy code.” Old code that's hard to change, often because nobody fully understands it any more.
“How much of our time goes on working around old shortcuts instead of building new things?”


