Technical Debt
Shortcuts and compromises in code that ship faster now but create extra work later when the codebase needs to change.
Technical debt is a metaphor for the accumulated cost of shortcuts in a codebase. Like financial debt, it compounds: quick hacks that save time today slow down every future change because developers must work around the existing mess.
Common sources: duplicated code, unclear naming, missing tests, hardcoded values, inconsistent patterns, and features built on assumptions that are no longer true. AI-generated code can accelerate technical debt if you accept output without reviewing it, because the AI optimizes for "works now" rather than "maintainable later."
Managing technical debt is a core skill for vibe coders. The strategy is not to avoid it entirely (sometimes shipping fast is the right call) but to recognize it, track it, and pay it down intentionally through refactoring. Commit frequently, and schedule regular cleanup alongside feature work.