14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others!
An interesting thing I notice now is that people do not like companies that only post about outages if half the world have them ... and also not companies that also post about "minor issues", e.g.:
> During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes.
That's for sure not perfect, but there was also a 95% chance that if you have re-run the job, it will run and not fail to start. Another one is about notificatiosn being late. I'm sure all others do have similar issues people notice, but nobody writes about them. So a simple "to many incidents" does bot make the stats bad - only an unstable service the service.
I know you are joking but I'm sure that there is at least one director or VP inside GitHub pushing a new salvation project that must use AI to solve all the problems, when actually the most likely reason is engineers are drawing in tech debt.
Upper management in Microsoft has been bragging about their high percentage of AI generated code lately - and in the meantime we've had several disastrous Windows 11 updates with the potential to brick your machine and a slew of outages at github. I'm sure it might be something else but it's clear part of their current technical approach is utterly broken.
<mermaid>
flowchart TD
A["Claim: Bridge opening is conditional"] --> B["Actor: Donald Trump"]
A --> C["Project: Gordie Howe International Bridge"]
A --> D["Condition: Canadian concessions required"]
B --> E["Public statement"]
C --> F["Status: not opening (per claim)"]
D --> G["Type: policy/trade concessions"]
E --> H["Outcome framing"]
F --> H
G --> H
H["Message: No opening unless concessions are granted"]
</mermaid>
<mermaid>
flowchart TD
A["Claim: Bridge opening is conditional"] --> B["Actor: Donald Trump"]
A --> C["Project: Gordie Howe International Bridge"]
A --> D["Condition: Canadian concessions required"]
B --> E["Public statement"]
C --> F["Status: not opening (per claim)"]
D --> G["Type: policy/trade concessions"]
E --> H["Outcome framing"]
F --> H
G --> H
H["Message: No opening unless concessions are granted"]
</mermaid>
When I first typed up my comment I said "their current business approach" and then corrected it to technical since - yea, in the short term it probably isn't hurting their pocket books too much. The issue is that it seems like a lot more folks are seriously considering switching off Windows - we'll see if this actually is the year of the linux desktop (it never seems to be in the end) but it certainly seems to be souring their brand reputation in a major way.
Honestly AI management would probably be better. "You're a competent manager, you're not allowed to break or circumvent workers right laws, you must comply with our CSR and HR policies, provide realistic estimates and deliver stable and reliable products to our customers." Then just watch half the tech sector break down, due to a lack of resources, or watch as profit is just cut in half.
All the cool kids move fast and break things. Why not the same for core infrastructure providers? Let's replace our engineers with markdown files named after them.
I'm happy that they're being transparent about it. There's no good way to take downtime, but at least they don't try to cover it up. We can adjust and they'll make it better. I'm sure a retro is on its way it's been quite the bumpy month.
Copilot is shown as having policy issues in the latest reports. Oh my, the irony. Satya is like "look ma, our stock is dropping...", Gee I wonder why Mr!!
[1] https://www.theverge.com/tech/865689/microsoft-claude-code-a...