The software industry has a name for the consequences of short-termism: technical debt. The idea comes from writing code: if you prioritize short-term code fixes, or "hacks," over long-term, well-designed code and processes, then you accumulate debt that will eventually have to be paid down by future code rewrites and refactors. Accumulating technical debt isn't necessarily harmful—it can help projects move along faster in the short term—but it should be done as a conscientious observer, not as an unaware boiling frog.
Chapter:
Anything That Can Go Wrong, Will
Section:
It's Getting Hot In Here