Is it me, or did get issues get a lot worse with the transfer to MSFT?
If I were to bet, there's probably a product manager or other leader who's just gung-ho on new features and loosing track of who their customers are and what their needs are.
They don't/didn't care because what are you going to do?
On one hand, the free users shouldn't complain too much, though I get their anger. But the place I work is an enterprise paying customer and this is bullshit.
But the vibe coding BS probably made it 10 times worse.
Yup, keep seeing this in various companies. Teams that were effective and did solid engineering now are more effective and does even better engineering. Teams that were effectively already just "boilerplate monkies" now produce a lot more code than before, but the quality is the same so effectively they're worse at contributing now than before, and take more shortcuts, not less.
From my point of view, agents are amplifiers, so if you usually build spaghetti projects, agents just help you do that faster, not avoid the spaghetti altogether. If you usually build well-designed stuff, they can help you put that together faster.
The acquisition was 8 years ago.
Add in them being extremely high scale and critical infrastructure and it's easy to see where things can go wrong, vibe added code or not. I think we'd all prefer they have long slow roadmaps but clearly leadership thinks they're in a fight with the other AI companies to release the newest and bestest every day.
Embrace, extend, and extinguish.
What exactly are they extinguishing GitHub to the benefit of? Azure Repos?
The original red dog team that started azure is long gone and the general success of the cloud papers over all levels of incompetence so that the incompetence is now entrenched and unable to do better.
Cloud service providers have this unfortunate property where poor designs will make more money which makes it hard to maintain a culture of excellence. I tried to push a design change that would result in a 10x throughput for a certain product and was told that a 90% drop in usage is the last thing they want. I self host my own stuff with GitLab, so far not a single unplanned outage in 6 years.
Perhaps a Roman decimation is in order, whenever GitHub experiences an outage fire one GitHub employee at random. That should help get interests in line and allow for cross org cooperation. With 150 outages per year and a staff of 6,000 that amounts to 2.5% per year if no improvements are made.