this post was submitted on 14 Nov 2023

732 points (97.0% liked)

Programmer Humor

19551 readers

1038 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

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

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

732

Merge then review (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by agilob@programming.dev to c/programmer_humor@programming.dev

146 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 (1 children)

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