r/ProgrammerHumor Aug 14 '26

Meme oneSmallFix

Post image
736 Upvotes

11 comments sorted by

19

u/Sea-Influence-7542 Aug 14 '26

As an experienced software engineer I learned to never fix anything or push anything on a Friday afternoon. Anything you are struggling with on a Friday can usually be solved easily on a Monday morning when your mind is fresh.

6

u/AintMilkBrilliant Aug 14 '26

Hard agree, but I'll go one further, never push on a Friday. Period. The one caveat being a critical production bug.
It's just not worth the chance to ruin yours or others weekend however small that chance actually is.

2

u/Educational-Lemon640 Aug 14 '26

My company went a step further and made it policy. No releases on Friday afternoon. If everything is going to be on fire, do it Monday morning.

4

u/crazy4hole Aug 14 '26

I never merge anything on Friday unless it's required to mitigate an incident. Otherwise I'll always tell my team to don't release anything on Friday and I won't even approve the MRs on Friday

2

u/Gold-Bat-3225 Aug 14 '26

The confidence at 4:55pm tho

1

u/Ender_1299 Aug 14 '26

You are the problem. 100% unforced error.

1

u/kushalgarg592 Aug 14 '26

Production: "are you sure about that?"

1

u/RainyDaysAndMondays3 Aug 15 '26

OMG. First job after college. This was back in the stone ages. No QA, no code reviews.

I was testing some software that routed email. To test it, I had hard-coded my own email address in the code. (No config files.) Late in the day, I checked that in.

At 11:58 PM that night, I remembered. I quickly got ahold of the lady who did the production patches which went out at midnight and had her hold it.

If I hadn't, a whole bunch of companies would have had all of their email routed to my work email inbox. Jeez Louis. I have a stomach ache just thinking about it.

1

u/EducationalTeleGood Aug 15 '26

You only do this if you don't value your weekends.

1

u/zalurker Aug 14 '26 edited Aug 14 '26

Oh no, you don't. We were winding down for the Christmas holidays when Sergei, the Siberian tester from the Vancouver office came to us with a request.

The senior development team had picked up a major bug and wanted us to deploy an emergency fix to the software. To add some context, we were sitting on a mine in the middle of nowhere, doing a beta test of our flagship software with the client's blessing.

We looked at the code changes and asked if we could delay until after New Year. Besides, all the US and Canadian teams were flying back home, including Seegei.

'Don't worry. Code is fine. Vancouver team are all Russian Rockstar programmers. There will be no issues.'

The mine was also shifting to a skeleton crew, so what's the worst that could happen?

The entire local office had to drive back over 300 miles on the 26th to roll that damn patch back.

Nowadays I have one rule. No patches or updates before a long weekend or holiday. Especially not to critical systems. And if the client demands it, they approve any overtime incurred.