I had my first real benefit of using SVN last night. Working on a project (which hopefully I’ll mention some time soon) that involved some complex interactive 3D stuff. I needed to add a bit of functionality to it. Seemed easy, but it had some side effects. Started hunting them down and had to start changing things here and there. I realized I had gone down a really bad path. No problem though. Just went back to the last check-in, got that, replacing what I had, and started over. Very nice!
Resources
Search
Archives
Categories
Meta
Yeah – I just did my first ‘branch’ a few days ago for a bit of code I didn’t really want integrated into the main base. It was great – branched off – coded the tool and done! No copying files into backup directories and worrying about overwriting something.
Yep, I’m with you. Just got it all set up on my local machine last week, and have already used it several times. So anyone out there still standing on the edge, go for it!
I think that this sort of thing has happened to every programmer worth his salt, yet many of them will still be asking why they need to bother with source control. I can’t even start to count the number of “new features” I have started to implement that have brought the whole house tumbling down. Since Subversion, it’s something that I don’t have to worry about anymore. Even a local file-based Subversion repository (which doesn’t take more than about an hour to set up from scratch) is a real life saver. If the term “copy of copy of new folder” is a familiar one, then Subversion is for you.
I would never have done “copy of copy of new folder”.
However, “ProjectName_version_10_final_revised_final_final_updated”…
So I am not the only one that name his backup subversion in strangeway.
I usually use the date and time to mark up when a version was done..
somthing like this
name_final_YYYYMMDD_number of version.rar