Understand Legacy Code
The key points of Refactoring at Scale
The key points of Refactoring
The key points of Kill It with Fire
How to efficiently practice refactoring katas
It's like coding in the dark!
Find how to (re)organize code with git
Delete unused code (and how to retrieve it)
Can AI help me refactor legacy code?
Can AI help me write tests on legacy code?
Fake it until you automate it
Comparing 2 approaches of refactoring untested code
Another way of refactoring untested code
One way of refactoring untested code
7 advice to help you inherit a legacy codebase
Improve your refactoring and testing skills with the Expense Report kata
3 must-watch talks on Legacy Code
The key points of The Programmer's Brain
Testability, Empathy, and Safe Refactorings
Can AI-based test generation help you test Legacy Code?
Refactoring vs. Defactoring
What unit test tool should I bring to my JavaScript team?
DevOps, Living Documentation, and Hexagonal Architecture
4 tips to refactor a complex legacy app without automation tools
Design Patterns, Empathy, and Reading Complex Code
Should we stick to old patterns or sacrifice consistency?
What's the difference between Regression Tests, Characterization Tests, and Approval Tests?
Keeping dependencies up-to-date
Technical Debt, Rewrites, and Refactoring
Is it OK to change code for the sake of testing?
How to tell your client how bad their codebase is?
Safely restructure your codebase with Dependency Graphs
The key points of Re-Engineering Legacy Software
Does refactoring Legacy Code pay off in your career?
Refactoring, Unit Tests, and Symmathesy
The key points of Beyond Legacy Code
When is it the best time to refactor?
Work faster and safer on untested code with Overcommitting
The best way to start testing untested code
What you can do when code is really hard to review
The key points of The Legacy Code Programmer's Toolbox
Approval Tests, TCR, and Menders
When should you stop refactoring Legacy Code?
4 developers working their way through Legacy Code
Where should you put the documentation?
Start cleaning your Legacy codebase with The Daily Refactoring Hour
Identify who to ask for help with Knowledge Maps
Quickly improve code readability with Proximity Refactorings
The key points of Software Design X-Rays
7 techniques to regain control of your Legacy codebase
If you mock, are you even testing?
Convince managers to address Tech Debt with Enclosure Diagrams
Demine your codebase in 30min with Exploratory Refactoring
7 practices for a successful code handover
Reveal the structure of long methods with an online Word Counter
A quick way to add tests when code has database or HTTP calls
Bring Legacy Code under tests by handling global variables
Earn future maintainers esteem by writing simple ADRs
Is it fine to use "AND" in a function name?
5 talks on Legacy Code: The Legacy of SoCraTes, 1st edition
Focus refactoring on what matters with Hotspots Analysis
Don't make Clean Code harder to maintain, use the Rule of Three
Are functions that simply call another function a bad design choice?
What is wrong with boolean parameters?
5 coding exercises to practice refactoring Legacy Code
Dive into an unfamiliar codebase from its edges
The key points of Working Effectively with Legacy Code
5 arguments to make managers care about technical debt
The Ship of Theseus to NOT rewrite a legacy system from scratch
Is it up to the newer developer to pay back others' technical debt?
Use the Mikado Method to do safe changes in a complex codebase
3 steps to add tests on existing code when you have short deadlines
What is Legacy Code? Is it code without tests?