I worked with a guy who earned several "Tee Hee" awards for my team's repos. After three years of working with him I knew most of the ins and outs of all the subtle and complex ways git has to revert, rebase, merge, resolve conflicts, and generally cajole a code base back into something that builds. I even got to a point where, with only a medium amount of effort, a programmer could look at the commit history and sort of understand what happened, or at least not miss any of the important changes.

I appreciate that git, for all its complexity and opaqueness, at least had some way to fix nearly anything, if you could master it.