303
Sorry (not sorry) (lemy.lol)
submitted 1 month ago by to c/iiiiiiitttttttttttt@programming.dev
11 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 26 points 1 month ago (2 children)

This shit annoys me.

The rule is "No change Fridays" and it has been for the last 30 years.

At least it has been wherever I've had the authority to do so.

You think I'm working the weekend, you can fuck right off.

Monday changes, then I've got a week to fix it.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 8 points 1 month ago

    The rule is “No change Fridays”

    Absolutely. Just yesterday I had a call with cow-orkers, we have an problem on the environment which is actually quite a big deal and we tried to find a solution. Turns out we need to do a major version upgrade on one of our systems in the pile. But as nothing was literally on fire it's a problem which can wait until monday. There's not many cases in our environment which says it's mandatory to do any changes at friday/over the weekend.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 month ago

    In my branche, we usually need to update and test on the weekend and be there at 5-6 in the morning to monitor production start...

    I usually like GoLives on Thursday because of the possibility to do actual changes/fixes on the weekend

    But... Just different branches

    When I worked with mobile apps, Friday updates always were shit, because of exactly the reasons you mention

  • permalink
  • fedilink
  • source
  • parent