Live data from Hacker News

Days without GitHub incidents

dayswithoutgithubincident.com

141–150 of 178 posts

Re: Days without GitHub incidents

#141
post #139
post #97

Earlier quoted context omitted.

Apparently so did everyone else. What was your point?

The comment I responded to said they felt bad for GH employees. I was saying I don't feel all that bad given they are well-compensated white collar workers (like many of us here). Life is pretty good if one's biggest concern is work stuff and you're not personally in danger or actively being harmed. That's all I'm saying.

[deleted]

Re: Days without GitHub incidents

#142

Earlier quoted context omitted.

I think the correct middle ground is a site that lets you select the parts of the platform you rely on and ignore the others. For example, GitHub is "down" for me when I can't push, process PRs, or release packages, but I don't care about Actions or AI features.

You’re kind of an outlier - nobody wants AI but Actions are core for tons of workflows and deployment pipelines. Everyone bought into the “only robots can deploy” mantra (correctly IMO, it’s a huge time and friction saver) only to be bit in the ass by the platform being so u reliable they can be stuck for days without deploys.

Thats kind of my point, everyone has a different set of GitHub features they rely on. Some people even want the AI bits.

Re: Days without GitHub incidents

#143

I don't think aggregating the whole platform into one number is fair. It's like adding the whole aws into one number

If S3, EC2, EKS and RDB alone had a similar uptime as all of Github right now, we'd all know.

No one cares that much if repo wikis, commit stats or gist had these issues. It's the combination of inter-dependent services that are used in combination, like PRs, actions, discussions, etc.

If one were to build a single percentage for each of these components of both systems, github would still lose. Maybe it's a few days without outages more but this isn't a comparison.

Re: Days without GitHub incidents

#144
post #122

Earlier quoted context omitted.

> I have. I skimmed your profile. Working on the infrastructure for a couple mid-tier video games is a cool accomplishment, but equating this to having solved GitHub level scale rings hollow. GitHub has a couple orders of magnitude more daily active visitors than the games you worked on had at their peak. You can make valid criticisms of GitHub without trying to reduce their scale or inflate your credentials to creat…

I'm not sure that resorting to personal attacks against the parent commenter for making a legitimate critique is the right, fair, sensible, or mature approach here. Discarding legitimate criticism based on some self-determined criteria of intellectual superiority isn't a good look. It smacks of elitism and isn't something conducive to a productive and positive community discussion. It is unhelpful, rude, condescendin…

The commenter inserted his own personal bona fides (as a proxy for skill, experience, and knowledge) and use them to bolster his conclusion of culpability and incompetence of the GitHub team. If you take that risk, you should expect to be challenged if those skills are not up to par.

Put more simply: if you get into the ring, you’d better be prepared to take a punch.

Re: Days without GitHub incidents

#145

Earlier quoted context omitted.

Let me ask the question in reverse: what do you have against them such that the fellow human beings struggling to maintain their operations don’t deserve even a modicum of kindness, respect, and good will? Are you unable to separate the business from the hard working people behind it? It’s not like they don’t know that people like us are counting on them: they recognize that their service is the “dial tone” for much…

OP didn’t blame the staff. His focus is on the company. Invoking individual workers well-being to defend a billion dollar company is also very strange.

A company is made of individual workers. That doesn’t change because there are a lot of them or that their employer has a lot of money.

Re: Days without GitHub incidents

#146

Earlier quoted context omitted.

Let me ask the question in reverse: what do you have against them such that the fellow human beings struggling to maintain their operations don’t deserve even a modicum of kindness, respect, and good will? Are you unable to separate the business from the hard working people behind it? It’s not like they don’t know that people like us are counting on them: they recognize that their service is the “dial tone” for much…

I have all the empathy for people in the world. A corporation is not a person. If your organization cannot handle the load, then you need to adjust your practices. The organization needs to prioritize their paying users. The organization needs to shift people from new features to keeping the lights on. And maybe the organization needs to find another strategy to manage its azure transition.

A corporation is made of people. GitHub cannot exist but for the people who continue to work for it. And they’ve already said, multiple times, that restoring availability is their top priority.

Re: Days without GitHub incidents

#147

Earlier quoted context omitted.

Let me ask the question in reverse: what do you have against them such that the fellow human beings struggling to maintain their operations don’t deserve even a modicum of kindness, respect, and good will? Are you unable to separate the business from the hard working people behind it? It’s not like they don’t know that people like us are counting on them: they recognize that their service is the “dial tone” for much…

#hugops is to your coworkers, not to the nameless big-corps who can't maintain a service for paying customers. You should be raising a shitstorm when things you pay for aren't reliable or unusable. Hot take, if it's traffic is causing issues, throttle your free-tier, pause signups, or stop giving out free things (like runner time).

Who is “maintain[ing] the service”? The workers, of course!

Re: Days without GitHub incidents

#148

Earlier quoted context omitted.

Would you consider telling this to the people working at GitHub directly? I’m sure they’d appreciate your evaluation of their skills and talent.

There are two options, either they are lousy at their jobs, or they are incapable of pushing back against unrealistic demands. Neither is a good indicator of their skill and talent as engineers. I know I am speaking from a position of some privilege, but I have previously left workplaces that did not allow me to practice good engineering, and I do expect others to do so.

Really? Only two possibilities?

Re: Days without GitHub incidents

#149

Earlier quoted context omitted.

OP didn’t blame the staff. His focus is on the company. Invoking individual workers well-being to defend a billion dollar company is also very strange.

A company is made of individual workers. That doesn’t change because there are a lot of them or that their employer has a lot of money.

If anything your argument against MS’s uniqueness makes OPs case stronger.

Re: Days without GitHub incidents

#150

Earlier quoted context omitted.

A company is made of individual workers. That doesn’t change because there are a lot of them or that their employer has a lot of money.

If anything your argument against MS’s uniqueness makes OPs case stronger.

Tell us how.
Post reply on HN