₦airaland Forum

1. Make sure you understand the problem you’re trying to solve.

2. Prioritize clarity and correctness. Performance is less important, and cleverness is to be avoided.

3.If your code needs comments to be understood, it’s over-complicated.

4.Always comment your code, or at least your modules.
Extensibility and reusability are over-rated.

5. Don’t innovate security. Use well-established security libraries.

6.If you haven’t tested it, it probably doesn’t work.

7.If you have time to ‘go back and fix it later’ you’ve got bigger problems in your job.

8.Integrated Development Environments (like VisualStudio) and the internet (e.g. StackOverflow) are the best friends a coder could ever have.

9.printf is the world’s simplest debugger.

Source quora

No.3 though a well written code should always have a comment regard less if it's over complicated or not