729
Merge then review (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by agilob@programming.dev to c/programmer_humor@programming.dev
145 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments
[-] zalgotext@sh.itjust.works 1 points 1 year ago

Get the value to production

Ugh, not this SAFe Agile (tm) cultist bullshit. The "value" is working, bug free code, which you get when you put it through review and QA before it gets to production.

[-] Mossheart@lemmy.ca 2 points 1 year ago

There is no value in spaghetti piled on top of rotten spaghetti. Tech iCal debt is real and if you're just shippin it and plan to fix it later, y'all gonna have a bad time. Nothing more permanent than a temporary workaround.

[-] Deifyed@lemmy.ml 1 points 1 year ago

There's often features and bug fixes worth more than the ones introduced in the PR. I've yet to see bug free code just because it's went through review and QA.

[-] zalgotext@sh.itjust.works 1 points 1 year ago

Surely you've seen bugs caught because code went through review and QA though. Those are bugs that would go into production if following the "advice" in this post.

[-] Deifyed@lemmy.ml 1 points 1 year ago

I'm saying identify the bugs through review, and fix them. Just do it in a new PR unless they are critical

this post was submitted on 14 Nov 2023
729 points (97.0% liked)

Programmer Humor

19623 readers
1 users here now

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

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev