this post was submitted on 18 Sep 2024
781 points (98.0% liked)

Programmer Humor

19315 readers
4 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
 
top 40 comments
sorted by: hot top controversial new old
[–] [email protected] 89 points 2 weeks ago (1 children)

Remove these blank lines.

I’m not seeing unit tests for this.

Unnecessary comment.

BLAM

Ow! Also, this could’ve been a smaller calibur.

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

The second one is very valid. Please do not waste my time without having a prove about your functionality.

[–] [email protected] 56 points 2 weeks ago (1 children)

LGTM (lunatic gunner targeting me)

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

it's me I'm lunatic gunner

[–] [email protected] 43 points 2 weeks ago (1 children)

I have either written or gotten a variant of every single one of these comments 🫠:

Please include the JIRA task in the commit title.

Did you run any manual testing?

Where's the PRD link in the commit message?

Can you please split this into multiple smaller commits?

Can you combine these two commits?

Did you email Jon about this because he's working on that project with Sarah and you might be duplicating efforts.

This should be named BarFoo instead of FooBar.

Why aren't you using CorporateInternalLib16 that does 90% of this?

Why aren't you using ThirdPartyPaidLibByExEmployee?

Why aren't you using StandardLib thing you forgot existed?

All our I/O should be async.

All our hot loop code needs to be sync.

This will increase latency of NonCoreBusinessFlow by 0.01%. can you shave some time off so we can push in feature B also?

Please add a feature flag so we can do gradual rollout.

What operational levers does this have?

Lgtm - just address those comments

[–] [email protected] 26 points 2 weeks ago (1 children)

I dunno, plenty of those sound pretty reasonable.

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

Mostly, yes.

I'd like to find a better way to phrase "why aren't you . . . " questions. It carries an accusatory tone in text, even if you don't intend that. The answer is almost invariably going to be either "I didn't know it existed" or "because reason X". Neither case justifies the accusatory tone. Maybe if the "I didn't know it existed" answer was something so basic that they really should have known it existed, but probably not even then.

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

My preferred variation of this is to make it an open question that leaves them in the position of authority, and assumes that they made a deliberate decision.

For example, instead of "Why aren't you using StandardLib that does 90% of this?", I would try "Could this be achieved with StandardLib? Seems like it would cover 90% of this".

[–] [email protected] 3 points 2 weeks ago

If you have seniority and they are a junior, some juniors do respond well to a senior having more knowledge about the codebase. With them, it can be beneficial to use a tone like "We have library X that seems like it could do a lot of the functionality here, unless you already took a look?" I know it's like 90% of the same but I know people who will just be shellshocked and just blindly say "yes" to any question you ask them, and I don't want a blind "yes" I wanna know the truth :) it also lets then explain why they didn't use it if they have a legit reason because hey, maybe I'm the one who needs to be caught up

[–] [email protected] 25 points 2 weeks ago (2 children)
[–] [email protected] 23 points 2 weeks ago

lunatic girl threatening me

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

Let’s gamble, try merging

[–] [email protected] 22 points 2 weeks ago (2 children)

"Did you run the formatter on this?"

Bonus points if it's python code and nowhere in the docs does it say which of the many formatters to use.

[–] [email protected] 4 points 2 weeks ago

Just make another PR where you add formatter instructions to the readme and pyproject.toml.

[–] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)
[–] [email protected] 5 points 2 weeks ago (1 children)

I'm fond of ruff lately. Pretty much the same as black, but it just comes with the linter instead of being separate tools.

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

👀 I’d fine-tuned (copied and pasted) a pylint setup that had some of black, what are the differences?

Edit: it’s so much faster than black, I’m switching

Edit2: used it today, faster and I like the linter. It also does some multi-line parentheses better imo

[–] [email protected] 18 points 2 weeks ago (1 children)

Just pull the trigger, we both know how this ends.

[–] [email protected] 4 points 2 weeks ago

Production errors.

[–] [email protected] 17 points 2 weeks ago (1 children)

The number of comments is inversely proportional to the size of the pull request.

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

Yet the review time is exponential with the size.

[–] [email protected] 8 points 2 weeks ago (1 children)

https://github.com/ZILtoid1991

Please, do pull requests on my projects! I might even accept them.

[–] [email protected] 8 points 2 weeks ago (2 children)

You realy want the D don't you

[–] [email protected] 6 points 2 weeks ago

gigachad_yes.gif

[–] [email protected] 6 points 2 weeks ago (1 children)
[–] [email protected] 4 points 2 weeks ago* (last edited 2 weeks ago)

All repos on the linked github account are written in D

[–] [email protected] 7 points 2 weeks ago (1 children)

i don't understand it, am i missing some context here?

[–] [email protected] 25 points 2 weeks ago

The meme format implies she catfished you with the promise of "Netflix and chill" at her house only to pull a gun on you.

In particular, she wants you to review and merge that goddamn pull request she made to your open source project repo two months ago that finally fixes that one really annoying bug.

[–] [email protected] 6 points 2 weeks ago

Look at that tiny numstat, I'll finish the review before the CI is even done

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

Takes on a slightly different meaning in the context of XZ utils

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

First problem is she's expecting a right boob like me to review her pull request. Second problem is I don't give a shit.

[–] [email protected] 4 points 2 weeks ago (2 children)

What is the original source material for the image and the name of the woman within?

[–] [email protected] 10 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

This is the artist, if you can excuse a link to X which I found on reddit via google.

...

I feel dirty.

Edit: Here's a KYM article. No idea why I didn't find it on my first sweep. It might have something to do with google being absolute dogshit these days.

[–] [email protected] 6 points 2 weeks ago

Thanks bro

Also I think that's Note wearing a TempleOS shirt in the background of this other post by the artist.

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

First version I saw of that one on twitter was about finding rare bugs in the wild. Which oddly fit looking at the PR.

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

Thanks, comrade

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

"Could you please rebase over main first?"

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

“No way this is merging with the main.”

[–] [email protected] 3 points 2 weeks ago