I think that comic also accurately describes the problem leading to that as well: it dismisses any explanation of Git&#x27;s underlying mechanics and repository structure as ignorable rambling prefacing the command to do what you want.<p>It took me a while to learn git, and the explanations I went through involved the underlying structure of the repository.  They seemed excessively complicated at the time, compared to memorizing commands for cvs and svn.  However, now that I understand that underlying structure, every new git tool or function just provides additional means of transforming the repository structure I have into the repository structure I want.<p>You don&#x27;t stop learning programming once you&#x27;ve memorized a rote sequence of steps to run a half-dozen algorithms on a hash table.  And you don&#x27;t stop learning git once you&#x27;ve memorized a rote sequence of steps to run a half-dozen algorithms on a git repository structure.<p>I don&#x27;t mean that to suggest that git has no room to improve in its UI; far from it.  But that particular comic seems to excuse a self-perpetuating problem of not wanting to learn something useful, and instead relying on people who <i>did</i> learn that useful thing while simultaneously belittling them for knowing it.