251–260 of 280 posts
Earlier quoted context omitted.
React apps with SSR is standard these days.
SSR that is javascript native, sure. This is still Ruby doing the rendering.
If you are doing 1000 commits a day, whats the point of git? Does the AI ever look back at the shit trail it left behind? Diffs are no longer diffs, they look like largescale delete and rewrite
Github used to be built on mysql / redis / ruby on rails / C / shell, running on dedicated hardware. Microsoft left it like that after they acquired the company. Eventually, though, they decided to migrate the whole thing to Azure. And they were far enough through that to be basically committed... when AI coding started hitting them with much higher workloads. I personally think the reliability problems are more to d…
They didn't leave the architecture alone, right? They shoved React in and created a weird SSR + React frankenstein that is objectively worse in many ways.
Ex-Microsoft, ex-GitHub, laid off nine months ago, not going to violate any agreements, but I will give some context. A lot of this applies to any large engineering org, really. Hilarious that this entire thread is people speculating on things they have no idea about. If it sounds like I'm defending GitHub a bit, yeah, I am. I can't think of a comparable situation that any other web site has been through. This isn't…
Android
Youtube
Waymo
Chrome
Workspace
GCP
>Which amazing developer tools from Google do you use regularly?
Kubernetes
Jax
Tensorflow
gRPC
Go
Istio
Earlier quoted context omitted.
I mean they may be working around the clock, but after 5 or 6 layoffs in 3 years… half their engineers are probably still learning the code base.
I don’t think their engineers « learn the codebase » anymore, that’s so 2025. It’s all agentic now, the model learns the codebase, the engineer ask the agents to do their best and believe in themselves
This behavior is what led them to the current situation and will only get worse.
Earlier quoted context omitted.
More load does not just mean needing to increase capacity, which would be simple for Microsoft to do. Additional load reveals limits and breaklines that were never known before - your temporary integer IDs are suddenly too small, you reach the maximum file descriptors in a Linux distro, your hash function suddenly has repeating conflicts, your DB index is suddenly oversaturated. Having massive exponential growth of y…
A good rule of thumb I once heard (from Jeff Dean, I think) was that (in a complex system) every 10X you go up in scale you need to re-consider basic design elements, trade-offs, etc, and probably change some of them. It's hard to design something (large and complex) for much more than 10X scale with only HW capacity increases.
Github is struggling because AI-boosted coding increased the number of commits 14x in the past year, and the pace is still accelerating. The site is struggling to keep up. Github's COO confirms it here: https://x.com/kdaigle/status/2040164759836778878 Platform activity is surging. There were 1 billion commits in 2025. As of three months ago, it was 275 million per week, on pace for 14 billion this year if growth rema…
Github is struggling because AI-boosted coding increased the number of commits 14x in the past year, and the pace is still accelerating. The site is struggling to keep up. Github's COO confirms it here: https://x.com/kdaigle/status/2040164759836778878 Platform activity is surging. There were 1 billion commits in 2025. As of three months ago, it was 275 million per week, on pace for 14 billion this year if growth rema…
GitHub’s reliability issues started earlier than the boom in agentic coding they talk about. I have comments on here from 2025 talking about massive outages with actions and issues.