Rewrite the app, or keep patching?
Work · Board of 3Our app is a four-year-old Rails monolith. Our two engineers spend about 40% of their time on bugs and slow deploys. Do we rewrite it this year, or keep patching?
Chief of staff
Your board is seated: The Engineer, The CFO, The Skeptic. They read the brief first, then research, then argue it out.
The EngineerTechnical Builder
The CFOFinancial Controller
The SkepticRisk Assessor
The board’s call
Don’t rewrite. Spend one quarter on the deploy pipeline and the three modules behind most of the bugs, then measure again.
40% of two engineers is about 0.8 of an engineer, every month. A rewrite would take both of them most of a year with no new features; a quarter of targeted fixes costs a fraction of that and tells you whether the monolith is really the problem.

The Engineer disagreed
“Patching buys you a quarter, not a codebase. If bugs aren’t down by half by March, plan the rewrite then, one module at a time.”
Example · Board of 3 · up to 135 credits


