|
> Is 16h of downtime acceptable for a $44b business? After a 70% reduction in headcount, is a 16 hour downtime acceptable in a 5% market? I'm going with yes, executives from all major corporations are itching to press that button if only they could get away with it. The problem with Twitter is not, was not, and will never be a technical one. It's a simple site with a simple tech stack, using standard technology to scale. The problem with Twitter, and what Musk doesn't seem to understand, is a sociological and political one. Social networks are the crack cocaine of tabloid media, left to the whims of bad actors they can destroy democracies, incite lynchings, distribute hate and misinformation on scales without historical precedent. "Free speech" just doesn't cut it, social networks are publications not mediums, they chose what people get to see and react to, and the fact that the choice is made by an algorithm does not absolve them of responsibility for the consequences, especially if the algorithm is tuned for revenue maximization and easily gamed by bad actors to spread their content. By firing the watchers, Musk is setting Twitter up as an menace to stable democracies around the world. |
But the current staff needs to maintain code from a MUCH larger staff. That's hard. Especially with microservices where every team did "their own thing" and some teams just vanished completely. You have "dark areas" where no one knows how stuff works and what's going on.
Normally when you downsize at this scale you do this in an orderly way. Every person hands off their work and responsibility. Spends a couple of weeks writing docs and instructions and then leaves. This was done quickly and violently. I'm sure there's many repercussions we don't see simply because the systems are simply running. Once the team looks at some containers and decides to pull the plug to "see what happens" we'll find out...