5 Things: About Programming, Prelude

Over the years I've developed a set of best practices that I use. More than anything these are things that in my opinion "just make sense." In this five part series I'll be discussing my approach to:

1. Conditionals (test right, test left)
   
2. OO design (do it, divide it, armor it)
   
3. Globals (don't, just don't)
   
4. General style and naming (var/class names, tabs, blocks)
   
5. Version control (it's free and worth twice that)

I won't presume to say that these will come to fruition in order, at once, or even quickly. As I write them I'll post them. If I'm especially inspired I'll write them more quickly, and then... post them. In the (likely) event that there is a construct similar to: [some topic] these are place holders for links to upcoming posts, probably part of the series (or to remind me of something in another potential series).

Being upfront, there will be a bias toward languages like PHP because that's what I've been developing in for the last few years. I don't like to get into the holy wars revolving around various languages and which is better. Take away what you will and leave your "Perl/Ruby/Python/Java is better" opinions at the door please. As always, some people may disagree with me, that's your right. Some people may disagree vehemently, also your right. Some people may disagree, call me a stupid git and get otherwise abusive. To those people see the credo, "Sod off you little wanker!". 'Nuf said.