this post was submitted on 28 Nov 2024
485 points (98.8% liked)

Programmer Humor

32604 readers
240 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] _____@lemm.ee 23 points 4 days ago* (last edited 4 days ago) (3 children)

> someone nitpicks word you used in a variable declaration

> you change it

> someone more senior says the former made more sense

> this goes on for far longer than it should

> eventually you get a real review from someone in your team that identified something actually needs to change

> you change it and re request reviews

rinse and repeat

[–] projectmoon@lemm.ee 8 points 4 days ago (2 children)

Had a team lead that kept requesting nitpicky changes, going in a FULL CIRCLE about what we should change or not, to the point that changes would take weeks to get merged. Then he had the gall to say that changes were taking too long to be merged and that we couldn't just leave code lying around in PRs.

Jesus fucking Christ.

There's a reason that team imploded....

[–] lord_ryvan@ttrpg.network 4 points 3 days ago (1 children)

Had a colleague who would comment things like “add a newline here” as well as things that were fully his own preference.

That was the only time I closed comments without replying to them or fixing them, without feeling bad.

[–] projectmoon@lemm.ee 4 points 3 days ago (1 children)

For stuff like that, it's best to have an auto formatter like checkstyle or something.

[–] lord_ryvan@ttrpg.network 1 points 3 days ago

My point exactly! But naw, several others on the team insisted this guy policing others manually is better than putting a linter in the pipeline.

I don't work there anymore, this is one of the (minor) reasons.

[–] UnrepententProcrastinator@lemmy.ca 1 points 3 days ago (1 children)

People need to lameduck their code more

[–] zalgotext@sh.itjust.works 2 points 2 days ago

People need to reply to those comments with "out of scope" and a link to a new issue that will get buried in the backlog more often

[–] mac@lemm.ee 4 points 4 days ago

Don't forget get questioned by your manager/scrum lead as to why its taking so long to get out.

Well, I've had the PR ready for 3 days and the team asked me to make changes today

[–] Skullgrid@lemmy.world 2 points 4 days ago* (last edited 4 days ago)

you forgot the part where you have to rebase your branch and that causes merge conflicts that were resolved later but somehow still persist.