Honestly it depends. I like how everyone spouts the party line about how "anything less than clean well documented code is a sheer travesty!" but I work in a business with ridiculous deployment cycles and zero oversite: I do the best I can, but I write so much code its extremely difficult to write the clean perfect code that everyone else *claims* they write.

What I try to do is write code that can be easily maintained by someone who has roughly my ability. I comment the tricky parts, I name the programs, variables, and classes friendly names, I deploy, I move on. I don't have time to do anything else.

Sometimes I feel a bit guilty about it, but not very. You should see some of the horrors I deal with on a daily basis. Decades of custom code in obscure languages with zero documentation. One of my coworkers develops exclusively in VB6 and deploys cryptically named binaries all over the place. The woman I replaced programmed exclusively in <a href="http://en.wikipedia.org/wiki/IBM_RPG">RPG</a>. 

It's just extremely difficult for me to believe, as much horrible crap as I've seen in my years as a programmer, that *everyone* only generates clean code.