This is probably more accurate:
-Who the fuck wrote such a shit!
-WHO???
-…
-Oh… it was me…
And I always think I write good comments until a year later I’m like these comments don’t help shit
Try to write as if you are explaining the functionality to an unrelated 3rd party like a new hire.
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.
Don’t be a dick to your (current) co-workers.
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.
To be fair, this is also me when I look at a network setup years later. (I do IT with a specialty in networks)
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
testing
