THE HIGH-RISK REFACTORING

Summary from the TLDR Web Dev newsletter

Before starting a refactor, developers should carefully assess the potential costs of failure (lost revenue, damaged trust, etc.) and how those risks can be mitigated. Refactors should be isolated from feature development and be rigorously tested. Sometimes, the best choice can be to not do a refactor.