Another example of Git's inherent complexity: Git Flight Rules. In the intro, she quotes Chris Hadfield from An Astronaut's Guide To Life:
Flight Rules are the hard-earned body of knowledge recorded in manuals that list, step-by-step, what to do if X occurs, and why. Essentially, they are extremely detailed, scenario-specific standard operating procedures.
This is an astronaut talking about a type of documentation useful in flying the space shuttle. Kate's premise is that we need something similar -- a collection of detailed, non-obvious solutions for weird but not-unusual problems painstakingly collected through hard experience -- for Git. This popped up on Pinboard's "Popular" page today, which attests to the fact that lots of git users see value in this.
My takeaway is that Git imposes a degree of mental overhead which at least approaches that experienced by astronauts operating a space shuttle. I'm not saying it's impossible to understand or that it's not worth understanding; but that this amount of mental overhead is overkill for the comparatively simple needs of prose writers.