I think it was Donald Knuth who once said we write software not to convince the computer to do the right thing but to convince our peers that the program is doing the right thing.
The beauty of your post is that it convincingly brings across that the version control "structure" is part of this software, and must be "written" towards our peers too.
Under pressure, the temptation is high to keep whacking at the code until we think it "works". Same with the commit history. And if we are offered an hydraulic press... squash away! (not)
The keyword here is "textbook"
The beauty of your post is that it convincingly brings across that the version control "structure" is part of this software, and must be "written" towards our peers too.
Under pressure, the temptation is high to keep whacking at the code until we think it "works". Same with the commit history. And if we are offered an hydraulic press... squash away! (not)