3 years ago

In a recent conversation about the challenges of refactoring legacy code, one of the responses talked about when to resolve tech debt. The problem isn’t how to schedule tech debt, it’s making it clear what tech debt is. After that, when to resolve it should be obvious In The Unicorn Project, Gene Kim refers to tech debt as “complexity debt”; things in the software or environment that increase the complexity of operations and/or new changes.

This is tech debt: Now, a quick question: the next item on the backlog is scrambled eggs.