Glossary

Technical Debt

Technical debt is a metaphor for the consequences of deliberate or accidental shortcuts in code: "do it fast now, refactor later". "Later" often becomes "never", and the debt accumulates as slow, brittle, hard-to-change code.

Types of debt

Consequences

Every new feature in an indebted codebase costs more: harder refactoring, more bugs, slower onboarding. At the extreme, debt makes a project practically unmaintainable.

Management

Allocate regular time for debt repayment (10–20% of a sprint). Document known debt as tasks, not as // TODO: fix later comments.