Skip to content

Instantly share code, notes, and snippets.

@jmewes jmewes/ Secret
Last active Mar 18, 2019

What would you like to do?
The Big Rewrite Warnings

One answer that many companies try is, "Oh, we just rewrite it. Maybe it's in Cobol, maybe it's in Java, but it is not in one of those new trendy languages like Go or NodeJS with JavaScript. So we'll rewrite it." And the answer is that that almost always fails. And there is a specific term for it: The second system syndrom... -- Dan Kohn

  • Almost all the successful microservice stories have started with a monolith that got too big and was broken up
  • Almost all the cases where I've heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble. --

And this is why big rewrite projects are difficult and hard to accomplish correctly. I advise not to even do them. (...) -- Chad Fowler

As a general rule, you should never rewrite your software. I have (barely) survived several rewrites in the past and they all shared the same horrible experience: ... --

I have seen this happen over and over again. Big Redesigns in the Sky almost always fail horribly. Horribly! HORRIBLY!! -- Robert C. Martin

The problem of big rewrites is that they are a technical solution to a cultural problem. -

Why You (Probably) Shouldn’t Rewrite Your SaaS Product - A Cautionary Tale. This is our experience of building and launching Proposify 2, and the painful lessons learned in the process. --


This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.