Latest articles
- 5 arguments to make managers care about technical debt
If you think that management wouldn't let you refactor Legacy Code, use these 5 arguments to convince them.
- Avoid rewriting a legacy system from scratch, by strangling it
When an application becomes impossible to maintain, a rewrite is very tempting. But it could make things worse.
- Is it up to the newer developer to pay back others' technical debt?
And what you can do about it if you find yourself in such situation.
- A simple technique to do safe changes in a complex codebase
When a codebase is large and complex, it's risky to big changes. Here's a structured way to approach the problem.
- 3 steps to add tests on existing code when you have short deadlines
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.
- What is Legacy Code? Is it code without tests?
Here's a useful definition of "Legacy Code" you can refer to.
Written by Nicolas Carlo who lives and works in Montreal, Canada 🍁
He founded the Software Crafters Montreal community which cares about building maintainable softwares.