Too Long; Didn't Read
Every software company has some amount of technical debt, which is additional development work created in the long-term by taking a shortcut in the short-term to get code out the door. Technical debt can take the form of poor design decisions, much-needed refactorings, technology upgrades, and outstanding bugs. In this article, I’d like to discuss why it’s important to pay off your technical debt quickly and the consequences of failing to do so. I'll also address some of the common obstacles that software engineers face when trying to prioritize time to work on technical debt.
Share Your Thoughts