this post was submitted on 06 Mar 2025
700 points (98.9% liked)

Programmer Humor

21564 readers
2445 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
 
top 20 comments
sorted by: hot top controversial new old
[–] [email protected] 44 points 1 week ago (1 children)

Accurate, except the bottom right panel only happens in very limited circumstances, hardly ever after a year has passed.

Source: I've been writing software since 1983 or so.

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

Yeah same, also I don't usually need a year to think that. The next day often works. πŸ˜…

[–] [email protected] 39 points 1 week ago* (last edited 1 week ago) (1 children)

This is probably more accurate:

-Who the fuck wrote such a shit!

-WHO???

-...

-Oh... it was me...

[–] [email protected] 29 points 1 week ago (1 children)

Me at a previous workplace.

-This is a piece of shit, who is the code owner of this module.

  • Ah, it's me ("inheriting" code ownership when someone left was common)

  • Who did this change

  • Ah, it was me

  • Surely I just made a minor change to this line here, who wrote the function.

  • it was me, it was me all the way down

Fits the general theme of the thread as it was not giving any trouble for a year before being found.

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

The more frustrated you are when running git blame the more likely the command turns out to be a mirror.

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

This is where the programmer's way to humbleness starts :-D

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

Last time that happened to me, it was a mirror, but also not.

I had moved functions from one file to another without changing the contents. As a result, all those lines referred to me.

And since I started thinking, I found this

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

Good link that, I'll have to add those flags to my list of aliases

[–] [email protected] 22 points 1 week ago (1 children)

And I always think I write good comments until a year later I'm like these comments don't help shit

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

Try to write as if you are explaining the functionality to an unrelated 3rd party like a new hire.

[–] [email protected] 4 points 1 week ago (1 children)

Yeah, write it for the person who has to replace you when you inevitably get laid off so that your company can hire someone for half your salary.

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

Don't be a dick to your (current) co-workers.

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

Me during code reviews of other people

[–] [email protected] 10 points 1 week ago
[–] [email protected] 9 points 1 week ago

Sometimes, I just rewrite my code until it is good enough. Other times, I leave it to my memory, so I can figure it out later. And others, I'm just not happy about it, like the times I did bigbin2dec and it would only work well with something like thread-ripper.

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

There’s an exponential amount of time between each panel. 1 hour, 5 hours, 2 days for the answer.

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

s/year/week/

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

This is why you're meant to comment your code.

Your code tells you "what", your comments tell you "why".

Here's a good review of comments in the redis codebase: https://antirez.com/news/124

[–] MystikIncarnate 3 points 1 week ago

To be fair, this is also me when I look at a network setup years later. (I do IT with a specialty in networks)

[–] [email protected] 1 points 1 week ago