727
Merge then review (programming.dev)
submitted 2 years ago* (last edited 2 years ago) by agilob@programming.dev to c/programmer_humor@programming.dev

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
[-] dbilitated@aussie.zone 2 points 2 years ago

I just made a github action that merges anything updated in master into feature branches automatically. you get pinged if there's a conflict but the automerge keeps drift to a minimum so it's less common and fixed sooner.

better than merging poorly tested/reviewed code.

and yeah, a small team of superstars doesn't need reviews so much, but most teams have a range of devs with different levels of experience and time working with particular parts of a large codebase. Someone more senior or more expert derisks people picking up tickets and improves code quality.

it also leads to plenty of good conversations about the best way to implement, so overall it's a win.

this post was submitted on 14 Nov 2023
727 points (100.0% liked)

Programmer Humor

25457 readers
1013 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