Technical Debt

When I first heard the phrase “Technical Debt”, I nearly fell of my chair, but recently, a couple of articles have passed me by and I thought I’d have look and think about if it helps address the intractable problem of maintaining legacy technology, but particularly applications code. The problem is that to make changes, one often has to amend code that’s already in use. This increases the cost of the project. The increase in cost to new projects is part of the “Technical Debt”, however, it’s basically a metaphor. Is the problem one that financial management tools, can be used to improve the understanding of? Does this apply better to code that one has development rights to, rather than packages or infrastructure? Here as every are my notes and links. Continue reading “Technical Debt”