VCS stands for Version Control System. Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. Version control for a web designer or developer is a must in the modern era. It allows you to change certain files back to a previous state, change the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more. Using a VCS also generally means that if you make an error or lose files, you can easily recover them. In addition, you get it at an impressive speed. This applies to our class because we will be using Git for the rest of our assignments.
The history of Git is an interesting one. Git began with a fair amount of controversy. In 2002, the Linux kernel began using a proprietary DVCS called BitKeeper. However, after monetary disputes, the Linux community created their own version of BitKeeper. Using their acquired knowledge, they added a few improvements. These included more speed, a simple design, non-linear development, full distribution, and the ability to handle large projects. Git was created in 2005, and has not looked back. This is relevant to our class because it is important to know the history of Git and be appreciative of the functions that were not always available.
The usefulness of Git cannot be overstated. With its development, Git allowed web developers and designers to work on projects at the same time and make/commit changes and have it reflect in real time. The author from one of the articles described its function as basically taking a stream of snapshots of the data. This may not be a game changer for small individual projects, but imagine a large collaboration where multiple people are working on the same project at the same time. Then, it is easy to see how useful Git really can be. The importance of Git will be relevant to our class because as we continually use it, Git's core functions will be displayed.
To master Git, it is important to master a few basic commands. The first is "git init". This creates a new subdirectory named .git that contains all of your necessary repository files - basically a Git repository skeleton. Another important command to understand is "git add". This specifies files that you would like to be tracked. Once they are added, the same files can then be finalized using "git commit". After these simple commands have been executed, the result is a Git repository with tracked files and an initial commit. This is relevant to our class because the articles say a solid understanding of basic commands is important to a successful Git experience.
Highlight #5
Git's Impact On Developers
As mentioned earlier, Git has many useful functions that have revolutionized the world of web development and design. Git is not the only of its kind to perform the functions, but it is one of the most efficient and highly regarded. With Git, large groups can work on a project at the same time, seeing other's changes and additions in real time as they are committed. Also, a key feature is the idea of a local repository. Constant internet access is not required to work on a project. This may not seem like a big deal, but this feature comes in handy quite often. There is even a "blame" feature, where users can see who made certain changes, and when! This is relevant to our class because it is important to understand how Git has made the developmental experience easier/more convenient.