The Human Side of Legacy Code

I've written several articles on the technical sides of legacy code and technical debt. But now, let's focus on the emotional side, the human factor. I've touched on this previously,…

Continue Reading The Human Side of Legacy Code

Strangle Your Legacy Code

So you've decided to do something about that piece of legacy code that is taking too much of your team's time. Then you should be aware of the strangler pattern.…

Continue Reading Strangle Your Legacy Code

Monitoring Legacy Applications

So you have a legacy application with quite some technical debt? But you've started turning the ship around and the situation is improving, right? If you're planning on increasing the…

Continue Reading Monitoring Legacy Applications

Timed vs Scoped Releases

I want to add one more thought to my previous post on how to achieve weekly (or faster) releases. It's about the difference between timed releases and scoped releases. A…

Continue Reading Timed vs Scoped Releases

When Not to Refactor

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…

Continue Reading When Not to Refactor

When Should A Startup Refactor?

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…

Continue Reading When Should A Startup Refactor?

Refactor or Rebuild

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…

Continue Reading Refactor or Rebuild

Be Prepared For Leavers

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…

Continue Reading Be Prepared For Leavers