Why should I use version control if I'm working alone and already back up regularly?

Question

I\'m working on a project:

• Just me, no collaboration/source code sharing
• I\'m already backing my code up regularly, and I can use Dropbox to restore mista

Answer 1

You're saying you're using Dropbox to restore mistakes (or "can"), so in effect, you're using Dropbox as your version control. A very simple, badly designed one. Dropbox is great for many things, but it won't help you figure out which files were changed together in the same time, or return a folder to a particular snapshot.

These are things that a "proper" version control can do better for you.

Answer 2

Because most of the code you write is wrong. Mine certainly is and I am considered a damn good coder.

Its nice to be able to backtrack to a working version, also, you will find users ( and this may include yourself! ) flip flop between "I want it all" and "I just want a summary" its useful if you have the "I want it all" version safely stashed.

Answer 3

1) Once the version control system is set up, it will make your life so much easier. Manually backing up your source changes? Oh man, please no. What a PITA.

With version control in place, you just fire off a command. It tracks what changes and makes it easy to save them.

Why would you want to punish yourself by manually handling version control? Using git to track local changes is SO easy. Easy to set up also.

2) Keeping track of the history. Keeping a history of commits manually will almost immediately get out of hand.

Answer 4

You can check from the commit history how long the meat is in the oven. (In case you commit before cooking when you code at home, as I do.)