Would the UX concept of a 'next page' even make sense if the content doesn't get read by the end user? What would an app that's mindful of the unavoidable technical limitations look like I wonder? I'm not familiar with the specifics at hand or what Musk can see, but from my perspective he has first hand knowledge of web dev and is smart enough to not be blinded by buzzwords and dogma. He seems to have earned a decent living from his approach don't you think?

If there's a problem sending too much data between back end services, perhaps there's just more data being sent than necessary. Perhaps there's some data usage costs or introduced latencies involved somehow?

I tried my best to fill in the blanks for this story, and my working understanding is this:

1) Client requests service. 2) Service is graphQL, which makes the "thousands of calls" Musk is referring to towards other backend APIs. 3) There was an incorrect international cache/CDN configuration which hurt response time of these APIs for some countries. 4) Musk claims its the API calls causing slow performance, engineers point out that its technically the cache.

Debate is about if using graphQL is even worth it if it needs such complex caching to work well

Perhaps local backbone telecoms correspondingly differ in capabilities from one locale to another?

That's part of it. He believes he'll be wildly successful regardless of domain expertise. He's so smart and anyone who questions or doubts anything he proposes is a worthless idiot.

There couldn't possibly be a good reason for things being the way they are, and he can't be arssed to stop and learn before loading and firing off a tweet from his gigantic ass cannon.

There must be a word for this.

It's an opportunity lost, if you ask me. Programmers and SRE people from Twitter, SpaceX, and Tesla probably could have learned a great deal from each other, had there been any attempt to bring the cultures together diplomatically.