Quote:
Originally Posted by kiwidude
And no I dont buy the argument that putting them in Git will magically increase the number of contributions.
|
Well. For my part, I don't use my VCS for team dev (I'm the only dev) nor distribution (my pro work isn't distributed anywhere beyond my workplace, and the non-pro depends on the projects I contribute to). I use my VCS solely for source control. Meaning, version control and central management of my code. Because let's be honest, bad stuff can and will happen to any code, and a VCS is here to mitigate that. Also: code history, branch-and-forget for testing purposes, release tags, etc.
So, yeah. If you already have a VCS on hand, excellent, forget this post. If you don't, it would be a good idea to get one. It doesn't have to be public, and you don't have to share it, especially if you work alone (or close enough) on your projects. Just a [Subversion|Git] repo on your dev box would be more than enough.
Sure, it'll take a few hours to install, set up and learn to use, and your workflow changes a little, and you have to adjust your backup policy. But in the long term, it's worth the effort even if you code solo.
Wow. Juuuust a little OT, I guess. Sorry about that. It's just that with the advent of GitHub, even coders begin to think that a VCS's purpose is to share code. Yeah, it helps tremendously for that, but it's more than that, and it's not just for teams. I personally couldn't work (easily) on my projects without a VCS to back me up, even though I work alone.