There's no need to set up a server to use SVN. It will run perfectly well against a local repository on the same machine, or over ssh (again without a dedicated server) to a remote machine. And there's other options besides (or on top of :) SVN that don't require dedicated servers either.
Additionally: Not that you're not free to work without a net if you really want to, just don't be surprised when you go splat. And you will eventually go splat (Murphy and what not . . .). And the more cautious who do use SCM religiously will snicker when you're hoist on your own petard.
The cake is a lie.
The cake is a lie.
The cake is a lie.
| [reply] |
not applicable to the situation, such as it's insistence on using version control
It is interesting indeed to read others opinions. I started using a basic unix version control system (SCCS) more than 10 years ago, and have used RCS and CVS as well, every day of my life since. I find it to be such a crucial code development tool since it removes all fear from the process:
- the fear of going down the wrong path,
- the fear of commitment,
- the fear of releasing bad code which is used by others
If I make a grave mistake, or even if I just hate what I churned out, retrieving the latest stable version takes mere seconds.
In a way, I was a little surprised version control was even mentioned in the book, if only because I took it for granted that everyone used it as a matter of course. I learn something new everyday.
| [reply] |