Hacker News new | ask | show | jobs
by 93po 896 days ago
> they've had a lot of downtime

Twitter is possibly the website most well known for downtime, and has been since literally the beginning. There's no real measure for whether it's true it's down more than usual lately, and sensationalist journalism and anecdotal reports from people with an axe to grind aren't really reliable.

The closest thing I can think of is looking at Google trends, which shows that "twitter down" is pretty consistent over the years:

https://trends.google.com/trends/explore?date=all&geo=US&q=t...

There's a spike in Nov 2022 when the layoffs happened, but again that's not indicative that it's especially bad - just that people were especially whiny about it or anticipating it would be bad

1 comments

This is what I find ... interesting about the engineering layoffs - was Musk right? Was there a large part of the engineering function at Twitter that was just existing on some mythology, and was in fact just not needed? If so, are the FAANG companies (and others) the same? Legions of engineering roles just bullshit wastes of $200K salaries plus share options and free pizza?

I utterly hate Musk, so firmly hope he was wrong. Just wish Xitter went down more.

> interesting about the engineering layoffs - was Musk right?

Yes and no. Twitter was started before so much of the common “web scale” Open Source projects existed. Cassandra, Kafka, Spark, Kubernetes, etc didn’t exist yet.

So versions of the aforementioned and then some were completely done from scratch at twitter, who has continued to maintain those projects despite them not being the premier open source offering in each of those categories. They also never achieved the scale of some of the largest tech companies where it makes economic sense to have say, a custom database or queue system.

Finally, Twitter has been using GCP for some of their new projects in the last few years, but they still had old legacy systems and teams to maintain that software, so they couldn’t fully reap the rewards of the cloud.

So, if you rebuilt twitter today you could likely do it for a fraction of the engineers they had at peak, by leveraging either cloud or popular existing OSS solutions. But that’s from scratch, not porting millions of lines of legacy code.

What Musk should have done was migrate various systems, then wind down teams. That probably would have worked, but been expensive in the short term.

So I think they cut too much, and I also think they honestly thought more engineers would be up for “hardcore twitter”, instead of quitting.

Musk forgot that all his very loyal Tesla employees may have also factored in their 10x RSU appreciation. It’s a lot easier to put up with insane working hours when your next years stock grant is 500k or million or something. Doesn’t apply at twitter.

Tl;DR: not a Musk hater at all, but he fucked up at Twitter.