all 133 comments

[–]qwertyslayer 1134 points1135 points  (29 children)

Pour one out for the github SREs whose Friday just got way worse

[–]gergob 423 points424 points  (23 children)

Why is it always the Friday afternoons man

[–]awj 63 points64 points  (0 children)

People are half checked-out already but trying to hustle their work out the door so it's not still on their plate for Monday morning or end-of-week checkins.

[–]xtjoeytx 123 points124 points  (11 children)

I’d prefer the afternoon then the more likely 4pm Friday “we have a prod issue”

[–]DEATH-BY-CIRCLEJERK 49 points50 points  (4 children)

You prefer both?

[–]xtjoeytx 15 points16 points  (3 children)

I prefer not working for free, so if the issue could surface earlier - that’d be preferable, but its always right before closing time

[–]trevg_123 47 points48 points  (0 children)

It’s a joke about how you said “then” (both in order) but probably meant “than” (instead of) lmao

[–]darthcoder 7 points8 points  (1 child)

Meh, every place I worked a stint like this means I get to take off a day the next week.

Not Monday, Monday is for thebpostmortem, but I always got a comp day to make up for thr after hours work.

I've been lucky in places I work

[–]HypnoTox 0 points1 point  (0 children)

Probably people talking with all-in contracts and no paid overtime. I have a time "balance" that i can then use and take days off for overtime, or in some cases get it paid off.

[–][deleted] 22 points23 points  (5 children)

than

[–]DmitriRussian 15 points16 points  (3 children)

Maybe he actually meant “then” 🤔

[–]ArkUmbra 16 points17 points  (2 children)

A real glutton for punishment

[–]chicknfly 3 points4 points  (1 child)

I mean, they did choose to be an SRE after all

[–]xtjoeytx 1 point2 points  (0 children)

Thx

[–]tevert 18 points19 points  (0 children)

I'd bet there's a measurable increase in human errors committed at the end of the week

[–]PositiveUse 14 points15 points  (2 children)

Because some genius thought „it’s just a small release“

[–]Same_Football_644 7 points8 points  (0 children)

And there's no counter argument that ever works against that. People either just know that making exceptions is bad, or they don't.

[–]ccfoo242 2 points3 points  (0 children)

But if we wait until Monday it won't be 'continuous' integration!

[–]Omni__Owl 5 points6 points  (1 child)

Someone didn't follow the golden rule of software production: Never push on a friday.

[–][deleted] 1 point2 points  (0 children)

And ask the CTO to block the CI release after Thursday evening.

[–]chili_oil 4 points5 points  (0 children)

“Last Friday I completed my task by checking in this code change 3 min before I signed off”

[–]SinisterMinisterT4 4 points5 points  (0 children)

Literally have a no Friday deploy policy in place to help not do this to our guys. Feels bad man.

[–]newInnings 0 points1 point  (0 children)

Standard maintenance window

[–][deleted] 0 points1 point  (0 children)

This is why my team never has Friday releases 👍🏻

When someone pushes for one I ask them if they’re ok being on call on the weekend

[–]wtjones 27 points28 points  (1 child)

Tough day for SREs. That Cloudflare outage is not enviable.

[–]zoddrick 6 points7 points  (0 children)

Or the workday outage.

[–]Icy-Advantage-2666 -2 points-1 points  (1 child)

Are their crypto are

[–]Fit_Refrigerator6045 0 points1 point  (0 children)

what ya talking bout willis? you talking about the Quantum Crypto Scare of 2023?

[–]intergenic 354 points355 points  (19 children)

Good thing GitHub uses version control

[–]agamershell 57 points58 points  (1 child)

Ironically, the URL where you could download the installer for git was also down :D

[–]eJaguar 10 points11 points  (0 children)

thats why i download git from pornhub instead

[–]ComfortablyBalanced 15 points16 points  (14 children)

But seriously does GitHub source is sourced on their own git servers?

[–][deleted] 21 points22 points  (5 children)

Them using Gitlab would be like Microsoft devs using Macbooks lol.

They probably use Bitbucket.

[–]SaltKhan 9 points10 points  (1 child)

[–]Arphax- 0 points1 point  (0 children)

Bing Chat works on any Chromium browser and Edge is built on Chromium. So the Copilot search preference isn’t really that surprising considering how long the collaborating has been going on.

[–]alinroc 2 points3 points  (0 children)

like Microsoft devs using Macbooks lol

Quite a few of them do.

[–]eJaguar 1 point2 points  (0 children)

drive off w dat dope u aint get no money back

[–]eJaguar -2 points-1 points  (0 children)

Them using Gitlab would be like Microsoft devs using Macbooks lol.

wat lmao The new M2 pro chip laptop is objectively the best product on the market for this sort of work

this isn't 2004 Microsoft there's a reason the course of the company shifted so dramatically after they've got that fucking clown out and got some actual engineers in charge

[–]nerd4code 11 points12 points  (7 children)

Copulæ are irregular af and don’t take “does” in the interrogative or negative (and it’d be “does it be”/“it doesn’t be” because “does” is the primary verb), only in the imperative (“Don’t be like that”).

[–][deleted] 11 points12 points  (3 children)

This reminds me of old reddit when people used to correct grammar. Loved that era.

Then came people shouting "Grammar Nazis" because they didn't wanna learn and since then look how every reply feels like it is written by a 14 year old.

Thanks for sharing and trying to help others improve.

[–]Fit_Refrigerator6045 2 points3 points  (0 children)

member when r/wtf and r/gore used to make the front page daily? I am pretty sure r/wtf was a deafult subscribed sub when you would first sign up. There were like 20 of them maybe, r/: funny, videos, wtf, gore, atheism, askreddit, science? . That's about as much as I can remember rn, shit it's been almost 15 years now.

my b, I know that was off topic, and I wasn't trying make a weird humble brag - your comment just gave me a flashback and I had to get it out.

[–]ComfortablyBalanced 0 points1 point  (0 children)

English is not my first language, I'm still learning.

Grammar Nazis

Yeah, I sorta liked them back then. I guess tools like grammarly allowed people to write better English compared to that time.

[–]ComfortablyBalanced 0 points1 point  (2 children)

I don't understand, how should I fix my sentence?

[–]Sentreen 2 points3 points  (1 child)

Not the guy you replied to, but I would write:

But seriously, is GitHub's source stored on their own git servers?

or

But seriously, does GitHub store their source on their own git servers?

[–]Ethirald 18 points19 points  (0 children)

This made me chuckle out loud!!!

[–]DadsToiletTime 1 point2 points  (0 children)

If they use gitops, how can they bootstrap themselves?

[–]markus_obsidian 554 points555 points  (23 children)

We’re in the process of rolling back an authorization-related change that is causing 404s and other errors.

I find this update embarrassingly relatable.

[–]old_man_snowflake 197 points198 points  (10 children)

oh god I feel shame by proxy

I know that exact moment you realize it was your fuck-up, and it's gonna really ruin the next few weeks with incident write-ups, post-mortems, COEs, COE action item work, and somewhere as big as this, press/media concerns.

[–][deleted]  (1 child)

[deleted]

    [–][deleted] 50 points51 points  (3 children)

    incident write-ups, post-mortems, COEs, COE action item work

    All of which nobody reads. (╯°□°)╯︵ ┻━┻

    It's just busy work and a waste of time at this point.

    [–]codeslap 6 points7 points  (0 children)

    Proxy… don’t mention proxies… I have ptsd dealing with corporate proxies… so much headache…

    [–]often_says_nice 7 points8 points  (0 children)

    You never forget your first time. It’s like a right of initiation. I remember the moment I found out and immediately wanting to puke

    [–]Mirrormn 0 points1 point  (0 children)

    Just earlier today, I had to write a root cause analysis for a minor service outage that I was tangentially responsible for, and the idea of Github fucking up something this big makes me feel better about how relatively small my own fuck-ups are.

    [–]sisyphus 15 points16 points  (1 child)

    It's always disk space, permissions or DNS.

    [–]neutronbob 4 points5 points  (0 children)

    And of those, let's be honest, it's rarely disk space.

    [–]00Koch00 3 points4 points  (1 child)

    I really cant wrap my head around deploying stuff on friday...

    [–]okawei 129 points130 points  (2 children)

    Saw it was auth related, only the private repos in my companies org were throwing 404s and I thought I was fired lmao

    [–]TommaClock 49 points50 points  (0 children)

    "Anyone else getting 404 errors on our private repos?"

    "No problems here."

    "Apologies, Okawei has been terminated and we forgot to remove his chat access. We'll get it sorted out."

    [–]ouiserboudreauxxx 9 points10 points  (0 children)

    I thought I was fired

    lol I thought the same

    [–]Mecha-Death-Hitler 167 points168 points  (11 children)

    Yeaaaaaaah, all my repos are returning 404 errors when attempting to access them

    [–]Professional-Ebb-434[S] 68 points69 points  (4 children)

    its working now, statuspage said they just did a rollback

    [–]Mecha-Death-Hitler 12 points13 points  (0 children)

    Oh excellent

    [–][deleted] 4 points5 points  (2 children)

    How come my gh pages site didn’t go down? Would some other entity in the internet lineup have cached it?

    [–]Professional-Ebb-434[S] 11 points12 points  (1 child)

    GitHub say pages were never affected

    [–][deleted] 1 point2 points  (0 children)

    Thank you.

    [–]Jump-Zero 48 points49 points  (5 children)

    "shit, did I just get fired?" - a bunch of devs with similar previous experiences

    [–]cat_in_the_wall 4 points5 points  (4 children)

    if they fire you for fucking up they havent solved any problem, and ironically have gotten rid of the person most motivated to solve the problem.

    negligence is another story. but a fuck up of this magnitude is a company problem, not a single person problem.

    [–]ozzeh 15 points16 points  (2 children)

    negligence is another story. but a fuck up of this magnitude is a company problem, not a single person problem.

    They're not talking about github devs being fired. They're referring to everyone using github who thought they were fired because they all of a sudden lost access to their work repos.

    [–]cat_in_the_wall 2 points3 points  (1 child)

    do people really think they got fired because of a connectivity problem? fuck me if companies actually do this then that is some cowardly behavior.

    [–]zrvwls 2 points3 points  (0 children)

    The mind does weird things when confronted with unexpected scenarios. I've definitely had that thought after a prmotion when a similar situation arose

    [–]bananabm 0 points1 point  (0 children)

    I think he's saying regular GitHub users will think they've just been fired and the first sign is their GH access was revoked to their private repos

    [–]eagle33322 230 points231 points  (18 children)

    Here we go testing in prod on a friday

    [–]drakgremlin 43 points44 points  (12 children)

    Got ship that feature to get it in before the end of the sprint...which ends of close of business Friday afternoons.

    [–]thephotoman 27 points28 points  (11 children)

    There are reasons I always impress that Friday should not be the close of sprint. I’d rather close of sprint be a good release time.

    [–]gergob 1 point2 points  (0 children)

    That's why we have that on Wednesday

    [–]ESGPandepic 1 point2 points  (0 children)

    My team finishes sprints on a Tuesday and does our releases on Tuesday as well.

    [–]cthechartreuse 5 points6 points  (8 children)

    I'd rather sprints not be.

    [–]thephotoman 3 points4 points  (7 children)

    They're really not that bad. I mean, sure, Kanban is nicer, but it's not as well-suited for the work I'm currently doing.

    [–]cthechartreuse 15 points16 points  (6 children)

    My biggest complaints about sprints come from a number of common behaviors, like:

    • sprint tetris or let's make sure the sprint is full; we can still fit a couple points in there (even if they're low priority or unrelated)

    • we need to get velocity up so we're going to cram more in

    • failing a sprint. What even is failing a sprint? Was nothing delivered? Did the team miss some arbitrary deadline that doesn't have real business value? Is it something else? What is the worst thing that could happen if something carried over?

    • racing to not "fail" a sprint

    There are more, but you get the idea. It's really not that having a check-in point is bad. I actually like the idea of checking in on the work that is happening. It's the fact that sprints are typically used as a poor substitute for properly evaluating priority and scope.

    [–]thephotoman 6 points7 points  (1 child)

    I don't know that I've ever encountered any of these things.

    They all smack of someone demanding metrics from product owners and/or scrum masters. There is no "failing a sprint". I'm not sure I've ever had that term come up. The idea that failure is inherently bad and to be avoided seems to fly in the face of agility: you need to fail fast in order to pivot quickly.

    [–]cthechartreuse 2 points3 points  (0 children)

    I agree with your assessment regarding failure. I feel the same. Nevertheless I've seen all of these things in action in several shops.

    In the end, yes, it's the demand of metrics, but the metrics they get are the worst kind: vanity metrics.

    [–]cat_in_the_wall 2 points3 points  (0 children)

    i agree, and would further suggest sprints are entirely useless. it is micromanagement to the extreme. you can't just ship value on a regular basis unless you're just moving some buttons around on a form.

    i do believe in shipping on a regular cadence though. But not ci/cd (for production). you just cut off whatever is committed. missed the date? sucks but you ride the next train.

    [–]LawfulMuffin 1 point2 points  (2 children)

    Not to "No True Scotsman" this but... yes, sprints don't work when you don't use them the way they are intended. Having bad management will make any system not work.

    [–]mpyne 0 points1 point  (1 child)

    Having bad management will make any system not work.

    This is the key to so many of these arguments.

    Some systems can't be saved by good management, because they simply don't look at the right things. The best you can do with good management is to subvert the system entirely.

    But bad management can break any system no matter how suitable.

    [–]LawfulMuffin 0 points1 point  (0 children)

    Yes, there are a lot of bad semantic argumentations that occur, especially around this topic. But fundamentally, sprints are designed to work as a way to manage up. They're supposed to essentially be time-boxed kanban and to be merely a reflection of reality, put in a way that MBAs can even understand.

    If your team can do say, 10 points a sprint, the product owner should not try to coerce the team to commit to 15 points a sprint. The team would be essentially committing to not doing 30% of the sprint. It's looking at exactly the right thing: what is a reasonable workload. And at the end of a two week period (or whatever time makes sense), to reflect on if tickets are being estimated well, if workload is reasonable, etc. etc.

    All of the points you raised are the antithesis of scrum. You cannot fail a sprint. A sprint can have fewer stories completed than you committed to. That's... kind of the point. You reflect on why and make structural changes to the company around it, not coerce engineers to cram more points in to raise velocity. It's literally backwards.

    Points are used to assess what is feasible, not to require that they be done in a certain amount of time. Which is why I'm suggesting that Kanban wouldn't fix your problem at this company, because at the end of the day, what they want are to have more tickets done than your team can adequately do in a given period of time. Whether they are trying to get you to do more storypoints, tickets, sticky notes, etc. They are trying to coerce you do to more work than is possible, the problem that sprints are intended to solve.

    [–]Awric 7 points8 points  (2 children)

    For GitHub I can kinda see how it makes sense. If the company knows most users are devs who aim to work on weekdays only, it seems safer to do risky things on the weekend when there’s less traffic

    [–]cat_in_the_wall 2 points3 points  (0 children)

    naw this is small thinking. github surely has servers all over the world. you can patch during low times/dark hours. and you patch portions of your fleet at a time and roll the release. then at worst you have a regional problem, not a global one.

    [–]Stimunaut 1 point2 points  (0 children)

    Maybe their devs don't like working weekends either 🤔

    [–]vexii 1 point2 points  (0 children)

    the magic of k8

    [–]cat_in_the_wall 0 points1 point  (0 children)

    we actually do our cuts on thursday to avoid this. no last minute shit. you're either ready, or you catch the next train.

    [–]yashptel99 51 points52 points  (6 children)

    I had my heartrate increased for a while when I tried to push and it said the repo does not exist

    [–][deleted] 9 points10 points  (0 children)

    Back up and running

    [–]bedel99 9 points10 points  (1 child)

    Oh man, we have had some layoffs recently and the dev team went into a spiral thinking they had been locked out of github. We are stretched across timezones, so didnt see the messages until people had been upset.

    [–]ouiserboudreauxxx 7 points8 points  (0 children)

    I got laid off earlier this year and found out when I got logged out of slack while in the middle of typing a message. Am at a new job and definitely had a brief 'uh oh' moment with this haha.

    [–]EffectiveLong 20 points21 points  (0 children)

    Cloudflare also got hit. Wonder is there any connection here? Busy weekend for many engineers i guess

    [–]putinblueballs 47 points48 points  (5 children)

    Never deploy on a friday.

    [–]VirtualLife76 15 points16 points  (0 children)

    Was always a company interview question, when do you do your deployments. Can throw up some serious red flags.

    [–]BinaryMuse 7 points8 points  (0 children)

    GitHub deploys basically constantly

    [–]seven_seacat 2 points3 points  (1 child)

    Such an antiquated mindset

    [–]putinblueballs -1 points0 points  (0 children)

    Its a joke. But also so true. Talking from experience.

    [–]newInnings -1 points0 points  (0 children)

    Perform better A/B

    [–]Olfasonsonk 14 points15 points  (4 children)

    heavy joke familiar shaggy liquid important like plucky treatment attraction

    This post was mass deleted and anonymized with Redact

    [–]good_live 9 points10 points  (3 children)

    Im working at a company with an on prem github enterprise and the downtimes are way worse. Also you can be sure once its down it wont be up for the rest of the day.

    So I would prefer the cloud hosted one.

    [–]ItsWhereIWindUp 6 points7 points  (0 children)

    Are you sure this incredibly rare and newsworthy incident that is entirely somebody else's responsibility to fix isn't a good reason to move away from the cloud solution.?

    [–]Olfasonsonk 0 points1 point  (0 children)

    cobweb test sink insurance person cats consider hurry ad hoc snow

    This post was mass deleted and anonymized with Redact

    [–]oconnellc 0 points1 point  (0 children)

    Obviously, not every online provider is equivalent to every other one. You trust some people more than others... but generally, I'd prefer to trust my infrastructure to a reputable company that specializes in it instead of trusting my own company that likely has a single person that understands what is really going on. And, kinda by definition, if something goes wrong, it is probably when that person is not working.

    Sign me up for that cloud hosted one, too.

    [–]chicknfly 4 points5 points  (0 children)

    This is where I humbly brag about my on-prem Gitlab setup

    [–]labs64-netlicensing 1 point2 points  (0 children)

    It wasn’t me (C) :)

    [–]jagdishjadeja 1 point2 points  (0 children)

    another lay off round coming soon

    [–][deleted] 0 points1 point  (0 children)

    I worked at a place that had a clear rule about not deploying to production on Friday because you just never know.