Maintenance and Updates › When to Rebuild vs. Maintain

Michael BrenndoerferAugust 22, 20251 min read
AI Agent HandbookAll chapters
Part 14 of 15Deployment and Operations - From Prototype to Production
Chapter 41Maintenance and Updates › When to Rebuild vs. Maintain
Reading section 14 of 19 · When to Rebuild vs. Maintain · 1 minSection 14 of 19 · 1 min

Book contents

Section 14 of 19 · 1 min read

Maintenance and Updates › When to Rebuild vs. MaintainOne section · Sections in this chapter14 / 19 ↓

Sometimes you'll face a choice: keep patching the current system, or rebuild it better. This is a hard decision, but here are some guidelines:

Keep Maintaining When:

  • The core architecture is sound
  • Changes are incremental improvements
  • Users are generally satisfied
  • The codebase is manageable

Consider Rebuilding When:

  • The architecture can't support new requirements
  • Maintenance is becoming harder and slower
  • Technical debt is overwhelming
  • User needs have fundamentally changed

Rebuilding is expensive and risky, so it's usually a last resort. But sometimes it's the right choice. If you do rebuild, apply everything you've learned from maintaining the current system to build something more maintainable.