|
|
|
|
|
by Hypergraphe
1659 days ago
|
|
I've worked, and still work, on large legacy codebases on a daily basis and I couldn't agree more that total rewrite is not the solution in most cases and a waste of time and money. But, I have also witnessed projets that were poorly engineered and should have been rewritten or refactored in time to permit better integration of junior devs, prevent the burnouts and the people quitting. Sometimes, when you don't make the good refactoring on time, you end up with nobody to maintain your software and you have to rewrite it. |
|
Your point about finding the right time to refactor is spot on. The answer isn't always "NO", but rather, there's something of an art and intuition to understanding if a huge refactor is really a net positive.
Lead developers should understand that failure to do this puts the business at risk, since hiring and maintaining competent developers is critical, and nobody is going to want to stick around to work on an outdated, unnecessarily complex system.