“Just rewrite it”: What platform teams really think about modernization

The article frames modernization as a reaction to constant business change, specifically mergers, acquisitions, and the churn of initiatives. Those forces are described as creating duplicate infrastructure that no one explicitly requested. For engineers, this means that the baseline environment may already be fragmented before any modernization effort begins, raising the bar for any clean-up work.

Platform teams are quoted as reacting skeptically to the mantra “just rewrite it.” The implication is that a full rewrite is not automatically the best response to duplicated services. Engineers must therefore assess whether the cost of rewriting, new code, testing, deployment pipelines, outweighs incremental refactoring or consolidation of existing assets.

The tension highlighted suggests that modernization projects can become a source of further duplication if not carefully scoped. Teams that pursue a rewrite without first mapping the existing overlap risk introducing parallel systems that compound operational complexity. Practically, this calls for thorough inventory and impact analysis before committing to large-scale code replacement.

Adopting a rewrite-centric approach would require allocating resources to develop, test, and roll out an entirely new codebase, as well as decommissioning legacy components. Conversely, a more incremental strategy may leverage existing services, reducing immediate development effort but potentially extending the period of duplicated infrastructure. Engineers need to balance short-term resource constraints against long-term maintainability.

The article’s focus on platform teams’ perspective underscores that modernization decisions are as much about organizational dynamics as technical merit. Where business units push for rapid change, engineering may encounter constraints such as legacy dependencies, compliance requirements, or limited staffing. Recognizing these limits helps teams set realistic expectations and avoid projects that stall when the underlying duplicated infrastructure cannot be fully reconciled.