[krasicki]

Be careful not to confuse technical debt with technical entropy.

Technical debt may be nothing more than a prioritization strategy that is either intentionally or unintentionally blindsided by a technical asymmetry of attention to a rate of system degradation.

Smart organizations will throttle the degree to which development performs like an ever insatiable desire to maximize efficiency at the cost of mortgaging away the responsibility for system refreshment.

Just as "fitness functions" are desirable sensors for expiring licensing and contractual renewals so should an enterprise think about and implement ecosystem fitness functions that compare existing system state against the latest industry trajectories. Identifying, recognizing, and rectifying business ecosystem weaknesses will go a long way in preventative maintenance and reduced technical entropy and debt.