Comment by kelnos
15 hours ago
> Over 1 billion monthly users and over 100 billion messages a day, much of which is multimedia. Plus ads, payments, business integrations, a developer platform...
Right, but it's already doing that, and runs just fine, from what I understand. The developers don't have to sit there pounding the enter key on their keyboards over and over all day to keep the messages flowing.
Is the user count and message rate growing so quickly that people are constantly needing to make architectural changes and performance improvements in order to keep it scaling up? Does adding new capacity need constant human intervention?
Or are they adding new crazy features all the time that are genuinely challenging to implement?
As a software developer who has worked on big distributed systems, I'm well aware that things take a lot more work than they often seem from the outside, but this strains belief.
> It has panned out for Musk to have a radical right-wing echo chamber for him and his supporters.
I suspect this was the goal all along. Twitter didn't have to grow revenue/profit-wise; those two metrics could even decline, and Musk would be happy. He just needed to find a side-business for Twitter to get into (which turned out to be AI datacenters) that could make some cash to help keep the lights on. The point of owning Twitter wasn't the business; the point was for Musk to be able to control discourse in exactly the way he wanted.
> Right, but it's already doing that, and runs just fine, from what I understand. The developers don't have to sit there pounding the enter key on their keyboards over and over all day to keep the messages flowing.
It “works fine” precisely because there’s a lot of engineers pounding the enter key.
This is really just basic stuff, when you serve literally billions of users worldwide, you need a lot of people just to keep everything going smoothly as more and more people adopt it. Software doesn’t just magically scale to arbitrary usage and what made sense to build 5 years ago may no longer be the correct architecture today.
> Right, but it's already doing that, and runs just fine, from what I understand. The developers don't have to sit there pounding the enter key on their keyboards over and over all day to keep the messages flowing.
> Is the user count and message rate growing so quickly that people are constantly needing to make architectural changes and performance improvements in order to keep it scaling up? Does adding new capacity need constant human intervention?
> Or are they adding new crazy features all the time that are genuinely challenging to implement?
> As a software developer who has worked on big distributed systems, I'm well aware that things take a lot more work than they often seem from the outside, but this strains belief.
IMO based on working on not-that-large-or-high-revenue systems, but ones where these things already applied, a bunch of it is probably a combination of three things:
* You're doing enough total revenue that a couple million a year to fund a team of engineers to try to make tiny marginal improvements in ad revenue through targeting, or new features on how to present ads, etc, can still easily pay for itself.
* You're running at a high enough scale / spending enough on resources that you can similarly justify spending millions on teams to knock more millions off your infra costs.
* You've got enough usage/users that making tiny improvements in bug rates/crashes/etc similarly results in more usage that more-than-pays-for-itself. (And the list of bugs to squash is possibly never-ending if those other groups keep changing things!)
"Why make 30M profit on 100M revenue when you can make 35M profit on 115M revenue" sorta thing.