sort of silly to try to keep the metaphor as a financial instrument.

its really a simple message: write bad code, and you might pay for it later. sometimes you get lucky, sometimes you don't.

"technical debt" as a term isn't intended to capture a specific risk/reward payout structure. It doesn't need clarification in this vein.