Coincidentally happens on the new CEO's first week.
It doesn't rely on him running it, it just runs under his UID.
A widely distributed authentication/security process does an internal healthcheck by looking up 'jbezos' on the datastore. A few hours ago someone disabled the jbezos user.
fun fact jeff's employee id is like 72 or something while still being the lowest as they didn't reset the oracle sequence once they got that system working after testing but before making his user.
I've stopped being surprised when I encounter some configuration file somewhere with a comment: "TODO: Fix this later" and it turns out more than half the business relies on that thing being configured that way.
Even at companies who do have the money and technical resources to do things right, things get forgotten, or pushed back on.
So, while these are problems that are unlikely, I'm sure I'm not the only one wondering... "Did they have something dumb like this, too?"
Again, a joke, but I've seen stuff fail in other dumb ways because of some assumptions that were made about things that never change (until the day they do).