I know everyone is waiting for it to crash, and you may be right, but so far, stripping (hundreds of?) millions of cost out of the business seems to be have been a good strategy from a technical perspective at least.
Core services for Twitter have been throwing 500s a dozen times every few hours. [2]
Twitter performance for users in Australia has fallen apart twice due to what was found out to be someone losing access to a root certificate and mitigation delayed because the team that could fix it is no longer employed. [3]
This is far more than a few stability glitches.
[1] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
[2] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
[3] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
They launched Twitter Blue which was a disaster, then redid the timeline, which at best is a mild improvement, and they rushed out things that were already in development.
I'm not in the Twitter Death Cult camp, but I don't think we can judge new development based on the last four months.
The other 80% are focused on new product features, growing revenue, growing engagement, growing new user signups, l blocking bad actors and legal compliance.
Axing all of those roles could make it easier to ship valuable user-visible features, since the remaining engineers wouldn't have to work around feature flags for fifty ongoing experiments.