It actually helps having someone asking you about the code. I had reasons to revisit an old codebase I cobbled together (and basically stoipped working on) Jan-Mar 2007 and once I had had a glance at the code, it wasn't too bad, even if there's almsot no comments (I'd climb out on a limb and say "completely undocumented", but there's a few design docs and at least one protocol spec in the code tree, even if it's not in the code itself).
Oh, indeed; that's why I adhere to the Next Jackass Principle ("always comment your code thoroughly for the next jackass who will have to maintain it, because 95% of the time, the next jackass is you"). Thanks to the comments, I knew what the routine in question was supposed to be doing; however, it took a couple of minutes to re-grok the template-sludge enough to figure out how. Fixed now.
no subject
(You don't believe me, look at any code you haven't touched in a year...)
no subject
no subject
no subject
no subject
no subject