Debt Metaphor

Channel:Ward Cunningham · Length:4:44 · Published:2009-02-15 · Views:95161

Watch on YouTube

Summary

Ward Cunningham explains the history and intent of the debt metaphor, which he coined while refactoring the WyCash product. He says debt means code reflecting an incomplete understanding of the problem, not sloppy programming.

Why HN recommends it

HN links it as the authoritative correction to common misuse of the term technical debt, straight from its originator.

For the best description of technical debt, you can't do better than listen to the man who first coined the term. — HN, 2016

Software architecture & design · Software practice, open source & careers

Subtitles (excerpt)

I became interested in the way metaphors uh influence how we think uh after reading George Loff and Mark Johnson's metaphors we live by. An important idea is that we reason uh by analogy with the uh uh metaphors that have entered our language. I coined the the debt metaphor to explain the refactoring that we were doing uh on the u Ycash product. This was a an early uh product done in uh digit talk small talk. And it was important to me that we uh accumulate the the learnings we did about the application over time by modifying the program to to look as if it had been uh as if we had known what we were doing all along and it and to look as if it had been easy to do in small talk. The explanation I gave to my boss and this was financial software was a uh financial analogy I called the debt metaphor. And that said that if we failed to make our program align with what we then understood to be the proper way to think about uh our financial objects, then then we were going to continually stumble over that disagreement and uh that would slow us down, which is like paying interest on a loan. with with borrowed money, you can do something sooner than you might otherwise, but then until you pay back that money, you'll uh you'll be paying interest.

On Hacker News

For the best description of technical debt, you can't do better than listen to the man who first coined the term. Ward Cunningham explains: [VIDEO] — philbo, 2016-01
While we're at it, let's talk about what Technical Debt really means. A mess is not technical debt. Ward Cunningham explains Debt Metaphor [VIDEO] transcript at [LINK] — cratermoon, 2023-02
It's kind of a pet peeve of mine around technical debt. Some programmers and places I've worked get it wrong, so I refer people to Ward Cunningham's explanation: [VIDEO] — cratermoon, 2021-06
Here are a few of the resources I have used in the past to help explain to non-technical folks some of what a developer needs to deal with when involved in a large project. 1) Ward Cunningham explains "technical debt": [VIDEO] 2) comic strip - "How Projects Really Work": [LINK] — datashovel, 2014-11
No sorry that is just bad encapsulation and goes under poor programming.Technical debt occurs when you write a good program to your current understanding of the solution knowing that the full understanding of the solution will come later, and that you need to do something now to get to that learning point later, and so you have to repay your partial understanding at the beginning with refactoring… — avereveard, 2023-12

Related videos