Thread: Why no emphasis on commenting

For me it depends on the size and scope of the project. I had assignments which required only a simple script and and to be honest, the only comments were those with my name, the class name, and the assignment number.

Quantity of comments does not equal quality of code readability. I hated classes where the rule of thumb was to comment every line of code. Writing effective comments (something short and concise which explains a ~5-10 lines of code, depending on difficulty of reading just the code) is something I think a lot of classes really skimp out on.

I believe that encouraging students to comment is better than not, but if it's something that they see as a "burden" while coding rather than being helpful, they won't do it later on in their careers.

I guess it all depends what kind of person you are to begin with.

I personally am quite organized. I've always liked to design things first and I've always left myself comments whether it be whilst programming or writing HTML/PHP code etc.

It's good to be able to read what is going on without having to analyse the code and my comments have proven to be invaluable when going back over older projects.
Comments are also useful for anyone else who happens to be working on the code with you or reads your code at a later date.

When you first start programming, I believe it is very handy to get into the habit of commenting your code. It's all part of the learning process.
If you can comment your code successfully then it proves that you understand what is happening regardless of if it is required or not.