Programmer Humor

The entire purpose of writing good readable code which is mostly self-explanatory and were it isn't it's properly commented to explain what's going on, is so that it it's not a necessary for the person who picks it up later to be somebody who does remember what that code does and how it does it.

Whilst this is mainly important to allow other people to work in that code, as a side effect the actual person who wrote the code if they follow those coding principles needs not remember what it does and how it does it.

One of the upsides of being a senior dev is having figured this kind of thing out from experience, which offsets the downside that since you're older and have done a ton of things, it's less likely that you will properly remember the details of a specific code base after some months of not looking at it.

In a more serious note, that's why you document your software!

You dont. Thats why you write comments!

My first tech job out of college, I was told to go talk to "Dave," the guru old-timey programmer and learn the lay of the land. He turned out to be this crotchety old guy, with low tolerance for idiots, but a soft spot for someone who actually paid attention.

A few months in, I was told to go fix a feature in the company's main product which was sold to power utilities. This was a MASSIVE code base, with a mix of C, C++, assembler, and a bit of Fortran thrown in. I spent a week poring through all the code trying to figure things out. Then I hit a mystery workflow that didn't make sense.

I walk over to Dave's office and ask a specific question. Now, mind you, he had worked on this years ago, and had long moved on to new products. He leans back in his chair, stares at the ceiling, then without looking at the screen once tells me to go look at such and such file for such and such variable, and a list of functions that were related. I go back to my desk and damn if it wasn't EXACTLY as he described.

Now, I'm probably as old as he was then. I don't remember what I wrote an hour ago. No matter what I build, I'll always be in awe of Dave and what he could keep in his head.

Which is why making code readable is so very important. Our juniors and students will think we're ridiculous, when we spend a long time cleaning up some code or choosing the least misunderstandable name for a type. But you fuck that up and then others, as well as your future self, will be wasting many more minutes misunderstanding what your code does.

Partially yes. But if I create something myself I can "revisit" the headspace of that portion very easily, like I walked into a room.

Doesn't work as well on codebases I don't own fully though.

This made me chortle. I remember when I first joined a dev team asking someone how many of something their section should be able to store:

I don’t know, I’d have to look at the code.

It was an eye opening moment. Very few people can keep everything in their head. I’ve met a couple. They were rockstars who were truly exceptional.

The people who say "the code is the documentation" totally misunderstood what that was supposed to look like

The code is so convoluted the programmer has no idea how it works. Just tables and arrays references each other.