---
title: "Comment by Crhistian on \"Code Clarity: Why Comments Should be Avoided in Your Code\" | Hashnode"
description: "A good rule of thumb to follow is that a comment should explain why not how. Very often I see well intentioned developers litter a codebase with line by line co"
url: "https://hashnode.com/posts/code-clarity-why-comments-should-be-avoided-in-your-code/64340b2b7a6ecaa1407251c3/comment/6434524394d1164842da0360"
---

[Discussion](https://hashnode.com/posts/code-clarity-why-comments-should-be-avoided-in-your-code/64340b2b7a6ecaa1407251c3)

Comment [Code Clarity: Why Comments Should be Avoided in Your Code](https://hashnode.com/posts/code-clarity-why-comments-should-be-avoided-in-your-code/64340b2b7a6ecaa1407251c3)

[Crhistian](https://hashnode.com/@crhistian)

[Apr 10, 2023](https://hashnode.com/posts/code-clarity-why-comments-should-be-avoided-in-your-code/64340b2b7a6ecaa1407251c3/comment/6434524394d1164842da0360)

A good rule of thumb to follow is that a comment should explain why not how. Very often I see well intentioned developers litter a codebase with line by line comments that add no value.
