In spite of all that’s been written on the subject of technical debt, it’s still a common occurrence to see it defined as simply “bad code”. Likewise, it’s still common to see the solution offered being “stop writing bad code”. Technical debt encompasses much more than that simplistic definition, so while “stop writing bad code” is good advice, it’s wholly insufficient to deal with the subject.
See the full post on the Iasa Global Blog (a re-post, originally published here).
One thought on ““Technical Debt – What it is and what to do about it” on Iasa Global Blog”
Debt can be overcome d with consistent, positive effort in one direction. Sometimes its in the lack of aligning higher architecture needs and low level aspects of design. I believe with efforts those gaps could be bridged. Than only one right opportunity needed to knock that debt out of question.