DEV Community

loading...

Discussion on: Coding practices your future self will love you for

Collapse
mnivoliez profile image
mnivoliez

I should add "do not write in comment what you could have write in code".
That include the name of function/variables, the types (if it's a typed language that is), the exception that can occur, any optional result, constant arguments.. etc...

Collapse
mohanarpit profile image
Arpit Mohan Author

Couldn't agree more. Comments should describe the "Why" and not the "How". The "How" is already present in code.