Or maybe they need to bring back quality assurance expertise to the company.
replyYes that would be part of getting things under control, of course.
replyAnd/or move more contextually aware humans with 10K+ hours of hard won experience and fear of failure/sense of pride back into the loop.
replyI mean, if we're talking about "fixing" the symptoms of the downtimes rather than the sources and causes, I guess they could just null route github.com until they have things under control?
replyPersonally, I think they'd have more luck actually attacking the source, what that might be. Somehow I think Microsoft's push for "Every developer only use AI for development, no manual thinking/coding from now on" is the detrimental step, seemingly many companies are still discovering the right approach. Put a freeze to that, and I'm fairly sure you'd see less downtime pretty much immediately, unless all real engineers already left the company, I'm sure I would have at this point.
It’s not just their own slop that’s causing this, it’s also caused by the tsunami of slop being uploaded by vibe coders.
replyIf you want to upload to GitHub, you should pay. The days of charitably giving away compute for the “open source communities” are over.
Grandfather existing public repositories in, then cut it off. Stop the bleeding. It doesn’t have to be forever.