this post was submitted on 02 Oct 2023
1544 points (98.4% liked)

Programmer Humor

32558 readers
511 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago (1 children)

I stated programming games on a school computer in the early to mid 80's. When the tape drive broke, I still used to have the code in my head, just type it all in for others to play. Now I find code I wrote last month and can't remember doing it. At least it tends to be, "which genius wrote this" these day. Tend to leave comments everywhere for myself now, including my own name and other messages to myself like,"don't touch this it works, your bug will be in..."

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago) (2 children)

Yeah, I'm about the same age and started noticing my ability to keep everything in memory falling at around the mid 20s. I mean, I'm still probably way better at keeping all manner of obscure details in memory compared to the average person (we exercise that so much in this profession it's only normal), but it's below the peak point, not enormously so but it's kind like having once been a top "athlete", years later you know you can't reach that peak performance anymore.

Also once you go through the full life-cycle of enough of your projects (that got shipped and a year or two later you have to pick it up and change it), you kinda figure out that even at peak "performance" you wouldn't be remembering much from a project from years ago and start adding comments to help you pick it back up and alert you to possible pitfalls you noticed and avoided but forgot all about in the meanwhile.

Fortunally I figured it out long ago that I've created a couple of principles around commenting that have repeatedly saved my ass years later: things like documention parameter assumptions in functions, actually writting down the "why we do this" or commenting before the code of especially complex algorithms (I actually design the algorithm to the comment first and only after than code it).

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

Yes, very similar practices here.

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

@ProfessorPuzzleCode @Aceticon

Oh ruck. At twenty I could remember the direct way through the Zac Mc.Kracken Mazes. And all the chords of our Bands songs. And all the Beatles lyrics. But heck... no code.... now I at least remember the bash scripts.....

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

I started a practice with my team on our wiki. We have a section named the Oamonomicon, since out system is named OAM. Any sort of weird one off request or problem gets documented there. What were the symptoms? What steps did we use to find the problem? Then if we start seeing a pattern of issues, we have a better idea of how to resolve them.