725
Merge then review (programming.dev)
submitted 10 months ago* (last edited 10 months 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
[-] Mossheart@lemmy.ca 18 points 10 months ago

have the author address issues after the merge.

Hahahahahahaha. Sorry, you've merged, next ticket, PM needs shiny results for execs this QBR!

This is how bug backlogs grow.

[-] SmoothLiquidation@lemmy.world 5 points 10 months ago

This exactly. By the time they notice a problem you are three tickets down and on to the next sprint.

[-] Deifyed@lemmy.ml 3 points 10 months ago

Yeah, I see your point. Maybe my employers are different, it's never been an issue explaining why the ticket isn't closed just because the PR is merged

[-] karmiclychee@sh.itjust.works 2 points 10 months ago

Oof, I felt this

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

Programmer Humor

19301 readers
1007 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