>George;
>
>Every place I have worked as a programmer I have introduced coding standards. I like to work in an environment with code that others as well as myself can read. It makes a programmer’s job easier.
>
>Having said that I made a good deal of money and was able to support my family for several years by being called in by different companies to fix problems with FoxPro/VFP code left by others. I am very good at such things. Too many programmers write code that is difficult to understand, not commented, and not efficient. I love puzzles and this is fun to me.
>
>My motto is, “Fix the code and do not worry about inefficient code written by others. Leave inefficient code alone unless you are paid to do otherwise”!
>
>If everyone writes well-commented code that follows standards, and works, a good source of employment will disappear! :)
>
Tom,

I personally believe that well written code explains itself partially. IOW, it's easy to figure out the how, but the why is another issue. That's where good comments come in. They should explain the why rather than the how. For example, I can see that you're iterating through an array from the code, however, I don't know why unless the comments tell me.

As I said previously, the only naming convention I believe in is that variables and so on being meaningfully named. I don't care if it's Camel Case or Pascal Case or whatever case. I don't care if you use Hungarian notation or anything else. Make it meaningful.

The problem as I see is that too many unmeaningful comments actually hurts the readability of the code.