Seags

A long time ago (a few months to be exact) we realised the hard way why it is so important to use version control. To those of my followers who don't know what version control is, it pretty much allows you to make changes, add features or fix bugs to your application but with ability to move between different versions and going back to your original code.

This would have been great when we made a nice big update, it broke, and we then had to scramble to get it to work again on a production site instead of rolling back to an older, working, version.

This is when my research into a version control system (VCS) began. It was an interesting learning curve and one that I got a lot of flack for simply because I was a well established web developer you didn't use a VCS. Yes guys, "what was I thinking?".

So we are running Git in our offices and have been for a little while now. Git is a VCS that has taken the development world by storm and has led to great services such as GitHub. Git allows us in the office to do the following:

Roll back on older versions if required.

Create almost a seperate application with something called branches when trying new features.

We push changes we have made and tested to the server (BACKUPS).

Then last something we are implementing is getting a dedicated line in to allow collaborators to push and pull code from anywhere.

So as much as I took the flaming I got about taking so long to get going I now ask myself the question, "WHAT WAS I THINK?".