|
|
|
|
|
by ryandrake
681 days ago
|
|
I thought the company would collapse after firing 80% of staff, and for a long time I kept arguing that Twitter was still in the "Wile E Coyote ran off the edge of the cliff but didn't fall yet" phase where they were running on pure momentum. I must admit, as time goes by, it's harder and harder to argue that. I just can't believe that 80% of the company was really just not needed. Every company I've ever worked at was lean to the point where they almost couldn't get anything done due to lack of people. I can't imagine a company that could lose 80% of their people and keep on trucking. |
|
That's a pretty dramatic collapse.
The thing about Infra - is that if all you want is 99% uptime - that's, with reasonable architectural decisions - relatively straightforward. You can run with a skeleton crew (particularly if you make really smart Infra Decisions like Midjourney, Whatsapp, others have done an outsource 95%+ of your infra to a third party (Discord, Platform Messaging APIs).
As time goes on though, and you go through incident review after incident review, and sharpen things up - and 99% becomes 99.9% you start to get diminishing returns on more Infra Employees - at some point they don't add much reliability value (but boy do they make pager rotation schedules pretty nice).
My sense (from both interviewing and working with them) is that the vast majority of people fired/laid off from Twitter weren't (for the most part - definitely lots of exceptions) core engineers or core infra-people -they were people on the periphery associated with making Twitter a friendly place for advertisers, and just maintaining a healthy work-life balance for the Infra people - a job where you could work your 30-32/hours week without it becoming all encompassing.
When they were fired, Twitter became a very unfriendly place, and the advertisers ran away, and the revenue crashed.