734
Merge then review (programming.dev)
submitted 2 years ago* (last edited 2 years 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
[-] Deifyed@lemmy.ml 1 points 2 years 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 2 years 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 2 years 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
734 points (97.1% liked)

Programmer Humor

25448 readers
1001 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 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev