Sure, backseat commenting is easier and I wouldn't wanna be in charge at github right now, but on the other side there also a reality where we'd see video essays about githubs downfall because their reliability crashed so hard that businesses could not trust them and moved to competitors / self hosted instances which then meant less paid users to subsidize the ever growing demand of the free users.

Yes it's potentially a write-heavy workload which also needs to be consistent aka the worst case scenario.

The easy solutions like caching and read replicas don't work and you're forced to go the route of sharding or similar techniques that have much more painful tradeoffs.

I'm not sure if that's why everything keeps breaking but at that scale write-heavy workloads are never going to be easy