Technical Debt Doesn't Disappear

Legacy systems are hard. Being able to work effectively with them is something they don't really teach you in school. Probably because it's entirely frustrating, complicated, and a big turn off even for seasoned programmers. It's a bit of a black art and there's little joy or glory in being good at it. Except perhaps that the job market for your specialty is pretty small and will always be in demand.<p>For a good read on the subject, try "Working Effectively with Legacy Code" by Micheal C. Feathers.<p>I prefer the term "technical baggage," over "technical debt." This is mainly because debt refers to an economic means of borrowing a sum of future purchasing power. This breaks down when referring to the cost of engineering decisions. The cost of maintaining legacy systems tends to increase with time and you cannot calculate any sum to borrow based on assets or secured revenue. The decisions you make now will haunt your business for a long time to come. Poor technical decisions are simply something you will have to learn to live with.<p>When dealing with legacy systems from a business perspective, the question one has to ask is, "how valuable is it to maintain and enhance the existing system going forward?" In other words, when will the costs of continuing development of your legacy system outweigh the revenue it generates? For large systems found in banks and insurance companies it can be a very long time. For small businesses it is much shorter than you think.<p>FWIW, it seemed to me that Netscape simply made the decision to start from scratch too late. The revenue they were generating from their old code base had trickled off too long and dipped below their operating costs before the warning signs went up. I don't think it makes a compelling argument against re-writing.<p>As someone supporting a legacy system, it sometimes makes sense to re-write the system. Treat the existing system as a prototype and derive the minimum viable product from it to start with. Spin it off as a new product, set an shut-off date for the old software, and convert your customers. Obviously this doesn't work for every scenario; so YMMV. Just be smart about it and use evidence to back up your assumptions. Sometimes simply writing a legacy compatibility layer and porting the most painful bits of code slowly is the key. Re-writing certainly isn't for everyone.

I used to work for a startup that rewrote its products all the time. It was a huge mess with all the consequences outlines in the article.<p>The problem was not the rewriting itself but the lack of understanding how things went wrong the first time. From my experience it is absolutely mandatory to have many deeply introspective and self-critical thought sessions to figure out how you got into the mess. Only if you have clearly identified what went wrong in the past, you will be able to successfully rewrite a project and avoid the mistakes.<p>For some of the products we did this and rewriting was a huge success. For some others we did not and the rewrite turned out to be just as terrible as the original version. Then we rewrote it again and it was still a mess.

A book that I would recommend for refactoring object oriented code (Java in particular) is Refactoring-Improve the Design of Existing Code by Martin Fowler (a friend to the Go4). Written well and in a simliar format at Design Patterns-Elements of Reusable Object-Oriented Software by Go4 (Gang of Four).

At my current job I was tasked with making a new framework and transitioning our code over to it. The reason that we decided to actually work on technical debt is because we are growing very rapidly and the old setup is too slow so the customers are actually affected. It was extremely useful to have every technical stakeholder in the design discussion to figure out what features we really need, where we went wrong with the old design, and how to transition properly without spending 10 months. So far so good, we are transitioning a bunch of our code over to the framework and it seems to be working well. Im sure mistakes will be made along the way, but planning with people who made the original mistakes (and subsequently have manned up to them) should help prevent remaking original mistakes.

It's really about sustainability. Technical debt isn't sustainable. Getting into a situation where you're afraid to fix the old thing because of opportunity costs isn't sustainable. Most often, this is because the cost of testing is too high and/or the cost of the bugs that would probably happen/escape testing would be too high. Quick fixes that get you through the next month at the cost of more technical debt going forward aren't sustainable.<p>Sustainable practices are smart practices.

Do we really need all these articles that urge people to never, ever rewrite anything? (Classic example being Joel's article, which also uses Netscape as an example: <a href="http://www.joelonsoftware.com/articles/fog0000000069.html" rel="nofollow">http://www.joelonsoftware.com/articles/fog0000000069.html</a> .)<p>Managers and business users hate rewerites as it is. That's part of the reason there is so much horrendous legacy code out there. Often, people who have the authority to make decisions about rewriting something don't interaface with the code, don't understand undetlying issues, don't see what was changed in technological context since the code was written.<p>In my own experience, most of the rewrites were totally worth it. It wasn't just because the code became better, it was because the understanding of the problem has matured. People were able to understand the problem better, so were were able to write better code to solve it.

I think that architects and developers often forget the basics software development when planning rewrites. Because they've been working on the product for so long, they think the normal rules of working iteratively and getting feedback don't apply. They try to replicate the entire existing system at a point in time, turning the rewrite into a waterfall project. Then they're surprised when things they fall behind and can't adjust. You're better off in almost all cases to break it up and approach the problem as refactoring instead.<p>When I was an "e-business" consultant, we had a saying: "Six month projects take nine months, twelve month projects take eighteen months, and two year projects get canceled." If your rewrite is projected to take over a year, you're in huge trouble.

&#62; The scariest problem is our project_list_data function with Cyclomatic Complexity of 145 million.. which is down from 195 million. It "passes" data in via a series of globals and "returns" data the same way. Don't worry, we're working on it.<p>Is this meant to be sarcasm? Because if not, thats an insanely huge function. I imagine most compilers would choke on it...

This hits home. I was brought into a company to work on a product together with an other new hire, and the company decided that we would go and do a rewrite – for this decision I was partially to blame. Six months later we were stuck with a failing ‘classic’ site that had barely been maintained, angry customers and nothing to show for it. Lessons learnt.

Anyone know of a link to the mentioned talk? The one given ( <a href="http://joind.in/talk/view/2418" rel="nofollow">http://joind.in/talk/view/2418</a> ) is just the conference description.

This is rather concerning the presentation of the text: Did anyone else find the black font of this size on green background disturbing for the eyes? Selecting the text helps, though...