When you look at code you wrote last year
When you look at code you wrote last year
20 comments
-
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.
-
Yeah same, also I don't usually need a year to think that. The next day often works. 😅
-
-
This is probably more accurate:
-Who the fuck wrote such a shit!
-WHO???
-...
-Oh... it was me...
-
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.
-
-
And I always think I write good comments until a year later I'm like these comments don't help shit
-
Me during code reviews of other people
-
*yesterday
-
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.
-
There’s an exponential amount of time between each panel. 1 hour, 5 hours, 2 days for the answer.
-
s/year/week/
-
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
-
To be fair, this is also me when I look at a network setup years later. (I do IT with a specialty in networks)
-
testing
20 comments