tɛk dɛt/
Definition
An ever-accruing metaphysical liability incurred whenever speed is prioritized over sanity.
Originally a metaphor, now a lifestyle.
Refers to all the shortcuts, hacks, and “temporary solutions” that became permanent fixtures the moment someone said, “We’ll fix it later.”
Common Manifestations
- TODO comments breeding like rabbits in the codebase.
- A backlog item called “Refactor everything” that’s been there since 2017.
- Engineers speaking reverently about “the monolith” as if describing an ancient curse.
- Pull requests described as “small fixes” but containing 1,200 changed files.
- Managers referring to it as “technical opportunity” to sound positive in status reports.
Usage Example
“Every time we take on a new feature, the interest on our Tech Debt compounds faster than our morale depreciates.”
HR Guidance
Tech Debt is not a problem—it’s an investment in future pain.
Encourage teams to view it as a bonding experience, much like shared trauma.
If morale dips, rebrand it as “legacy value creation” or “architectural nostalgia.