all 20 comments

sorted by: hot top controversial new old
[–] 44 points 2 years ago (1 child)

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.

  • source
  • hideshow 1 child comment
  • [–] 39 points 2 years ago* (5 children)

    This is probably more accurate:

    -Who the fuck wrote such a shit!

    -WHO???

    -...

    -Oh... it was me...

  • source
  • hideshow 5 child comments
  • [–] 29 points 2 years ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 23 points 2 years ago (3 children)

    The more frustrated you are when running git blame the more likely the command turns out to be a mirror.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 2 years ago (1 child)

    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.

    And since I started thinking, I found this

  • source
  • parent
  • hideshow 1 child comment
  • [+] 22 points 2 years ago* (last edited 1 year ago) (3 children)
  • [–] 5 points 2 years ago (2 children)

    Try to write as if you are explaining the functionality to an unrelated 3rd party like a new hire.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 2 years ago

    Me during code reviews of other people

  • source
  • [–] 10 points 2 years ago
    [–] 9 points 2 years ago

    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.

  • source
  • [–] 6 points 2 years ago

    There’s an exponential amount of time between each panel. 1 hour, 5 hours, 2 days for the answer.

  • source
  • [–] 4 points 2 years ago

    s/year/week/

  • source
  • [–] 3 points 2 years ago

    To be fair, this is also me when I look at a network setup years later. (I do IT with a specialty in networks)

  • source
  • [–] 3 points 2 years ago

    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

  • source
  • [–] 1 point 2 years ago