Off the top of my head ...
• consistency applies to all that follows
• remember you're writing for humans, not just for the computer
• write all code so that a stranger can understand it one year from now
without your presence / coaching
• generally speaking provide high level comments; what is the program trying to solve / achieve?
• use camel case, pascal case, Hungarian notation ... whatever spins your propeller
• name classes / modules / functions / variables meaningfully so code is self documenting (nouns and verbs)
• use comments where preceding fails to illuminate
• avoid magic / clever code that you may not understand a year from now
• indent to easily demonstrate hierarchy / parentage
• don't be afraid to use white space liberally
• if you have a problem defining your own style find someone's style you like and mimic it until your own style emerges
That's all I've got for now ...
