Chapter 65. Avoid Big Rewrites
Simon Aronsson
We’ve all been there in some form at one point or another. Our product owner has asked us how long it would take to enable our software to run serverless.
For the last couple of hours, you’ve been browsing the code, trying to make sense of it. But it’s just too old, too much of a patchwork. Layer after layer of added abstractions and cross-dependencies. Names of past engineers you’ve never heard of. It almost feels like you’re about to break the F12 key on your keyboard just repeatedly calling Go to Definition.
At last, tired and full of frustration, you give up. You go to your product owner and say that the shape of the code is just too bad. That it would require a total rewrite. Two days later, the product owner gets back to you and gives you the go-ahead. Full of excitement, you assemble the team to tell them the great news…
I’ve been in this situation enough times to tell you that your chances of taking on a task like this and succeeding are slim to none. Every time I’ve been part of a project like this, we’ve always come to regret it. Common outputs have included (although not been limited to) the following:
-
Not making deadlines
-
Going over budget
-
Introducing obscure bugs
-
Burning out team members
-
Losing stakeholder confidence
If the codebase is too complex or complicated to understand ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access