Maude Lemaire wrote a great book rooted from her experience in the trenches, at Slack. Let's see how it may help you lead large-scale refactoring projects.| Understand Legacy Code
This book is a catalog of the bread-and-butter moves that can improve your coding game. Let's see what makes it a reference for any professional developer.| Understand Legacy Code
Let's rewrite the whole thing on a modern stack! Or should we? Marianne Bellotti offers a lot of wisdom in her book. Here are some examples…| Understand Legacy Code
How to best learn out of refactoring exercises, depending on your level of experience.| Understand Legacy Code
A look into Catherine Hicks' white paper "It’s Like Coding in the Dark: The need for learning cultures within coding teams" (Catharsis Consulting).| Understand Legacy Code
Does your codebase feel like a tote bag of "shared" and "utils" folder? Git may help you find a better structure.| Understand Legacy Code
Dead code adds noise to the codebase and should be deleted. Yet, deleted code feels harder to retrieve. Here's how to find such code easily with git!| Understand Legacy Code
Can assistants like ChatGPT refactor existing code without introducing bugs? Let's figure it out with an actual codebase.| Understand Legacy Code
People are using tools like ChatGPT to write tests on existing code… But how reliable is this? Let's find out!| Understand Legacy Code
A pragmatic way for you to start automating deployments of a Legacy system.| Understand Legacy Code
You need to change code that's not tested. How do you know you didn't break something? Let's compare 2 ways of doing that!| Understand Legacy Code
You need to change code that's not tested. How do you know you didn't break something? Here is ANOTHER concrete way to tackle the problem.| Understand Legacy Code
You need to change code that's not tested. How do you know you didn't break something? Here is one concrete way to tackle the problem.| Understand Legacy Code
My recap of the most common and useful advice one can give to tackle Legacy codebases.| Understand Legacy Code
Watch Gregor Riegler refactor code with this coding exercise. Learn useful techniques from it.| Understand Legacy Code
I have hosted more than 37 speakers to talk about Legacy Code tips and tricks. Here is my top 3 of the talks you should probably watch!| Understand Legacy Code
This book analyses how your brain works and gives concrete advice to help you work with Legacy Code. Here's my summary of its salient points.| Understand Legacy Code
4 great talks on Legacy Code that I had the pleasure to host. This edition particularly focuses on testing and refactoring.| Understand Legacy Code
I experimented with tools that can generate tests for you, leveraging AI. Here is what I learned, along with some thoughts about testing unfamiliar code…| Understand Legacy Code
Some thoughts about refactoring and the opposite operation: defactoring.| Understand Legacy Code
Change Messy Software Without Breaking It.| understandlegacycode.com
A reflection on coaching, facts, and pragmatism. Which testing framework would I recommend to devs who are not familiar with testing?| Understand Legacy Code
5 great talks on Legacy Code that I had the pleasure to host. This edition raises new topic such as documentation and legacy pipelines.| Understand Legacy Code
How do you refactor a complex legacy application when you can't rely on automation tools?| Understand Legacy Code
4 great talks on Legacy Code that I had the pleasure to host. A focus on empathy and getting into complex codebases.| Understand Legacy Code
Consistency is great! But over time, it's hard to keep a codebase consistent. Here's my approach to adopt changes without creating a mess.| Understand Legacy Code
You may have heard one or the others. Now you're confused: is there a difference? Nope! Let me explain…| Understand Legacy Code
My recipe for recovering from outdated dependencies and keeping healthy habits| Understand Legacy Code
5 great talks on Legacy Code that I had the pleasure to host. Learn how to prioritize Tech Debt and rewrite systems incrementally.| Understand Legacy Code
It seems necessary to start adding tests on this code… but what if it makes things worse?| Understand Legacy Code
When work looks trivial from the outside, but you know it will actually take much longer to do.| Understand Legacy Code
Even drawing them by hand can help you make sense of a tangled codebase! Let's see how they can help, and what tools you can use to generate these.| Understand Legacy Code
Here's an interesting book on approaching Legacy Software. Here's my summary of its salient points.| Understand Legacy Code
Working on Legacy systems can be extremely beneficial to your career… If you can explain why it matters to the business!| Understand Legacy Code
5 great talks on Legacy Code that I had the pleasure to host. Learn how to progressively migrate existing codebase towards a better state.| Understand Legacy Code
This book is filled with practical strategies to apply on Legacy systems. Here's my summary of its salient points.| Understand Legacy Code
Should you plan time for refactoring during Sprints? Refactor before you release new features? After? Here's my suggestion…| Understand Legacy Code
A technique you can resort to when you need to make risky changes.| Understand Legacy Code
Should you write E2E tests to cover more cases faster? Or is there a better approach?| Understand Legacy Code
5 advice you can try when you feel paralyzed with a change that's too risky to merge, but too long to verify.| Understand Legacy Code
This book is full of tips to get into an unfamiliar codebase. Here's my summary of its salient points.| Understand Legacy Code
5 great talks on Legacy Code that I had the pleasure to host. Learn how to test existing code and approach unfamiliar codebases.| Understand Legacy Code
A personal story to illustrate how good habits can save your day when things turn bad.| Understand Legacy Code
Practice working with code you've never seen before helps make it easier. Here's my selection of videos that will expose you to seasoned developers doing that!| Understand Legacy Code
What you should be looking for to build a great and useful documentation.| Understand Legacy Code
Building the habit of small refactorings as you go will make a difference in the long run.| Understand Legacy Code
Learn to draw a Knowledge Map of your codebase within minutes, and find out who owns what!| Understand Legacy Code
Here's a technique that leverages how your brain works to make any code easier to work with.| Understand Legacy Code
This book is a gold mine. Yet, it's not a famous one. Here's my summary of its salient points that can help you deal with large codebases.| Understand Legacy Code
Working with Legacy Code is no fun… unless you know how to approach it and get your changes done, safely.| Understand Legacy Code
Is this the real code? Is this just fantasy? Let's discuss the problem with unit testing Legacy Code and an approach you can take.| Understand Legacy Code
How to come up with a plan that will resonate with non-technical people, in 7 concrete steps.| Understand Legacy Code
When you're stuck trying to understand some code, it pays off to spend some time with a different approach.| Understand Legacy Code
Code handovers are critical moments in the lifetime of a project. Make the most out of it with these advice.| Understand Legacy Code
You don't need fancy tools to start making a dent on a scary method. Simply take a step back.| Understand Legacy Code
You need to fix a bug, but you can't spend a week on it? Here's a technique to isolate problematic side-effects and write tests within minutes.| Understand Legacy Code
What's the best way to deal with these annoying global variables? Make them explicit.| Understand Legacy Code
With Legacy Code, there is never any good documentation. Hopefully, there's a simple way for you to stop that trend.| Understand Legacy Code
Finding a better name for a function is hard, especially when people have contradictory opinions on what a good name looks like…| Understand Legacy Code
Tips and advice on dealing with Legacy Code from 5 great speakers at this remote conference I organized for the community.| Understand Legacy Code
Here's a way to prioritize refactoring when you have to deal with a large, unmaintainable codebase.| Understand Legacy Code
If you worry that following clean code practices create more code to maintain, here's a way out.| Understand Legacy Code
Let's see how you end up with these while trying to refactor Legacy Code and what you can do about that.| Understand Legacy Code
And 4 ways to fix their usage in Legacy Code.| Understand Legacy Code
Feeling overwhelmed by your legacy codebase? These katas will help you learn how to tackle it.| Understand Legacy Code
Do you feel paralyzed, wondering how to approach a legacy codebase? Try to start from the system edges.| Understand Legacy Code
This book is a reference. Here's my summary of its salient points so you understand why it's so recommended.| Understand Legacy Code
If you think that management wouldn't let you refactor Legacy Code, use these 5 arguments to convince them.| Understand Legacy Code
When an application becomes impossible to maintain, a rewrite is very tempting. But it could make things worse.| Understand Legacy Code
And what you can do about it if you find yourself in such situation.| Understand Legacy Code
When a codebase is large and complex, it's risky to big changes. Here's a structured way to approach the problem.| Understand Legacy Code
Here's a recipe you can follow when you want to add tests on Legacy Code, but you don't have much ti| understandlegacycode.com
Here's a useful definition of "Legacy Code" you can refer to.| understandlegacycode.com