Beyond "Clean Code": Why Your Comments Matter

cchmaynard about 6 hours ago 3 commentsRead Article on blog.moertel.com

DE version is available. Content is displayed in original English for accuracy.

⚡ Community Insights

Discussion Sentiment

67% Positive

Analyzed from 100 words in the discussion.

Discussion (3 Comments)Read Original on HackerNews

johnmwilkinson•about 1 hour ago

I completely agree. I wrote a book on the subject of how to write clear code (Bob Martin was off by one letter!) and comments are a key element of that.

https://elementsofcode.io/chapters/documentation/

We’re in good company: Jon Ousterhaut had a conversation with Uncle Bob where he brings up the exact passage you quote as a point of disagreement.

blinkbat•about 6 hours ago

I disagree that it's the codebase's job to communicate product's intent

tmoertel•about 6 hours ago

Thanks for your feedback. (I am the author of that article.) I was trying to argue that it’s the code’s job to communicate its authors’ intent for the code itself. To help me clarify my writing, can you tell me what I wrote that led you believe I was talking about intent at the product level and not the code level? Thanks!