To comment or not to comment, that is the question.

If you spend time reading some source code on Github, you'll find out one interesting fact, the more elite a programmer is, the more thoroughly he documents his codes using comments.

I have both books. I think idea Uncle Bob was trying to get at was: you should write the code so clear that it's read like a book. The names of functions match their function and so on and so forth...But even though I kind of agree I will say that we've now gotten to a point(and this is from a Front End angle) where we have tools that extract comments before something goes to production. I also feel like comments help you remember things in your code and helps others to learn faster. Imagine the web without being able to view source code or comments. Their wouldn't be much progress and we'd be reinventing the wheel too much.

I think this is a interesting topic, I was always taught to comment my code, and I think it is important perhaps to highlight certain aspects which someone may find difficult to understand. But the problem is if/when that code is updated or changed in some way if anything those comments will become confusing for the reader. Hence why I think books like Clean Code promote using correctly named functions etc.