I wholeheartedly believe that they could not have fixed it with 9,600 people months of work. They haven’t been able to fix it with many multiples of that.
> They haven’t been able to fix it with many multiples of that.
which may actually be the problem. I suspect that there is actually some ideal ratio that could be calculated of Input Fields / Dev, LoC / Devs, or maybe Unique Pages / Dev, or some mix of all of the above. Some of the metrics I hear out of places like airbnb absolutely blow my mind (>5000 engineers! wtaf are they all doing?!?). I can sort of see the #s at google, MS making sense given the breadth of the problems they are solving, but other places, not so much.
There was an interview with a lead tech at Uber about this some years ago, with the conversation starting with "why is the app so bloated!?" (in terms of megabytes) and his answer also answers your question:
The smooth and simple interface of the Uber app is the tip of the iceberg. His example was that their users don't (and won't) reinstall the app because they travel overseas. If anything, the time when you've just stepped out of an airport is precisely when you want the app to work smoothly!
The hiccup is that many countries have their own payment systems, Byzantine tax codes where this may or may not be displayed up front to the user (in various currencies and formats), there may be local laws around taxi-like services, etc... Some of those laws apply to areas smaller than a city, or may apply only to airport pickups, or the CBD area during congestion, so on and so forth.
The "core" app might be a simple thing that you can bang out over a weekend with an AI and a decent UI framework, but then you need to "draw the rest of the owl". Don't forget that there must be a matching app for the drivers! Different categories of drivers offering services that may be local to a region and totally absent elsewhere: rikshaws, tuk-tuks, taxi boats in Venice, and who knows what else!
AirBnB is very similar to Uber in this respect. They have to deal with about a hundred countries worth of law, often down to the state level. There's fraud detection. Customer support. Integration with travel agencies. Government-mandated reporting. Etc, etc...
You're assuming performance has been the core priority, or even a priority at all, and I think this is a bad assumption to make. I would estimate a much smaller number of people-months of work if I were you.
Dev users assume the only problem a product can solve is performance, when there is a lot more than that in reality.
Maybe in the past companies wouldn’t take the extra time for performance enhancements - but they’re apparently saying that AI is sooo good and speeds up work that they don’t need all of these extra people. So if their product was sped up it would enable their customers to work faster and lay off all of their extra employees (or just keep everyone and just do more stuff faster).
So are they doing this to make the product better or, as others have mentioned, they can’t innovate further and can’t grow their market so they need to cut costs.
They need to just clean slate start from skratch. I don't believe that code base can be saved.
AI means it's easy to copy any SAAS now right? so should be easy /s
which may actually be the problem. I suspect that there is actually some ideal ratio that could be calculated of Input Fields / Dev, LoC / Devs, or maybe Unique Pages / Dev, or some mix of all of the above. Some of the metrics I hear out of places like airbnb absolutely blow my mind (>5000 engineers! wtaf are they all doing?!?). I can sort of see the #s at google, MS making sense given the breadth of the problems they are solving, but other places, not so much.