955
Peer reviewing is torture now
(lemmy.nz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Sep 2026
955 points (98.7% liked)
Programmer Humor
33210 readers
383 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 3 years ago
MODERATORS
You know, you could just chunk it up in a way to keep it readable.
for a new feature request? a PR isn't a commit, it's a set of commits which would add to the line change amount.
Like even if you spread it out across 20 or 30 commits that's still going to be the same line count.
I guess you could push not yet functional or used code to lessen the line count change, but that seems in bad taste. I've always gone off the working repo should always be in build or clean state and a push or commit shouldn't break that.
I work in a Scrum team and we implement features iteratively, so we start with the minimal feature, merge it, get feedback, and go on from there.
At work there's no excuse to keep a feature in a stale branch until you accumulate 1000 lines of code change.