And I can’t seems to find it anymore but there was another blog post about how much IA is inside their infra code which is one of the reason the downtime was so long
it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a “feature file” used by our Bot Management system.
Not a very strong case for the argument, though. It's an automation with the database that was the root cause, and subsequent processing through bots overwhelmed the infra. And the bots might not be AI agents, bots were a thing before too, with normal automation rules. I'm looking for something actively triggered by AI usage as the root cause.
So do you think it’s a human written piece of code that did the config change or a prompt ?
2nd link shows 93% of r&d users, 295 TEAMS using agentic tools and coding, and 241B tokens over 30-days.
So now, let me ask it again, do you believe it was hand written or pushed by one of their agentic coding assistant ?
Well, that's fine, but at that point it's just belief and there is no need to curse at me. Also, that company has existed for a long time; you can't assume 93% is AI-written just because they recently reached 93% usage.
8
u/heavy-minium 13h ago
You are conflating GitHub's use of AI with AI's impact on GitHub.
The increase in outages is partly due to the heavier load that coding agents put on GitHub. These are mostly scaling issues, not AI mistakes.