[ruh-roh]

The "once they start trying to change things" aspect is where I'm most keen to watch.

Surely we have all been involved with large-to-small systems where we were curious how well/long they would stand up on their own without intervention. It's kind of fascinating to watch a real-world example, even though we likely won't get a lot of detail. But still, :popcorn_emoji:.

But what's getting somewhat-ignored in this discourse is they aren't changing anything. All deploys are frozen. And the new CEO has made a ton of promises about new features and policies. Eventually they need to roll those out, and once they do, damn... Even if they have strong automated tests, those generally only tell you that new code is functionally ok. Anything that crosses interfaces, deals with end-to-end integration, or adds new tables/dbs/jobs/etc that would eventually hit their scaling solutions - all could have catastrophic effects.

(And that ignores the consent decree stuff on changes too.)