There are cases where it makes sense not to touch a legacy codebase with lots of technical debt. Unlike real debt that must always be repaid, technical debt doesn't always need to be. But the use cases are more exception than rule. No Need For Change A piece of software that runs fine without the need for any change can be left to run just fine. If there are no (blocking) bugs, there is still support for the platform, maybe you're monitoring it closely and all is OK, then you have little business reason to touch it.…

If you're working at a startup, chances are things need to go very fast. Faster than business that have a steady income. A product needs to get out the door as fast as possible, so it can be OK to incur some technical debt and create legacy code. But when do you start to clean up the technical mess that is the result? Don't Wait Too Long Industry experts agree on the fact that technical debt and legacy code will slow you down in the long run. In fact, many believe that it already starts to slow…

So you have a working piece of software but you know the quality needs to improve. The team might be saying alarming things like "we need to rewrite this entirely." Should you halt feature development for weeks or months? Probably not. Keep Producing Features Features are what makes your product attractive to your customers. It's why they choose your product in the first place. And hopefully, it's why they're paying you as well. So stopping the development of new and requested features isn't a decision taken lightly. Some companies have done so, and successfully. A notable example…

The TIOBE index is an index that rates the popularity of programming languages. It recently created a bit of a hubbub when it listed Visual Basic .NET on the fifth position. This was a step up from the sixth position in June 2018. This is in contrast to the perception and gut feeling of many programmers out there. However, there can be several explanations to this phenomenon. But there are also some concerns with the TIOBE index. And should we even care? The TIOBE index I recently tweeted this (partial) graph of the TIOBE index: https://twitter.com/petermorlion/status/1143412393441157120 The…

I've previously answered a specific question about whether or not .NET 4.6.2 is legacy technology. Let's broaden the scope and have a look at some examples of legacy technology. This will allow us to distill some common properties of why certain technology can be regarded as legacy technology, and what our options are. Some Specific Examples Creating a full list of legacy technology would be an impossible task. We could list hardware, operating systems, code libraries, applications, and services across a variety of eco-systems. The list would be endless. But here are some well-known examples of what…

In the land of legacy code, many teams discuss whether they should refactor the existing application or rebuild it from scratch. But the answer to this problem is more nuanced than many would like to admit. What is Refactoring? I've previously written about what refactoring is and why it is a valuable investment. In short, refactoring is where code is changed so that it has a higher quality, but without changing any functionality. This higher quality usually allows teams to pay off technical debt, prepare for new features or adhere to new standards for example. What is…

A lot has been written about why software developers leave, and how you can avoid it. But you can never avoid it entirely. So you must have a way of reducing the damage you experience when someone leaves. You Can't Keep People My father worked for Philips for 20+ years. Most of my friends and colleagues haven't worked at the same place for more than 10, maybe even 5 years. The current economy demands flexibility from employees. But it goes both ways. Employees have come to expect flexibility from employers: remote work, flexible hours, and also regular…

I've previously mentioned that one of the traits of legacy code is that it lacks documentation or the existing documentation is of inferior quality. Let me now provide some guidance on how to document a legacy code project, or any project for that matter. Start With the Overview The minimum amount of documentation a piece of software has must be a description of what the software does. What problem is it trying to solve? A next step would be a high overview of how this problem is solved. Don't document the nitty-gritty details yet. Just a description…

I recently received a question from a former colleague regarding the .NET Framework they were using for their application. The question was: should we regard .NET 4.6.2 as legacy? The question that follows from this is: should we make the effort of moving to a newer version or to .NET Core? Even if you're not using .NET, this post may still be relevant to you, because you can apply the thinking to your application and framework. The Support Lifecycle One thing any company should check is the support lifecycle of the framework they're using. This is important…

In any project, there quickly arises a need for what we call refactoring. This is especially true in legacy projects. But what do we mean by refactoring exactly, and why is it so important? Refactoring: New Wine in Old Bottles? Wikipedia defines refactoring as follows: Code refactoring is the process of restructuring existing computer code—changing the factoring—without changing its external behavior. Refactoring improves nonfunctional attributes of the software. https://en.wikipedia.org/wiki/Code_refactoring So what this means is that developers change the underlying structure of the code, i.e. change the implementation, of existing features and functionality. But those existing features and…