I had a less experienced person with me looking at some code.

I pointed out that a particular section of code is shit; just bad form, hard to debug and generally unpleasant to work with. I noted that the person that wrote this didn't really know what they were doing, sure the code works and has been working for a long time, but this is not how we would do things.

They asked "wow, who wrote this?" I replied "it was me 13 years ago"; it is a great ice breaker, in a non-critical part of the system, new people realize we all have to start somewhere.

It also allows me to go over the standards we use, why we use them and how to simplify debugging.

Am I the only one who likes looking at my old code? Generally I feel like it's alright.

Usually the first project when I'm learning how to use some new language or environment is super-shitty. I can tell it's very bad, usually I don't like interacting with it if I have to make changes, but it's still not overly painful. It's just bad code. And that one exception aside I generally like looking at my code.

Had this multiple times. Reading code from 2 years ago and being like "what idiot wrote this" only to find out the culprit was me. Then the memories came back and I remember why the compromises were made. What I learned from that is not to judge people too much on their code. What you see is a combination of both their skill and also a whole bunch of necessary compromises for which you may not know the reason. Nowadays I don't get too annoyed if the code is a bit messy. As long as it's well tested and documented.

Back then? You mean last sprint?

That's scary as shit

And this is why you comment your code