Peter Morlion logo

Avoiding Technical Debt

Is it possible to avoid technical debt when starting a new project? And if not, should we just give up? Or can we find a way of maintaining quality projects while delivering business value at a constant pace? On Technical Debt If you’re unfamiliar with the concept, you can read about technical debt first. In […]

What Is Technical Debt?

Have your developers ever mentioned technical debt? Or are you wondering if you have technical debt? Are you interested in doing something about it? Is it even necessary to do something about it? Let’s first have a look at what technical debt is. Wikipedia defines technical debt as: Technical debt (also known as design debt […]

How Company Frameworks Increase Technical Debt

I focus on helping teams and organizations reduce technical debt. This means a lot of work in legacy applications. But once technical debt has been reduced, it’s important to think about how we will avoid creating too much new technical debt in the future. Of course, there will always be technical debt, but we should […]

How to Use Code Coverage to Your Advantage

Code coverage is an interesting tool that has received quite a bit of bad press over the years. In fact, ever since it became easy to see the code coverage of your tests, there have been fanatic supporters and rejectors. As is so often the case, the value lies in how you use it. Many […]


Media Watch & use My skills Not only have I been blogging for many years now. I’ve also produced online courses and articles and have been featured on a podcast. Courses Legacy Code And Technical Debt For Managers Software Architecture: Patterns for Developers Learning RabbitMQ L’architecture logicielle: Les patrons pour les développeurs Documents & articles […]


About Hi, i’m peter code guy My name is Peter Morlion and I help companies turn around legacy projects and help teams write maintainable code. nice to meet you Are new bugs constantly appearing in your software products? Or is the team struggling to push out new features because the system has become too complex? […]


Services What i offer Looking for a speaker on legacy code, technical debt, refactoring and automated tests?Or someone to coach the team? Consultancy & coaching Coaching & teaching Consultancy & coaching Code Assessment and Strategy Are you interested in the current state of your code?Is it high or low quality? Where are the pain points? […]

The Multiteam Monolith

The monolith is an architectural pattern where the software application consists of a single executable that is deployed as a whole. It can be difficult to work with when it is being maintained by a single team. But matters worsen if it is managed by multiple teams. Here’s why. How Monoliths Grow When a company […]

The Testing Hourglass Is Fine For Legacy Code

I’m a big proponent of automated testing, and so also unit testing. Automated testing is the number one tool in my toolbox to avoid or fix technical debt. But it can also become a force that is blocking you from fixing that technical debt. Here’s why. Two Schools There are two schools in unit testing […]

Software Quality: A Complete Guide to Defining and Measuring

This post was written for the LinearB blog. You can read the original here. There are countless resources on software quality. If you’re reading this, you probably have an idea of what high- or low-quality software is. But defining it seems a lot harder. And if you identify low-quality software but others disagree, how can you avoid endless […]