31–40 of 61 posts
Earlier quoted context omitted.
Microsoft management/engineering practices+AI slop.
I get that, but all of that was in there for quite some time though, no?
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added): > users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with . Put simply, a user on a 99% reliable smartphone cannot tell the d…
This has gotten to a point where it doesn't really matter anymore. When a service crosses a certain reliability threshold it's like a phase change. The customer base eventually adapts to the situation. Anyone who still genuinely cares has moved to self hosted enterprise or something else by now. It was most tenuous for me when they almost met the SLA. Now that they've blown so far beyond it, the stress is mostly gone…
I care but I can't move out because it's Orders from Up High which migrated us to Github. We haven't been here a year and it's not worth my neck to mirror our code in some kind of skunkworks forge instance. Woe. Woe is me.
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added): > users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with . Put simply, a user on a 99% reliable smartphone cannot tell the d…
Sure they can. If Google loads and Github doesn't, then it's clearly Github being down, not the mobile network.
Also not everyone uses a phone. My desktop & fibre internet has way better than 99% reliability.
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added): > users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with . Put simply, a user on a 99% reliable smartphone cannot tell the d…
I think there's 3 big themes with this, thought not
1. LLM tools have added considerable load.
2. LLM used by developers to increase velocity seem to be leading more outages. This calls into question the increased velocity.
3. Roadmaps focused on pushing features that aren't reliability problems. i.e. github moving to azure, or adding AI features.
All these same problems happen to orgs with other fads that aren't AI. Following fads is not good engineering.
The Google SRE book offers the following as one of the reasons to not gun for 100% reliability (emphasis added): > users typically don’t notice the difference between high reliability and extreme reliability in a service, because the user experience is dominated by less reliable components like the cellular network or the device they are working with . Put simply, a user on a 99% reliable smartphone cannot tell the d…
At a guess, I could imagine some sort of failure of cached pages, which can be cached for signed out users but probably not for signed in users (as the rendered HTML would need to have user context like their avatar etc)
What's going on with GitHub lately? I've never seen them having so much issues over the years as they do have now.
Microsoft management/engineering practices+AI slop.
I k ow for a fact that ANY other platform would fail faster than github if they had the same volume of http requests.