I think that I've read Clean Code sometime in the last few years, but I don't remember anything from it :|
Anyway, those are all valid points, but I would add an exception to the third one - comments are essential, in my opinion, but they should not tell what the code is doing (code should be doing that in a readable way) but why is code doing that. Why in this context should be business or some domain requirement, something that's on a higher level than code but affects its nature. Still, if this can be told through code alone, leaving a comment would induce an additional cognitive load on the reader, so it's not a hard rule.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that I've read Clean Code sometime in the last few years, but I don't remember anything from it :|
Anyway, those are all valid points, but I would add an exception to the third one - comments are essential, in my opinion, but they should not tell what the code is doing (code should be doing that in a readable way) but why is code doing that. Why in this context should be business or some domain requirement, something that's on a higher level than code but affects its nature. Still, if this can be told through code alone, leaving a comment would induce an additional cognitive load on the reader, so it's not a hard rule.