@faassen The original metaphor is specific to an assumption that understanding of the problem ought to be embedded in the code, and that the history of design changes that led to today's code should not – it just makes things harder to understand.

But the point I'll try to make in the upcoming episode is that the metaphor lands differently for people who think debt is something to be paid back vs. something to be rolled over into more debt.