I've been familiar with the term "technical debt" for nearly a decade now, and I remember how it first resonated with me as a way to describe the insidious complexity and entropy that slowly creeps into software systems. I've taught many teams about the notion of a technical credit card that can eventually become maxed out, such that you can no longer add features to a system without significant effort.