Recent post from stackoverflow.com made me laugh. 'No version control' execuse. I have to reveal my stupid experience for this. It was my first year in career. I developed a replacement of production data feeder. It had a significant improvement, and I was sure it will make other people's life easier. But, suddenly, an accident happened. At that time, neither did I version control, nor backed up a source. The fact that first year professional doesn't know version control system should not be a good execuse, but I didn't know that.
My intention was to clean up test data like this:
$ rm -fr $PRJ_HOME/data
But, actual command was issued like this:
$ rm -fr $PRJ_HOME/ data
With just an extra space, I screw up the $PRJ_HOME. Fortunately, I had spare partition with enough disk space. I dumped /dev/sdaN to a single file. It was too big to open in vim, so chopped in pieces, and went through ugly binary format searching for my piece of code. After recovering all of my sources, I learned CVS and spent a week to learn to setup and manage CVS. Now it became Subversion.
There is no execuse, no good reason not to use VCS(Version Control System).
I can think of one. Temporary project only, which will create noisy commits on main VCS. However, even though the project is temporary, building on my own subversion tree locally and stuff into it before going to main VCS is not a bad idea.
Subscribe to:
Post Comments (Atom)
2 comments:
Well you can still use an even better solution and use any of the DVCS that are out there, I find them vastly better to SVN, yet I heard that recently SVN got it's merge right and a better DVCS capabilities.
deepspawn, Thanks for the comment. At this moment, I am happy with svn. Hopefully if I have a spare time, I would love to consider options like git.
Post a Comment