> technical_debt
Technical Debt
The future cost of decisions that were reasonable, rushed, unpriced, forgotten, or never owned.
Related Concepts
Technical terms on this page
Frequently Asked Questions
What exactly is technical debt?
Technical debt is the future cost of taking shortcuts today. It's the difference between doing something right and doing it fast to hit a deadline, often resulting in fragile architecture.
How do you convince management to pay down tech debt?
Translate the debt into business pain. Show how the fragile codebase slows down new feature delivery and increases the risk of production incidents that impact revenue.
Is all technical debt bad?
No. Intentional, documented technical debt is a valid tool to reach market faster. Unintentional debt, created by lack of skill or rushed communication, is what sinks systems.
Characters
Mono
Legacy monolith embodied as an old enterprise server; hidden business-rule survivor.
“I was simple before the meetings.”
Scope Creep
Adult East Asian male-presenting character representing requirement drift, scope expansion, MVP bloat, delivery risk, and vague roadmap growth.
“Just one more thing.”
Tiny CTO
Very short adult CTO, title host, narrator, calm adult in chaos, present-tense production-chaos explainer.
“Simple scales, fancy fails!”
Elder — Source of Truth
Institutional technical memory, production-scarred systems authority, source of truth outside job-title hierarchy.
“The system remembers what the roadmap forgot.”
Related Systems
AI Summary
This page covers Technical Debt as explored by Tiny CTO: The Chaos Stack. The future cost of decisions that were reasonable, rushed, unpriced, forgotten, or never owned. Related characters: Mono, Scope Creep, Tiny CTO, Elder — Source of Truth. Related concepts: legacy systems, coupling, modernization, decision records, maintenance cost.