Programmer Humor

19623 readers

8 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

[email protected]

708

Merge then review (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

141 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

[–] [email protected] 1 points 1 year ago (1 children)

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 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.

[–] [email protected] 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