Comments are a hack to work around the failure to write code which is sufficiently clear and expressive (note that I'm talking about inline comments, not comments used to generate documentation). When I find myself typing a comment, I step back and look for ways to improve naming, or refactor, until the comment is no longer necessary.
Talk about misleading advice. I agree with your premise that the purpose of your code should be apparent through a the use of a meaningful naming convention but that does NOT eliminate the need for comments. Comments should be redundant, they are meant to confirm the obvious so that there is no room to second guess what that section of code is meant to do. Your code may be "clean" and "easy to read" but that means something between jack and shit to the poor PFY who has to bring it into compliance with a new standard. Who do you honestly think is better off? The intern who has the privilege of learning from your immaculate structure while basking in the glow of your brilliance; or the guy who can read what you've done and make the changes he needs to and make it out of the office in time to meet that new blonde from accounting out for drinks?