Shared publicly  - 
What's the term for the feeling you get when looking at code and wondering "who in the hell wrote this crap, it's all messed up, needs to be fixed, how is it even working in the first place!", so you run 'git blame' and realize it was yourself, over a decade ago?

Then, wondering if you can blame someone else for not fixing it up since then, you run 'scripts/' and realize that you are the maintainer for it as well.

Time to just back away slowly from the keyboard and forget I ever even opened those files...
Jonas Danielsson's profile photoDarren Hart's profile photoGuy Dawson's profile photoSiebe Joris Jochems's profile photo
git rm -rf . && git commit -m 'I quit'
Realizing that you grew as a developer, cleaned up the code and made it more readable, faster and more maintainable. Have a good day. ;-)

I love creating new German words.
Ah. Good to see everyone has a learning curve, even the best kernel hackers.
Just another reason one should have an ample stock of brown paper bags handy at all times.
"Vain and Irresponsible" (because you closed the editor and backed away from those files)
My reaction would be "waou, I progressed a lot from this time". But if you say maintainer, you speak about the Linux kernel, so of what part do you speak of? Just curious…
You should feel good that it took 10 years. I've had the same experience with code I wrote only a few months earlier.
I thought that was the implied meaning of the closed curly brace?? I'll have to rethink my whole process now...
Ugh. I'm glad I'm not the only one that happens to.
Greg, I'd have contributed patches and got a leg up into kernel work but it was so bad I, instead, submitted it to Worse Than Failure. (Just to be clear: I'm kidding.)
It means you're still learning and improving. This is a good thing. Really :-)
There usually isn't a whole decade in there for me...
that teaches self, lots of things ! :)
The term ist "long-time contributor" :)
Tsk, you're not a roleplayer, are you? Otherwise you'd know that it just means you gained enough xp to level up. ;)
The term would be "you, git" :-) 
"Practically inevitable" ?
As has been stated by a wise man long ago, debugging code is twice as hard as writing it, so if you write it as smart as possible, you are by definition not smart enough to debug it.
This is why it is recommended to leave hints to readers including the later self.
As for a word: selective memory.
That which turns to glimmering gold
everything long past
So it goes. Code sucking is the natural state of the universe.  As you approach enlightenment your code will suck less.

If your old code doesn't suck to you, you're not improving.
Add a comment...