Clean Code Tip: Not all comments are bad

bellonedavide

Davide Bellone

Posted on May 11, 2022

Clean Code Tip: Not all comments are bad

Many developers say that

All comments are bad! 💢

False! Most of the comments are bad!

Examples of bad comments

For example, look at this method, and look at the comments:

/// <summary> Checks if the password is valid </summary>
/// <param name="password">The password to be validated</param>
/// <returns>True if the password is valid, false otherwise</returns>
public bool IsPasswordValid(string password)
{
    Regex regex = new Regex(@"[a-z]{2,7}[1-9]{3,4}");
    var hasMatch = regex.IsMatch(password);
    return hasMatch;
}
Enter fullscreen mode Exit fullscreen mode

Here the comments are pointless - they just tell the same things you can infer by looking at the method signature: this method checks if the input string is a valid password.

So, yes, those kinds of comments are totally meaningless, and they should be avoided.

Good types of comments

But still, there are cases when writing comments is pretty helpful.

public bool IsPasswordValid(string password)
{
    // 2 to 7 lowercase chars followed by 3 or 4 numbers
    // Valid:   kejix173
    //          aoe193
    // Invalid: a92881
    Regex regex = new Regex(@"[a-z]{2,7}[1-9]{3,4}");
    return regex.IsMatch(password);
}
Enter fullscreen mode Exit fullscreen mode

Here the purpose of the comment is not to explain what the method does (it's already pretty explicit), but it explains with examples the Regular Expression used to validate the password. Another way to explain it is by adding tests that validate some input strings. In this way, you make sure that the documentation (aka the tests) is always aligned with the production code.

By the way, for more complex calculations, adding comments explaining WHY (and not HOW or WHAT) a piece of code does is a good way to help developers understand the code.

Another reason to add comments is to explain why a specific piece of code exists: examples are legal regulations, related work items, or references to where you've found that particular solution.

Conclusion

Always pay attention when writing comments: yes, they often just clutter the code. But they can really add value to the code, in some cases.

To read more about good and bad comments, here's a well-detailed article you might like:

🔗 Clean code tips - comments and formatting

Happy coding!

🐧

💖 💪 🙅 🚩
bellonedavide
Davide Bellone

Posted on May 11, 2022

Join Our Newsletter. No Spam, Only the good stuff.

Sign up to receive the latest update from our blog.

Related

Make It Work, Then Make It Better
softwareengineering Make It Work, Then Make It Better

November 27, 2024

Regra 7: Elimine casos de falha
webdev Regra 7: Elimine casos de falha

October 2, 2024

Top 10 Clean Code Rules 🎨🚀
cleancode Top 10 Clean Code Rules 🎨🚀

September 5, 2024