On "naming" technical debt

Interesting little article that highlights the power of at least naming technical debt, if you’re in fact going to leave it for later:

[I]f you encourage your developers to document the decisions in code, then there’s a decent chance that they’ll record some ideas about how this should be done in the future.

Do you agree? Take a quick read and share your thoughts!

1 Like