Return to Answer

In layman's terms:

• There's nothing wrong with the comments per se.
•   What's wrong is writing code that needs that kind of comments.
• What's wrong is assuming it's OK to write convoluted code as long as you explain it friendly in plain english.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing for (writing code that isn't easily understandable) is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better than one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.

In layman's terms:

• There's nothing wrong with comments per se. What's wrong is writing code that needs those kind of comments, or assuming that it's OK to write convoluted code as long as you explain it friendly in plain English.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing for (writing code that isn't easily understandable) is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better than one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.

In layman's terms:

• There's nothing wrong with the comments per se.
• What's wrong is writing code that needs that kind of comments.
• What's wrong is assuming it's OK to write convoluted code as long as you explain it friendly in plain english.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better than one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.

In layman's terms:

• There's nothing wrong with the comments per se.
• What's wrong is writing code that needs that kind of comments.
• What's wrong is assuming it's OK to write convoluted code as long as you explain it friendly in plain english.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing for (writing code that isn't easily understandable) is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better than one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.

In layman's terms:

• There's nothing wrong with the comments per se.
• What's wrong is writing code that needs than kind of comments.
• What's wrong is assuming it's OK to write convoluted code as long as you explain it friendly in plain english.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better that one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.

In layman's terms:

• There's nothing wrong with the comments per se.
• What's wrong is writing code that needs that kind of comments.
• What's wrong is assuming it's OK to write convoluted code as long as you explain it friendly in plain english.
• Comments don't update themselves automatically when you change the code. That's why often times comments are not in sync with code.
• Comments don't make code easier to test.
• Apologizing is not bad. What you did that requires apologizing is bad.
• A programmer that is capable of writing simple code to solve a complex problem is better than one that writes complex code and then writes a long comment explaining what his code does.

Bottom line:

Explaining yourself is good, not needing to do so is better.