fawtytoo
Mini-Member
Posts: 51
Registered: 09-11 |
fraggle said:
When you don't use version control, your source code is ephemeral: basically just a bunch of files that you sometimes perhaps make "backup copies" of, if you remember to. After a while of using version control, I found that the way I thought about programming changed: more disciplined and precise. Your work becomes a procession of small changes, each documented, explained and justified (and the justification is as much for yourself as for others). It gives you greater confidence in your work.
I think I'm doing a poor job of explaining what I'm trying to say. Sorry to ramble on, I'm sure you're fed up of the whole subject by now, and it doesn't seem like you're likely to change your views at this point anyway. It's something I've wanted to write about for a while.
For the umpteenth time (or maybe the first depending on how you view it):
My code is not a bunch of files that I occasionally make backups of. I religiously make a copy of the project and make changes to that copy only. That copy gets a revision number. When I wish to make more changes, I make another copy and repeat the process. I have separate copies of my project for each revision. Hence, the patch files: they show the difference between, not just each revision, but each revision copy. It's not random or occasional, it's religiously done. There may be little evidence on my web site of this, but I am using version control. I can track every change to a revision easily, using both the changelog and the patch files. If someone gave me a patch for a specific revision, I can keep it with that revision only. Same with branching. My system is crude, perhaps a bit time consuming, but it does have version control.
Perhaps you are not the only one who is explaining poorly. But the reason I'm not changing is because I'm already doing it. Just not some where you can see.
|