Version control is one of those computer chores like backing up. We know that we *should* do it, but it is far too easy to start coding without having a good version control system in place. Then, when disaster strikes, we have nobody to blame but ourselves.
In an essay for Six Revisions, Anatoly Paraev explains version control by comparing it to the "file history" in Adobe Photoshop. However, he notes that "version control is much better than history in Photoshop: you also get a never-ending undo, effortless backup, peace of mind, and a more organized way of storing different versions of your work. You can have all of these things simply by taking a few minutes to read this article to understand what version control systems are."
"With version control systems, file versions are stored in a special database (usually called a repository). The fact that the history of a file is stored separately from the file itself adds extra safety: even if the file becomes corrupted, you can always restore any of its other versions from the history."
To earn this badge, you will experiment with a version control system called GIT. You will also use a graphical "front end" for GIT that is called SourceTree.