Skip to main content

> Term

technical debt

The accumulated cost of shortcuts, deferred decisions, and rapid solutions that require future rework.

Detailed Explanation

Technical debt is the financial metaphor for bad code. Like financial debt, it allows you to buy time or features today at the cost of interest payments (slower development, bugs, incidents) tomorrow.

If the principal is never paid down, the 'interest payments' eventually consume 100% of the engineering team's capacity, bringing all feature development to a grinding halt.

Why It Matters

It is the silent killer of engineering velocity. High technical debt makes simple changes dangerous and complex changes impossible.

Common Failure Mode

The business refuses to allocate time to pay down technical debt, leading to an eventual complete rewrite of the system that takes two years and fails.

Practical Example

Hardcoding configuration values to hit a deadline. Three years later, the company changes data centers, and it takes a month to find and change all the hardcoded IPs.

Production Manifestation

Adding a new field to a user profile takes three weeks and breaks the payment processing system because the legacy data model is a tangled mess.

Frequently Asked Questions

What is technical debt in short?

The accumulated cost of shortcuts, deferred decisions, and rapid solutions that require future rework.

What is the most common failure mode?

The business refuses to allocate time to pay down technical debt, leading to an eventual complete rewrite of the system that takes two years and fails.

AI Summary

The accumulated cost of shortcuts, deferred decisions, and rapid solutions that require future rework. It is the silent killer of engineering velocity. High technical debt makes simple changes dangerous and complex changes impossible.