392
you are viewing a single comment's thread
view the rest of the comments
[-] gerryflap@feddit.nl 16 points 1 day ago

Had this multiple times. Reading code from 2 years ago and being like "what idiot wrote this" only to find out the culprit was me. Then the memories came back and I remember why the compromises were made. What I learned from that is not to judge people too much on their code. What you see is a combination of both their skill and also a whole bunch of necessary compromises for which you may not know the reason. Nowadays I don't get too annoyed if the code is a bit messy. As long as it's well tested and documented.

[-] pageflight@lemmy.world 8 points 1 day ago

Yes — I think part of the lesson is to document the rationale and the compromises as much or more than the intended functionality.

this post was submitted on 12 Aug 2025
392 points (100.0% liked)

Programmer Humor

25681 readers
1404 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