Basically the more your code reads like prose, the less need there is, for you to have to describe what you are doing in the comments. Instead of describing the "what" of your code you can then describe the "why".
You can describe the reasons you have chosen to do something, instead of what it is you're doing.
Good post!
RE: Making your code clean: How proper naming can save the day