“Good code is its own best documentation. As you're about to add a comment, ask yourself, 'How can I improve the code so that this comment isn't needed?' Improve the code and then document it to make it even clearer.” - Steve McConnell

@CodeWisdom No. Code and natural language are different. Quit telling people to use the wrong tool for the job.

@CodeWisdom @mjpt777 A comment describe why you did it in that way, the code describe how did it. So please think before to write code and comment.

@CodeWisdom But then comes that section, where you must manipulate the array. It's just 3 simple lines, but the comment /*Remove duplicate, and resize array*/ is what makes me say "oh, yeah - now I see". Not all code lines makes sense when you are searching for something, but comments do.

@CodeWisdom Says the guy who worked on 10 different software development projects in 10 years and never had to support the code he wrote.

@CodeWisdom @NickHodges I sometimes get scared when I see a large chunk of comments in my code, was probably a sign of doing something I didn't understand :)

@CodeWisdom @barryosull perfect response to your image post

@CodeWisdom This will definitely help...

@CodeWisdom Disagree. Main purpose of good doc is to find the section of code you're interested in. Micro-doc is indeed - or should be - spurious.

@CodeWisdom Still, documentation is inevitable.

@CodeWisdom The problem with this statement is that to most people good code is code written in their favourite programming language.

@CodeWisdom You may write the best code. But proper comments explaining the code might prevent some idiot from modifying the code in an unexpected manner