⛑ I'm building up a kit to help you rescue your codebase!
When I say "Legacy Code" I mean valuable code you're afraid to change.
We all have to deal with Legacy Code. But it's damn hard to!
Here you'll find answers to your questions. I'm sharing useful tips and concrete advice that will help you tame the legacy codebase you've inherited.
📖 Helpful Guides
- Getting into a large codebase
Diving into a large, undocumented codebase is overwhelming. Let's see some techniques to approach it.
- Is it a best practice or a code smell?
Not sure if a pattern will make the code more maintainable? Here are a few resources that will help.
- Changing untested code without breaking it
Without tests, every code change is risky. But how to put tests on a code that wasn't design for it?
- Code feels impossible to maintain
Sometimes, you seem to hit a point of no return and that the best strategy would be to burn it all and start over. Are there alternatives?
- Making others care about it
What you can do when it seems that no-one cares about the technical debt that's piling up.
🥋 Specific techniques
- Approval Testing
A technique to quickly put tests on Legacy Code, so you can refactor safely.
- Behavioral Analysis
A technique to get insights from large codebases, using VCS information.
💡 Latest articles
- When is it the best time to refactor?
Should you plan time for refactoring during Sprints? Refactor before you release new features? After? Here's my suggestion…
- Work faster and safer on untested code with Overcommitting
A technique you can resort to when you need to make risky changes.
- The best way to start testing untested code
Should you write E2E tests to cover more cases faster? Or is there a better approach?
- What you can do when code is really hard to review
5 advice you can try when you feel paralyzed with a change that's too risky to merge, but too long to verify.
- The key points of The Legacy Code Programmer's Toolbox
This book is full of tips to get into an unfamiliar codebase. Here's my summary of its salient points.
- If you want more, check all my published articles
- Tips for Working with Legacy Code
I talk with Jason Swett about working with legacy code, adding tests to legacy code, how to safely make changes to legacy applications, and more.
- Changing Messy Software Without Breaking It
I talk with Robby Russell about practices like feature toggling or sustainability weeks to work on improving things. I also give advice for listeners who struggle to get stakeholder buy-in on dealing with technical debt challenges.