Comment by qrush
2 days ago
I got an "it is unacceptable" from their CPO on 8/7, and that they are "working around the clock on it".
https://x.com/mariorod1/status/2085800861469495465
I really think something deeper is going wrong there, and they're not being honest with their paying customers (and enterprises) about it.
The reality is that it's probably a skill issue. Scaling a mature platform 10x can be a really, really hard problem, they obviously don't have their arms around a solution, and are probably spending a majority of their time on ops to keep the bleeding down. In the old days you would have Jeff Dean come down from heaven and invent a new database for you or something like that. It doesn't really seem like Github has that kind of technical ability, so they're probably trying to cobble together Azure ops with internal bandaids while everyone internally is cranking out AI code and it's just not going to be enough.
May I just leave this for you here? https://isolveproblems.substack.com/p/how-microsoft-vaporize...
A technical foundation is not infinitely strong. Put a big enough castle on a swamp, and it will sink into the swamp.
This is nightmarish.
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
Which is why my colleague pushed fix after fix but still failed at addressing the root cause of a bug. Turns out outsourcing all your thinking to a machine that doesn't truly understand your system yet hallucinates isn't going to work.
Yeah, and the rest are probably not quite so invested.
I wouldn’t be surprised if that tweet response you got was written by an LLM