Tackling Technical Debt

Talking about technical debt is like trying to catch smoke. When you think you have the problem described and addressed, someone can say “but what about” and now the whole solution seems to fall apart. For example, when someone is talking about larger debt projects, like big refactors or rewrites, and someone says “What about the small improvements people can make daily?” So, then, that’s talked about for a bit, and someone says, “But we also need time to make bigger refactors.” And the cycle repeats. Even if we catch a little bit of the smoke, enough squeezes out and we have to catch that smoke, but then we lose our grip on the first batch, and in the end people are just frustrated. ...