Aside from the staffing changes, what unique insight do you have, that Elon Musk does't have, that makes you so confident that the platform is doomed? And so quick at that.
No system I've ever seen is 100% automated. Especially for occasional tasks eg. hot patching emergency security fixes or refreshing expired internal certificates.
When you have a big tech company with thousands of employees, the pareto principle comes into play in a huge way: proably only 10% of these people are actually doing any work that directly impacts the platform.
At least half the employees are probably not doing anything really useful. This applies even to tech companies with a mere 100 total employees. At 3000 employees it's probably even more so. Specially with the majority "working from home".
There are probably only about 10 key engineers who understand at a deep level how things are working.
On the other hand, Musk is bootstrapping a hardcode engineering culture where a lot of the platform can be implemented from scratch in a few weeks by top engineers if he can hire them, and I'm pretty sure he can.
His "Fork in the road" email is actually brilliant, many just don't realize it. He is good at making engineers a "high status class"; see this analysis by Samo Burja: https://samoburja.com/how-elon-musk-is-making-engineers-cool...
There are many top teir engineers who are eager to work for him.
From what I've seen, Elon's companies pay below-market for most roles. Levels.fyi indicates that, on average, engs take a 10-15% pay cut by deciding to work for Tesla.
I'm sure there are a handful of engineers that exist that could save Twitter single-handedly, but none that would do it for the pay he's offering.
This is the relevant part of the "Fork in the road" email:
> Design and product management will still be very important and report to me, but those writing great code will constitute the majority of our team and have the greatest sway.
Most companies put engineers _below_ design and product management: the designers and product people make decisions, and programmers just implement.
Once you're past the $120k/year mark does a higher salary matter that much really? It only matters if you don't find anything fulfilling about your job.
What would you rather?
$180k/year with great say over the product or $220k/year with little say on the product?
I stopped reading at this point.
Especially given it's highly distributed, fan-out architecture is not one that everyday engineers typically deal with.