Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don’t let code become stale.

1 point

It can work if you have a test zone and only a small amount of people work on a given code base.

Also checks to ensure the code compiles and tests pass before merging, as some quality gateway.

permalink
report
reply
1 point
*
Removed by mod
permalink
report
reply
4 points
*

Something like that happened to me yesterday. I reviewed one PR, then some Important Guy came in and said:

  • it is nice you reviewed my work, but we need to push this to production right now.
  • just fix these things, I described you how. Just copy/paste these snippets
  • these are cosmetics, I don’t care
  • “cosmetics”, huh? Your shit may just crash
  • gfy and push this to production right now
  • well, ok

Of course, lack of these “cosmetics” caused crash in production. It’s my fault of course.

permalink
report
reply

“Xtreme programming practices”.

Lmao what!

permalink
report
reply
12 points

Bet you $50 we later learn this guy was orchestrating a supply chain attack.

permalink
report
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 1

    Monthly active users

  • 256

    Posts

  • 842

    Comments