Rewritten Guide: Incremental Mass

Feature: Incremental Mass-Rewritten Guide

Phase 3: Re-Integration (Days 31–45)

A rewritten piece of mass does nothing if it sits in isolation.

  1. Internal Link Cascade: From your newly rewritten guide, link out to 3–5 other Fossils you plan to rewrite next month. This passes fresh link equity.
  2. External Re-Promotion: Do not just "share the link." Extract the best 3 new paragraphs and post them as a Twitter/X thread, LinkedIn carousel, or Reddit summary. Link back to the full guide.
  3. Email Re-Introduction: Send a simple email to your list: "We fixed something old. It's now 10x better. Here's what changed."

Part 1: The Philosophy of Incremental Rewriting

Before diving into specific habits, you must understand the framework.

  1. The Edit vs. The Delete: You aren't deleting your old life; you are editing it. If you watch 4 hours of TV a day, an incremental rewrite doesn't demand you stop watching TV. It demands you replace 1 hour with a different form of entertainment or self-improvement.
  2. The Friction Threshold: Incremental changes work because they stay below your brain’s "alarm system." Your brain resists massive change but will accept small tweaks that require little willpower.
  3. Compound Interest: A 1% improvement in your health or happiness compounds over time. Saving $5 a week or reading 5 pages a day creates a massive library of results over a year.

Phase 2: Rewrite the Leaf Nodes

Do not rewrite the whole call graph. Start with read-only operations that have no side effects. incremental mass rewritten guide

2. The "Rewritten Guide" Concept

Most existing guides (Fowler’s StranglerFig, Feathers’ Working Effectively with Legacy Code) assume sequential replacement. The Rewritten Guide is not a first-edition how-to. It is a meta-guide – a guide that has itself been incrementally rewritten to reflect real-world failures. Key revised principles:

| Original Guide (2008) | Rewritten Guide (2025) | | :--- | :--- | | "Start with the smallest module." | "Start with the highest-traffic, lowest-business-risk API endpoint." | | "Rewrite then route." | "Route then rewrite (dual-write + comparison)." | | "Maintain perfect parity." | "Tolerate temporary functional drift with feature flags." | | "One team, one codebase." | "Enable parallel modular teams with contract testing." | Internal Link Cascade: From your newly rewritten guide,

Example Workout Plan with Incremental Mass

| Exercise | Week 1 | Week 2 | Week 3 | Week 4 | | --- | --- | --- | --- | --- | | Squat | 100 kg | 102.5 kg | 105 kg | 107.5 kg | | Deadlift | 120 kg | 122.5 kg | 125 kg | 127.5 kg | | Bench Press | 80 kg | 82.5 kg | 85 kg | 87.5 kg |

Title: The Incremental Mass Rewriting Guide: Refactoring Legacy Systems Without Breaking Production

Abstract Legacy code is a liability, but a "big bang" rewrite is often a suicide mission. This paper presents Incremental Mass Rewriting (IMR) , a hybrid strategy that combines the architectural purity of a rewrite with the safety of incremental refactoring. We provide a step-by-step guide to strangling a legacy system by rewriting it in parallel, routing traffic gradually, and measuring success via objective metrics. Part 1: The Philosophy of Incremental Rewriting Before

1. Introduction: Why "Mass" Matters

In traditional rewrite strategies, the entire system is considered the unit of change. This fails when the system’s inertia (mass × resistance to change) exceeds project tolerance. We propose:

[ \textRewrite Inertia = \sum_i=1^n ( \textLOC_i \times C_i \times D_i ) ]

Where:

High mass means high risk. Incremental reduction of mass via molecular replacement is the only viable path for systems >1M LOC.