Thanks for your input on the article! In my my experience and research, it is very difficult to find "a rule of thumb [that] is generally accepted" regarding comments. While commenting on classes and public methods the way you describe is a common practice, my argument is that this is a largely arbitrary method of commenting code that can lead to comments that are not always maintained with the same care as the code it is describing. By only commenting when the code is not self explanatory, and cannot reasonably be refactored so as to make it self explanatory, your code will become easier to read and will be less prone to harboring unmaintained, misleading comments.

And I couldn't agree more with your sentiment regarding code that is so "slick and clever" that it requires comments. Readability is better than slick and clever any day of the week.