this post was submitted on 27 Jun 2023
202 points (99.5% liked)

Programmer Humor

200 readers
2 users here now

wat doing

founded 2 years ago
 
top 14 comments
sorted by: hot top controversial new old
[–] [email protected] 13 points 2 years ago (1 children)

I hate places without code review. Makes me nervous as heaven to merge code and want as many double checks as possible.

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (2 children)

I feel this way about open source and the seemingly frequent lack of detailed code reviews. This one project had two function options to use from a library. One handles errors by returning them to the caller so they can be handled gracefully. The other, calls PANIC! They chose the latter and it causes a crash loop for a relatively easy to hit code condition that is sensitive to User input.

Why ask for unit test, in the code review, when you can just accept the contribution for a feature that is used in large corps.

[–] [email protected] 2 points 2 years ago

I will say I hate having to pester folks to do review on a merge. The place im currently at requires two and its pulling teeth to get folks to look at someone elses code. well except for me I always treat merges as priority as that is ready to go whereas with mine if I have not merged then its not that ready.

[–] [email protected] 1 points 2 years ago

Down with the corps?

[–] [email protected] 9 points 2 years ago

Found my Senior Engineer

[–] [email protected] 7 points 2 years ago

I hate code reviews because for whatever stupid reason my brain decides this is how it is.

I was at an XP shop for a few years before my current job and I forgot how much I hate code reviews because we were constantly pairing and didn't do reviews in the same way. Coming back to the standard sort of code review model has been torture.

[–] [email protected] 5 points 2 years ago

When I do code reviews it is a personal attack. I only suggest code changes on my enemy's pull requests.

[–] [email protected] 3 points 2 years ago (1 children)

@Lenguador

Code reviews are only bad until you realize you can just say "cool story bro" and move on.

No change is always an acceptable response to review comments imo, unless it's one of mine.

If you can't defend that turd of a code unit, why the hell do you think it deserves to go into production?

[–] [email protected] 1 points 2 years ago

Thanks for the advice, but I actually love code reviews.

[–] [email protected] 2 points 2 years ago

"I don't understand what these two lines of code do, could you please modify, explain, or document." is very different from "I don't like the semantics of this function, replace it with this other one that does something unrelated."

We've worked at both places, and one is useful, the other... not so much.

[–] [email protected] 1 points 2 years ago

oof this is too real lol

[–] MichaelobRegular 1 points 2 years ago

Not if you make your PR over 100 lines of code change in 1 commit. Then you get the good ol "LGTM" stamp

[–] WalkableProgrammer 1 points 2 years ago

You expect me to be wrong and not offended FFS /s

[–] [email protected] 1 points 2 years ago

What are you talking about? Of course it is! Real men don't do doc strings!

load more comments
view more: next ›