- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
*yesterday
s/year/week/
There’s an exponential amount of time between each panel. 1 hour, 5 hours, 2 days for the answer.
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.
Me during code reviews of other people
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.
The more frustrated you are when running
git blamethe more likely the command turns out to be a mirror.This is where the programmer’s way to humbleness starts :-D
Last time that happened to me, it was a mirror, but also not.
I had moved functions from one file to another without changing the contents. As a result, all those lines referred to me.
Good link that, I’ll have to add those flags to my list of aliases
-
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. 😅
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.
