696
top 20 comments
sorted by: hot top controversial new old
[-] vk6flab@lemmy.radio 44 points 5 days ago

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.

[-] Carighan@lemmy.world 7 points 5 days ago

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

[-] Horrabin@programming.dev 39 points 5 days ago* (last edited 5 days ago)

This is probably more accurate:

-Who the fuck wrote such a shit!

-WHO???

-...

-Oh... it was me...

[-] fayoh@sopuli.xyz 29 points 5 days ago

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.

[-] antimidas@sopuli.xyz 23 points 5 days ago

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

[-] Horrabin@programming.dev 6 points 5 days ago

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

[-] ulterno@programming.dev 5 points 5 days ago

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

[-] antimidas@sopuli.xyz 2 points 5 days ago

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

[-] stebo02@lemmy.dbzer0.com 22 points 5 days ago

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

[-] Appoxo@lemmy.dbzer0.com 5 points 5 days ago

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

[-] scutiger@lemmy.world 4 points 5 days ago

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.

[-] Appoxo@lemmy.dbzer0.com 2 points 5 days ago

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

[-] UnfortunateShort@lemmy.world 10 points 5 days ago
[-] DacoTaco@lemmy.world 12 points 5 days ago

Me during code reviews of other people

[-] Reptorian@programming.dev 9 points 5 days 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.

[-] danc4498@lemmy.world 6 points 5 days ago

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

[-] spartanatreyu@programming.dev 3 points 4 days 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

[-] diemartin@sh.itjust.works 4 points 5 days ago

s/year/week/

[-] MystikIncarnate@lemmy.ca 3 points 5 days 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)

[-] stubing@programming.dev 1 points 4 days ago
this post was submitted on 06 Mar 2025
696 points (98.9% liked)

Programmer Humor

21375 readers
444 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