Contents
How many comments should be in code?
Three lines of comment for every line of code would not be excessive. For actual code, it would be much lower. I don’t agree with the extremists who think you should aim for zero comments, but certainly if you think you need comments you should first consider whether the code could be made clearer.
Why should you add comments to your code?
Commenting involves placing Human Readable Descriptions inside of computer programs detailing what the Code is doing. Proper use of commenting can make code maintenance much easier, as well as helping make finding bugs faster. Further, commenting is very important when writing functions that other people will use.
Why are comments in code a good or bad thing?
Good comments in code are essential for software with a non-trivial lifespan. Bad comments are worse than useless. Comments should be written for “the next guy”*. A good comment tells you about why something is being done – a great comment stops a future mistake. An example of a good comment:
Why do people leave bad reviews on businesses?
Good or bad, a vast majority of customers will leave businesses a review when prompted, and most consumers have the same agenda for their positive comments as their negative reviews: helping other people make better purchases.
How to write a good report card comment?
Effective report card comments are expressed with clear and simple phrasing, using: 1 An encouraging and/or positive tone 2 Language that is easy to understand for both students and parents, as opposed to educational jargon used from the… More
Why do people expect compensation for bad reviews?
In some cases, people may even be expecting compensation in the form of merchandise or credit to help make up for their poor experience. Less common overall, we found it was consumers with the highest annual income who felt the most entitled to free merchandise in response to their negative feedback.