Making others care about refactoring

🎓  Related articles

• The key points of Refactoring at Scale

  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.

• The key points of Kill It with Fire

  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…

• Delete unused code (and how to retrieve it)

  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!

• The key points of The Programmer's Brain

  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.

• What unit test tool should I bring to my JavaScript team?

  A reflection on coaching, facts, and pragmatism. Which testing framework would I recommend to devs who are not familiar with testing?

• DevOps, Living Documentation, and Hexagonal Architecture

  5 great talks on Legacy Code that I had the pleasure to host. This edition raises new topic such as documentation and legacy pipelines.

• Design Patterns, Empathy, and Reading Complex Code

  4 great talks on Legacy Code that I had the pleasure to host. A focus on empathy and getting into complex codebases.

• How to tell your client how bad their codebase is?

  When work looks trivial from the outside, but you know it will actually take much longer to do.

• The key points of Re-Engineering Legacy Software

  Here's an interesting book on approaching Legacy Software. Here's my summary of its salient points.

• Does refactoring Legacy Code pay off in your career?

  Working on Legacy systems can be extremely beneficial to your career… If you can explain why it matters to the business!

• The key points of Beyond Legacy Code

  This book is filled with practical strategies to apply on Legacy systems. Here's my summary of its salient points.

• Where should you put the documentation?

  What you should be looking for to build a great and useful documentation.

• Convince managers to address Tech Debt with Enclosure Diagrams

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

• Earn future maintainers esteem by writing simple ADRs

  With Legacy Code, there is never any good documentation. Hopefully, there's a simple way for you to stop that trend.

• 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.