I think you missed my point entirely. Code looking pretty, being nicely formatted, and having comments is certainly part of but not nearly the whole picture in what makes good quality code that is easily maintainable through the ages. If you've never really stuck it out long term on a project, you have never felt the pleasure or pain of your previous work.

This particular code serves me well (in my consulting efforts) since 2008 and 2011. As for maintainability, I still clearly understand it and it can be immediately used everywhere.

If, by maintainability, you mean "looking at the mess I did some years ago in some large project and see how it turned out", then yes, I avoided such projects and large teams. Most of my code was written either by me alone or as a part of 2-3 persons team.