> This left a lot wondering what exactly was going on with all those engineers and made it seem like it was all just bloat. I was partly expecting the rest of the article to explain to me why exactly it wasn't just bloat. But it goes on talking about this 1~3-person cache SRE team that built solid infra automation that's really resilient to both hardware and software failures. If anything, the article might actually…
No matter if it was or not and for better or worse: If Twitter survives this without any major harm it will have profound consequences for the whole software industry.
That said, Instagram was run by just a dozen people back then, while it had hundreds of millions of users, right? So it's not a new data point.
Storing, retrieving, indexing, managing 280 char blobs (with links, threads, embeds) is not exactly the most hardcore of a problem domains.
Microblogs are the typical tutorial topic, and twitter's only "innovation" was to increase the text limit.