Debt Metaphor

[tottinge]

Intention was to describe the difference between what the team knows and what the code expresses. In that way, incremental development can create some debt by borrowing against the future.

As he says, though, bad coding is not what was intended and prevents repayment. This is should be required watching for software people.

[mhughe]

Am I correct in understanding that the original debt metaphor is really related more to requirements than it is to code? That is, you incur technical debt when you solve a problem that is not quite the same as the one your customers actually want you to solve?

Does this mean that you can't know how much debt you incur when you start, since you never know how well your understanding of the problem matches the actual problem?

[CroWizCom]

sounds like a challenge between brainstorming and analysis in your interview at artima

[surgictube]

poorly written code could be a metaphor for accepting a higher interest rate ;)

[mrkatamura]

What?

[Braskus]

@doctorspankluv Im pretty sure those are DVD's :)