Put me on the "comment your code" side of the argument (the "why" can be critical six months down the line); and adding white space for readability, too!

Since I work in multiple languages (starting with COBOL back in '80), the "don't use abbreviations" in names is one area I have to disagree with. 

If we didn't abbreviate, the COBOL names would get totally out of hand, and take up an entire line by themselves.  In my current business, we have standard abbreviations that are used, for instance "Elig" means "Eligibility".  Fortunately it's a "spoken abbreviation" as well - a business standard!  I'll maintain, for the sake of discussion, that as long as an abbreviation is standardized, it's okay to use them in names of variables, stored procedures, functions, or whatever.

In terms of standards, I agree with Pam that they give you a structure, but getting too detailed with them will cause problems.  I worked on a standards committee once where we had a "cross every <T> dot every <I>"  member, and it wasted a whole lot of time.  A basic set of rules that everyone can understand is essential; anything beyond that is superfluous.