I was once at a meetup where a previous Twitter CTO gave a talk about their first rewrite. It was back in the day when Twitter was going supernova and their old

I was once at a meetup where a previous Twitter CTO gave a talk about their first rewrite. It was back in the day when Twitter was going supernova and their old Rails architecture was beginning to seriously struggle. The CTO came up with a new architecture, by complete fiat, and ordered that it be done HIS way. After one year of rewriting, the team realized that their new code would simply crash right away under load. Thankfully the CTO had some humility, learned from this, owned up to his mistake, and got another go at it. This is not going to happen with this doofus. There is a point in the life of a big company where a complete rewrite is basically business suicide. Might as well shut the whole thing down. Twitter is WAY past that point. And, obligatory Joel Spolsky link: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...