5 ms·
Agreed. Others have pointed out that one can just commit daily and use git as a backup. This is true, but there is still a psychological difference: We have be
by cjkahn 11y ago
Agreed. Others have pointed out that one can just commit daily and use git as a backup.
This is true, but there is still a psychological difference: We have become slaves of our window managers and development tools. The fewer tools you use, the more true creativity is unleashed.
The best works of humanity have been written before the existence of version control (and computers for that matter).
I see version control as a necessary evil for multi-developer projects.
- boomlinde 11y agoWell, if you're developing something, and that isn't your development tools themselves, you are still a slave to your development tools. I really don't buy this argument, and I just think that it's a matter of habit and convenience. You can pick and choose development tools freely until you think that you have a satisfying workflow. I would argue that for me, personally, using version control "unleashes more true creativity" because I can fire and forget my changes and just branch out or roll back until I find something I like, without thinking too much about where and what to backup. The not actually writing code or designing aspects of development then take less time out of my work.
- imdsm 11y agoI have to agree. With SCM, I feel more in control, and worry less about my code and files getting lost, and feel like I am free to do anything. I tell my developers when they're worried about testing something on code, just create a branch and try it, and if it fails, just move on. You shouldn't ever be worried about losing code, or changing things. This is one of the greatest advantages of SCM -- how many variations of a codebase you can have, and how easy that can be.