In my previous curmudgeon post, Writing Without
Distractions, I gave version control only a brief mention, and
promised a follow-up post. That would be this one. This post is intended
for people who are not in the software industry, including not
only poets but other writers, students, people who program as a hobby, and
programmers who have been in suspended animation for the last decade or
three and are just now waking up.
The Wikipedia
article on version control gives a pretty good overview, but it
suffers from being way too general, and at the same time too focused on
software development. This post is aimed at poets and other writers, and
will be using the most popular version control system, git. (That Wikipedia
article shares many of the same flaws as the one on version control.) My
earlier post, Git: The other blockchain, was aimed at software developers and
blockchain enthusiasts.
What is version control and why should I use it?
A version control system, also called a software configuration management (SCM) system, is a system for
keeping track of changes in a collection of files. (The two terms have
slightly different connotations and are used in different contexts, but
it's like "writer" and "author" -- a distinction without much of a
difference. For what it's worth, git's official website is git-scm.com/, but the first line of text
on the site says that "Git is a free and open source distributed version
control system". Then in the next paragraph they use the initialism SCM
when they want to shorten it. Maybe it's easier to type? Go figure.)
So what does the ability to "track changes" really get you?
( Quite a lot, actually! )
...and Finally
The part you've been waiting for -- the end. This post is already long,
so I'll just refer you to the resources for now.
Expect another installment, though, and please feel free to suggest future
topics.
Resources
Tutorials
Digging Deeper
Another fine post from
The Computer Curmudgeon (also at
computer-curmudgeon.com).
Donation buttons in profile.