> The truth about the Twitter layoffs is that the company is not even remotely profitable and likely never will be, so it doesn't really matter that much as long as the company barely continues to operate.
But it was profitable at certain times. Despite all the reported "bloat". Ironically now, it has little hopes of being profitable thanks to advertisers pulling out due to lax moderation (some of the automated stuff no longer working because the maintainers are gone!). So even if they managed to run the site with a skeleton crew, assuming they keep breaking non-essential features, it's unclear they could ever become profitable again.
There seems to be this echo chamber around the Twitter acquisition that thinks most software companies are bloated and that software engineers basically do nothing. They seem to believe Twitter will make that demonstration. It's particularly pervasive in semi or non-technical circles. I guess it's the same crowd that bought into no-code and low-code tools to "get rid of expensive developers" for the last decade.
While Twitter hasn't suffered any complete outage as of yet, several products and features seem to be broken, as well as a good chunk of their API (I don't buy the claim it's intentional because the latencies and error rates have been jumping up). To be completely honest, this level of service degradation would have killed more serious products. It's fine for Twitter because there's no SLA, no enterprise customers and no critical infra running on it.
But it was profitable at certain times. Despite all the reported "bloat". Ironically now, it has little hopes of being profitable thanks to advertisers pulling out due to lax moderation (some of the automated stuff no longer working because the maintainers are gone!). So even if they managed to run the site with a skeleton crew, assuming they keep breaking non-essential features, it's unclear they could ever become profitable again.
There seems to be this echo chamber around the Twitter acquisition that thinks most software companies are bloated and that software engineers basically do nothing. They seem to believe Twitter will make that demonstration. It's particularly pervasive in semi or non-technical circles. I guess it's the same crowd that bought into no-code and low-code tools to "get rid of expensive developers" for the last decade.
While Twitter hasn't suffered any complete outage as of yet, several products and features seem to be broken, as well as a good chunk of their API (I don't buy the claim it's intentional because the latencies and error rates have been jumping up). To be completely honest, this level of service degradation would have killed more serious products. It's fine for Twitter because there's no SLA, no enterprise customers and no critical infra running on it.