Mine little quirks are:
-I use a folder system, 'Icons', 'Programming'-'A-M','N-Z'
-I generally have one system per programming file
-Ontop of that I generally make my programming incredibly modular, believing in the great power of reusing code
-I leave an example of how to use my programming at the top of the file
-I don't always comment, but when I do, I find myself being hilarious
-I like to keep procs simple, generally having a 'master' proc that will do a long string of procs in a row. Again for modularity
Small example of programming that I just did:
Since my stuff is so descriptive (I like to think), I don't have the need to comment as much. Obviously I haven't included the actual procs in this, but do I really need to? You should be able to tell what each one does exactly.
Oh incase you're wondering what all the ewnh_ stuff is, it's so that everything's very specific to that file. I can reuse variable names, for example I might have a disallowedWords variable within a spam filter, so that would be ewsf_disallowedWords.
Some might argue this is a bad way of handling it and I should just reuse the same variables (What are the chances of me allowing certain words in names but not the spam filter?) but I say phooey to you!