Big (or “Long Term”) refactors are hard to pull off in a busy company. To succeed, we must: Convince business that it’s worth the delay. Decide what features will have to wait. Produce regular status updates and ETAs. Justify the refactor as we go. Is it the right approach? Keep ourselves from burning out. Allow time for the team to digest and review the huge diff. Fix a bombardment of QA issues. And we better do this all quickly, because god forbid original and refactored code coexist! Is this ...