Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

Post reply on HN
Print view View original

101–110 of 175 posts

Re: Red Squares – GitHub outages as contributions

#101

Post by linsomniac »

dijit wrote: post #76
u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…

>not intellectually curious or open

This checks out. I once was at a conference where they (Azure) had a giant booth. A fairly well known person in the community brings me over to talk to his manager who is working the booth. "We should hire him, he's really smart." Within a minute of talking to this manager he says "You're a Linux guy? We do Windows." and physically turns away from me, conversation over. You know, fair enough, was an easy way to find that it wasn't a good fit. But the lack of curiosity about "what do you bring to the table" was pretty stunning.

Be curious.

edit: Clarifying "they"

Re: Red Squares – GitHub outages as contributions

#102

Post by everfrustrated »

xyzzy_plugh wrote: post #92
__natty__ wrote: post #57

Contrast between official [0] and third party status pages [1] is huge. How their terms of service for SLA are legal if they are so different from real world usage of their product? I really like GitHub and their services but every time when it’s broken and their status page is green something screams inside me. [0] https://www.githubstatus.com/ [1] https://mrshu.github.io/github-statuses/

Their terms of service are legal because their terms of service require YOU, the CUSTOMER, to track their availability against the agreed upon SLA and to pursue credits when they break their SLA. At a recent gig we experienced many, many GitHub outages that were not tracked on their status page, and we kept a log (i.e. just search in slack). After our business people argued with our account executives at GitHub we go…

This. We talked to our account reps and engineering folks at GitHub - they had no monitoring to track if they had kept their end of the contracted SLA.

They expected us to log any faults and as you say the process wasn't worth it - even with massive outages - just for a few beans in credits.

GitHub has low availability simply because it doesn't cost them and they wear no legal or contractual damage from it.

If a competitor came to me and said, we will _pay_ you damages for the time your developers are offline not able to use our product to do their jobs, we would sign up immediately.

Re: Red Squares – GitHub outages as contributions

#105

Post by someguyiguess »

linsomniac wrote: post #101
dijit wrote: post #76

Earlier quoted context omitted.

> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…

>not intellectually curious or open This checks out. I once was at a conference where they (Azure) had a giant booth. A fairly well known person in the community brings me over to talk to his manager who is working the booth. "We should hire him, he's really smart." Within a minute of talking to this manager he says "You're a Linux guy? We do Windows." and physically turns away from me, conversation over. You know, f…

If they were curious they wouldn't "do Windows"

Re: Red Squares – GitHub outages as contributions

#107

Post by traverseda »

whirlwin wrote: post #103

We just invested a lot migrating 300+ pipelines from Azure DevOps to GitHub Actions. What a bummer timing-wise. Anyone got an alternative to GitHub Actions?

You can run your own github actions compatible-ish server. https://github.com/nektos/act

Personally my favorite is probably drone-ci.

I'd suggest not buying in too hard on any one of these CI systems and just writing shell scripts. Shell scripts are portable, and you can use whatever to trigger them.

Re: Red Squares – GitHub outages as contributions

#108

Post by weird-eye-issue »

u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

I don't think people generally care what the exact reason is it's more about there being any downtime in the first place

Also it's not a fair comparison because it's not necessarily the same code between the public and Enterprise...

Re: Red Squares – GitHub outages as contributions

#109

Post by everfrustrated »

rufo wrote: post #62
bharxhav wrote: post #6

Would be interesting to see if this correlated with their release cycles.

At least as of when I left the company, GitHub was being deployed to fairly close to once every 60-90 minutes (the frequency of a deploy train/merge queue batch going out) 24 hours a day, at least during weekdays… there are a fair number of international engineers and deploy trains get crowded during main US business hours, so while there are fewer PRs going out at odd hours US time, there were typically still some.…

Would love to know more about how they deployed their monolith. If you have anything to share or public links about it.
Post reply on HN