--- title: "The Repair/Replace Heuristic for Legacy Software" url: https://daily.dev/posts/the-repair-replace-heuristic-for-legacy-software-f0p2v1yc4 source_url: https://verraes.net/2016/04/repair-replace-heuristic-for-legacy-software type: article source: "Mathias Verraes" published: 2026-06-17T11:25:45.056Z updated: 2026-06-17T11:27:33.054Z tags: ["career", "architecture", "technical-debt"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The Repair/Replace Heuristic for Legacy Software **[Mathias Verraes](https://daily.dev/sources/verraes)** · 5 min read · 0 upvotes · 0 comments ## Summary A heuristic for deciding whether to repair or replace legacy software based on its historical design quality. If a system was well-designed originally, it likely contains encapsulated learning worth preserving and should be repaired. If it was poorly designed from the start, replacement is more attractive. The key insight is to build temporal models — understanding how a system evolved and why — rather than only structural snapshots of current state. This historical thinking reveals whether the system's purpose and constraints have shifted, and informs smarter decisions about technical debt repayment. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Learning to love other people’s code.](https://daily.dev/posts/learning-to-love-other-people-s-code--q3ox7xl8d) · Simple Thread · 0 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#architecture](https://daily.dev/tags/architecture), [#technical-debt](https://daily.dev/tags/technical-debt) [View this post on daily.dev](https://daily.dev/posts/the-repair-replace-heuristic-for-legacy-software-f0p2v1yc4)