Understand Legacy Code

Working with Legacy Code is no fun… unless you know how to approach it and get your changes done, safely.

Is this the real code?

How to come up with a plan that will resonate with non-technical people, in 7 concrete steps.

When you're stuck trying to understand some code, it pays off to spend some time with a different approach.

Code handovers are critical moments in the lifetime of a project.

You don't need fancy tools to start making a dent on a scary method.

You need to fix a bug, but you can't spend a week on it?

What's the best way to deal with these annoying global variables?

With Legacy Code, there is never any good documentation.

Finding a better name for a function is hard, especially when people have contradictory opinions on what a good name looks like…

Tips and advice on dealing with Legacy Code from 5 great speakers at this remote conference I organized for the community.

Here's a way to prioritize refactoring when you have to deal with a large, unmaintainable codebase.

If you worry that following clean code practices create more code to maintain, here's a way out.

Let's see how you end up with these while trying to refactor Legacy Code and what you can do about that.

And 4 ways to fix their usage in Legacy Code.

Feeling overwhelmed by your legacy codebase?

Do you feel paralyzed, wondering how to approach a legacy codebase?

This book is a reference.

If you think that management wouldn't let you refactor Legacy Code, use these 5 arguments to convince them.

When an application becomes impossible to maintain, a rewrite is very tempting.

And what you can do about it if you find yourself in such situation.

When a codebase is large and complex, it's risky to big changes.

Here's a recipe you can follow when you want to add tests on Legacy Code, but you don't have much time to do so.

Here's a useful definition of "Legacy Code" you can refer to.