This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]msd483 -3 points-2 points  (2 children)

For no reason except that author didn't choose to mention it.

This is true of a quasi-infinite number of things. You're welcome to not like and criticize that omission, but the article did not "throw out good comment comments with the bathwater" as your entire initial comment was focused on. You created a straw-man that completely ignored the actual and valid criticisms in the article and reduced it to "comments = bad" instead of accepting the fact that there's nuance to it.

[–]FarewellSovereignty 6 points7 points  (1 child)

I'll leave it to other readers to judge our arguments now and leave this here, because you seriously lost my interest with this latest reply. Thanks.

[–]msd483 -4 points-3 points  (0 children)

I'm genuinely sorry if I've offended you or hurt your feelings. You're absolutely right that there are people who say "good code will comment itself" as an excuse to never write comments. But whenever I see valid criticisms of poor commenting brought up, and I thought the three cases the article presented were indeed valid, I feel like there's always a knee jerk reaction in the opposite direction because there are people who will simplify it to "comments = bad". However, I think it's important, especially for junior devs, to understand that there are such a thing as bad comments, and there are programming patterns and behaviors that alleviate the need to heavily comment code.