And so the grand experiment begins. I feel bad for the folks losing their job because that always sucks, and I hope there's a decent severance package. Now we'll see what happens to Twitter... I hardly use it, so if it implodes it won't bother me too much. But I am curious to see if all the "how do you need X people to do Y?" commenters are correct in this case. The app is simple but doing simple things at scale is h…
> The app is simple but doing simple things at scale is hard. I wonder if we'll see more downtime and issues now. So, here's what I've never figured out... Once your app is built, and you've figured out how to scale it, and everything is autoscaling nicely, and you've reached the critical mass Twitter has...why do you still need all the engineers? Why do you need to keep growing? At some point, isn't the scaling solv…
Re: Twitter’s mass layoffs have begun
#881Once your app gets to that level, even keeping the lights on requires work. Third party dependencies don’t stop updates, security or otherwise. Laws and regulations change. Advertisers demand features that aren’t seen by the general public. Multiple SRE teams are needed to handle oncall rotations, outages, etc. And now that you have thousands of employees, you need to start building automated HR and IT tooling.