Jump to content

Article: Top 5 bad excuses for not using source code control


Recommended Posts

I'm going to disagree with the fundamental premise of this article -- I personally have NOT found any "added value" in using an off the shelf Source Code Control product. I am (essentially) a single developer (ie not part of an extended team) and, while I make use of consultants at times, the majority of those kinds of interactions occur episodically or in re: to small units of code. I use three different development systems and frequently change those out (any ways every 2 months); and am now simultaneously developing in Vista and XP, with one of my system being XP running within Parallels. I have several different physical backup that I use, including china copies and I rotate these on a scheduled basis. My major project consists of over 1400 subvis and I am currently engaged in a major refactoring/restructuring process in anticipation of the next major release. Partly this is because of the nature of the project itself, partly it's because of demands imposed by both Vista and the necessity of maintaining legacy support of XP-based deployment.

Now I'm not trying to imply that any of that mandates not using SCC per se (ie not using a particular SCC software package) but I am trying to give a bit of context for my comments.

I personally have found that the use of Subversion actually slowed me down and led to my losing some work. It did not help me and, while using it, I actually felt far less secure in my control of the actual source code and frequently quite frustrated with the overall process. Now I'm sure that others can argue that this was due to my unfamiliarity with Subversion itself -- I'm definitely NOT saying that it's bad in any way -- but no matter how true that might be, my lack of familiarity with Subversion misses the essential point that, in my case, it simply didn't add value to my work flow. And taking time to have it POTENTIALLY add value to my process wasn't a very effective use of my time at that piont. It just complexified my work enormously without giving me any direct benefit. As a contrast I have found the LV Project to be quite useful in a number of ways -- not so much as SCC per se but it is a "new" tool, with which I was originally unfamiliar, but have gradually grown to find directly beneficial and which was intuitively obvious enough to me AS I was learning about it, to be able to make use of it in some ways immediately.

FWIW -- and just to be clear -- I think that Subversion is a very good tool and I know an enormous number of people who use it both in and out of the LV world. I have and would recommed it to others who want to make use of SCC and don't want to have to pay a lot for that functionality. But it just didn't work for me. I may look at it again in the future -- when I am at a different point in the current work flow and can take time and space to really get to know it -- but until that time, I am reverting to my prior style.

Link to comment

QUOTE(PaulG. @ Jun 18 2007, 05:23 AM)

Few here would argue the importance of source control. WHICH source control software, however, would be a real discussion. :yes:

Well, I figured that I would not ignite a holy war, just yet ;) Plus, blog articles are supposed to be kept relatively short :)

But, feel free to post your opinions on which tools you (dis)like and why.

Cheers,

-Jim

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.