What is technical debt?

In practice

The symptom is not ugly code; it is a fall in the rate of change. Small features start taking weeks, estimates lose their meaning and the same area keeps breaking. The fix is to make it visible: a short register of known compromises, what each one costs, and what it would take to clear it, reviewed alongside the feature list rather than separately.

Where it fits in a build

Every system carries some. The question a buyer should ask a supplier is not whether there is any, but whether they can show you the list.

Common mistakes

• Treating a rewrite as the remedy, when the same pressures will produce the same result.
• Letting dependencies age until an upgrade is a project of its own.
• No tests, which converts every change into a risk and makes paying the debt down unaffordable.

Related terms

• Minimum viable product (MVP)
• Observability
• Proof of concept (PoC)

Working on something that involves this?

ASTACKRA designs and builds AI systems, automation and custom software for businesses that need technology shaped around their own workflow. If this term turned up in a proposal and you want a straight answer about whether it applies to your situation, ask us — no obligation, and we will tell you if the answer is no.