4 ms·
Until about 18 months ago my source control was a bash file that would create a time-stamped backup of specific hard-coded folders into /usr/sourcebackups. Just
by avinashv 17y ago
Until about 18 months ago my source control was a bash file that would create a time-stamped backup of specific hard-coded folders into /usr/sourcebackups. Just a mkdir, name the folder, copy everything as it is. This was run as a cron every midnight.
Not terribly proud of this. "Secret shame" is a pretty good way to describe it.
- brazzy 17y agoBah. I started using SVN for personal projects only about 2 months ago, and before that, my source control was "time-stamped ZIP archive created manually whenever I feel like it"
- avinashv 17y agoHaha good one-up. I recall doing that quite a few years ago, though I doubt I ever wrote a project longer than 500 LoC back in those days. One thing I found was the first few weeks of using a VCS I felt I was less productive and that the extra work wasn't worth it. I now see the benefits and am OK with the time sink of managing a repository, but do you find that for personal projects it's not worth the hassle for you at this point?
- brazzy 17y agoNot really - setting up the repository and getting the old projects into it was a bit of a hassle (actually much more the latter than the former, and mainly due to SVN behaving strangely with ignored files), but using it is hardly any additional work. I haven't really done much to use the capabilities either, but it just feels good to know that due to checking in frequently, I never have to worry about breaking something that was already working.