Most rewrites serve the engineer, not the business

# Summary The article argues that most code rewrites prioritize engineer preferences over business needs, with the author cautioning against discarding production code that contains years of bug fixes and institutional knowledge. While some rewrites are justified by concrete business problems—such as end-of-life runtimes, security vulnerabilities, performance degradation, or new capability requirements—rewrites driven solely by unfamiliarity with existing frameworks or aesthetic preferences represent costly vanity projects that risk reintroducing solved bugs.