A couple weeks ago, I started on a bit of tirade discussion about version control that turned into a short series - Version Control and You Part 1, Part 2, and Part 3 - and while that series may expand later, I'm moving onto the next step of the process....

Deployment!

For some people, the idea of deploying code keeps them up at night. Every time they consider what it takes to deploy their latest and greatest changes, they break into a cold sweat. They think they know the changes they've made. They think they know the code/db changes required. Generally this type of team has a deployment process of "well, we ftp it to the server and click around to see if it works".

Um... yeah.

For the record, that's not a deployment strategy. It's the fastest way to break everything and piss off frustrate your users.