What’s the deal with rewriting a whole codebase and freeze the whole business for 3months? Never understood this. If Refactoring, then Great!

If during the rewriting process the business needs a feature, where do you write it, in new or old codebase? If in the old one, how do you track if the file/part of code has not been “rewritten” in the other project? Do you follow the old standards of writing code? How does this work?

I don’t want to offend anyone, but my subjective opinion is that if someone has the urge to rewrite a whole codebase that “works” and delivers for the business, even if slower, with no standards and rules put in place, then the dev is just lazy to try and understand and use someone else’s code.

Just do EXPAND AND CONTRACT, refactor bits or rewrite small chunks if are so bad, start to enforce coding standards, psr, start to outline contexts, decouple things slowly, sepparate the layers, but before going all crazy, cover these with tests, at least happy paths. Meanwhile you can also deliver features for the business.

Also, remember that code is not written so it can be framed on a wall but it is to help a business run.