Oh dear god, that nonsense again. That might be true when you write boring, straightforward business code. But when you implement a complex algorithm, that's just silly.
It's also silly if, for example, you need to do "clever" things for performance reasons. Any comment that explains the why behind your code is a good comment.
See the recently discussed square-root approximation algorithm as an example.
This is only true of "unclever" code. You haven't written a lot of code if you haven't found a concise, optimized, abstract way to solve problems that aren't intuitive when first seen with the naked eye.
We aren't writing books, we're writing instructions for a computer and those two things can sometimes be very, very different.
-- What? --