this post was submitted on 20 Dec 2024
176 points (97.8% liked)

Programmer Humor

19817 readers
54 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
 
all 20 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 8 hours ago

kagis 'C++ naming conventions'

[–] [email protected] 5 points 11 hours ago (1 children)

Having dealt with this drama before, and as team lead currently, as soon as this project began, the first thing I did was set up a linter with very specific rules. If a dev doesn't agree with the rules defined there, too bad. They're there to prevent this kind of drama, and to make peer reviews more focused and productive. I don't wanna see PRs about syntax. They're nearly always just a difference of opinion.

[–] [email protected] 2 points 11 hours ago

If I ever get around to writing my own language, it's going to take parse trees off the disk, so people can deparse them into whatever they want and STFU.

[–] [email protected] 1 points 10 hours ago* (last edited 10 hours ago)

When I was a mod on Reddit we had a slack channel, one of the new mods got outed and shamed for a post where they were a dick at a show, the sub turned on them so we had to remove them, the head mod scolded them while we were all silent watching, it felt like we were kids hiding on the top of the stairs watching a sibling get scolded.

[–] [email protected] 5 points 1 day ago* (last edited 1 day ago)

Oof. This is a pet peeve of mine.

As manager, I shut this conversation down via direct messages to each team member involved.

I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.

I don't dictate much, but I do dictate that Slack isn't an acceptable place for this kind of discussion, on my team.

The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.

Alternately, if there's no strandard for this yet then my team knows they're encouraged to wing it until we discuss at next retro.

And yeah, I've had to open an issue to revisit a variable name after retro, lol.

My team are an opinionated bunch, and they're often perfectionists.

[–] [email protected] 12 points 1 day ago

Let me tell you: I’m currently developing a user-defined, recursive form, and most of the trouble with that stems from the fact that I don’t have a good name for the repeatable part of that form (as opposed to a static part) and the thing the form is embedded in.

Variable names do matter.

[–] [email protected] 6 points 1 day ago

I just use UUIDs

[–] [email protected] 3 points 1 day ago
[–] [email protected] 19 points 2 days ago (1 children)

I'm just gonna say it: fuckYourCamelCase

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

Proudly thinks that __M_fs_stdbuf_t is perfectly readable.

[–] [email protected] 13 points 1 day ago (1 children)
[–] [email protected] 5 points 1 day ago

Instructions unclear. You have been assigned: ǿ. You now owe a million Danish kroner.

[–] [email protected] 15 points 1 day ago (1 children)

Only if it stands for motherfuckers standard buffet.

[–] [email protected] 7 points 1 day ago

A buffet of underscores maybe.

[–] [email protected] 4 points 1 day ago

I don't get this meme at all... What am I expected to see in this picture? Or how am I supposed to interpret it?

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

$goddamnitJeffStopChangingMyFuckingVariableNames = 1;

[–] [email protected] 3 points 1 day ago

One day I will see this drama... Until then, it will remain only in memes.

[–] [email protected] 8 points 2 days ago

Missed opportunity to title post in the style of bad variable name.