Skip to content
BENIBIX Learn

Technical Debt

Development🧪 Testing & QualityCode Quality

Also known as Tech Debt, Code Debt

The cost you pay later for a quick fix you pick today.

Think of it like

Think of it like a mess you leave in the kitchen. Cooking gets slower until you clean up.

Example

Lucy hard-codes one country's tax rate to launch on time. A year later, adding a second country takes three weeks instead of two days.

Why it matters

A little debt helps you ship. Too much makes every feature slower, until the team spends its time on old mess.

Definition

Technical debt is the extra work you take on when you pick a quick fix over a clean one. Like money debt, it can be worth it to ship sooner. But it charges interest: every later change in that area is slower. If nobody pays it down, work can grind almost to a halt. Ward Cunningham coined the term in 1992.

Common mistake

Never writing the debt down. Keep a list, so the team can choose when to pay each one back.

Key takeaways

  1. 1
    Quick now, slow later. The trade you make.
  2. 2
    It charges interest. Each change costs more.
  3. 3
    Pay it down. A little, often.

Compare