technical debt
A design shortcut creates a continuing cost for future changes.
Use this when A deliberate shortcut will make a known follow-up task harder.
without the term
“We're cutting a corner here to ship by Friday. Can you leave a proper note about what we skipped, why, what it'll cost later, and when we should fix it, not just a TODO?”
with the term · How do you ask a model for technical debt?
Document this technical debt with its current benefit, future cost, and repayment trigger. Keep the immediate implementation within the agreed scope.
What is technical debt?
Technical debt is a shortcut that makes later changes cost more. Writing down the shortcut, its cost, and when to fix it lets you weigh repaying it against other work.
Why does technical debt matter when vibe coding?
A vague TODO can conceal the reason a compromise was accepted.
How do you do technical debt?
Name the shortcut, its concrete cost, and the condition that would justify changing it.
What goes wrong with technical debt?
Calling every stylistic disagreement debt without identifying a cost.