Is technical debt always bad, or can shipping fast ever be the right call?

It's not always bad, but the dramatic case of Knight Capital shows what happens when nobody owns the repayment.
On August 1, 2012, Knight Capital lost $440 million in 45 minutes, more than its entire market cap. Per the SEC's report: legacy "Power Peg" code from 2003 was deactivated but never deleted; an engineer reused its old flag for a new feature; and a deployment updated only 7 of 8 servers. The 8th server reactivated the dead code, executing roughly 4 million trades across 154 stocks. The system had even sent 97 automated warning emails beforehand that went unaddressed.
To be precise: the direct cause was a deployment failure, not simply "messy code." But the path there ran through classic technical-debt decisions, dead code never removed, shortcuts over process, no automated risk limits.
Martin Fowler's Technical Debt Quadrant offers a more nuanced view: debt can be deliberate or inadvertent, prudent or reckless. A deliberate, prudent decision ("we must ship now and pay this back later, with a plan") can be entirely rational. The dangerous quadrant is reckless debt with no ownership.
Longer breakdown here: [FullArticle]