[turbonoobie]

This is becoming a regular occurrence by now..

I wonder if reliability has become less of a priority. As somebody with little to no experience of running things at scale I’m finding myself attributing this to some form of “move fast and break things”.

[geerlingguy]

Nobody remembers the unicorn days? Earlier in GitHub's history, it seemed like a weekly outage was the norm. You just kind of expected it and built workflows in ways where you had a backup path to your code.

Often git operations were unaffected though.

[qbasic_forever]

Given that the change happened in the mid-morning PST (timezone where GitHub HQ and most devs are located), I'm going to bet it's almost certainly something messed up from a regular update or deployment.

[tazjin]

I remember something after their acquisition about new offers being lower than what certain people had previously, leading to important staff members leaving. This and some other issue I can't quite remember ... it was probably posted on HN :)

[whoisjohnkid]

good point; I think they might be deploying big features on fridays? as of late I've noticed most of the issues I have seen happen on Fridays.

[usui]

Why would that be the case? Shouldn't it be more common to find deployments happening early Monday morning? It's common practice to avoid potentially bug-inducing changes right before the weekend hits

[bombcar]

If you’re trying to minimize impact to employees you deploy Monday or Tuesday morning.

If you’re trying to minimize impact to business customers you deploy Friday night.

[swat535]

Yea exactly , Tuesdays are the ideal days to ship features, this has always been the case everywhere I've worked. Deployments on Friday is just asking for pain and Mondays are often too chaotic for a release..

[SemiNormal]

Because they likely get a large number of users doing git pull first thing Monday morning.

[Florin_Andrei]

> I’m finding myself attributing this to some form of “move fast and break things”

That was the case when they were the small and hungry startup.

Meanwhile they've been acquired by a giant corporation with a less than stellar reputation for reliability or quality. So it's most likely a case actually of "move slow and break things".

[nix23]

>stellar reputation for reliability or quality

That is unfair Minesweeper never crashed, and the printspooler is not up for debate here ;)