Ok, sure maybe wrong choice of words, not "overlooked" more like "underestimated". If you compare "comments" to other subjects... Also, when I try to discuss comments with developers, discussion is short - people focus on other things like "why to use framework A or B" or even “use tab or 2 spaces"... I worked with different developers and many times, there was no comments in code, or there were too many comments (because code was bad) and that is what I'm writing about. We should use comments but for good reason...
Sure "code smell" is maybe too generic, but my intention was to point that sometimes you do not need comment, instead you can write good code, so sorry for that "cute but useless" expression ;)
"The value of comments in code varies in a number of ways." I absolutely agree.
"The unqualified claim that code should always be self-documenting is silliness of high degree." Sure, also agree, but still code should be clean and readable. If you use language, which give you possibility to write such code, you should at least try. In tags for article I used javascript and php, examples are based on php and js. I also never claimed and never would claim that "code should always be self-documenting" because it is impossible. I even said that comment should be used as documentation for code. So, I agree with you (again ;) )
As for me, I also like comments in code, but I also like good and clean code (yep, again very generic expression). If there are too many useless comments, code become unreadable. Bad comments are like bad code ;)
I said when and how I prefer to use comments, but in most cases it depends on team which I work with and languages which we use. You should always discuss "comments" as part of project guidelines, the same way as you discuss other tools e.g. test framework, language, database, linting etc.
I'm repeating myself, sorry for that. I just want to thank you for comment and I agree with you (or you with me, if we take your comment as response to whole article)
"Code’s comments are always overlooked subject."
I don't know where you live, but in most universes I've called home for the last thirty years, the debate about the goodliness of comments has been vigorous and ongoing, sometimes vitriolic, never overlooked, and often heatedly argued.
The expression "code smell" has only relatively recently been coined and become popular (not necessarily correct - merely popular). I don't rank popularity as a motive to promote or even accept ANY claim. To be extra-clear, the expression "code smell" is a popular usage that means almost nothing; it's cute but useless, except in the context of some particular languages, if even then.
The value of comments in code varies in a number of ways. The unqualified claim that code should always be self-documenting is silliness of high degree. I've written code in languages that almost nobody would grasp without comments.
Without a few remarks, the following function is a wee bit obscure even for programmers who know the language:
I like comments. Prob'ly that's language-specific.