Totally agree. Good points in the article, but the second one is a big no-no.
Comments make the code harder to read, not to mention obsolete comments.
Please Gabor, don't tell me the comment "Represents a Book" in the article didn't immediately make the "function Book(title, author)" code instantly more understandable??? :-)
Comments IMO should be all about the "why" and not the "what" or "how".
+1 to linking to SO solutions where appropriate.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.