I find that learning git oftentimes has to do with remembering how to do things, not understanding them. Generally, Git can be summarized fairly easily, but wh

I find that learning git oftentimes has to do with remembering how to do things, not understanding them. Generally, Git can be summarized fairly easily, but when it comes to workflow, I think you just need the practice of doing it. Branches and submodules make a bunch of sense, but I think it's deceptive and fruitless to describe the whole fetch-pull-rebase-reset business as something that's trivially simple and logical. I don't know if those four followed from one flow of thinking, or whether they just co-exist as option for handling your project. The Django Book is one of my favourite programming guides ever, because it describes why the different features and shortcut functions exist, which gives a flow (chart) to the tools available to you in Django. With Git, I often just see a lot of users bickering over whether they should rebase, pull, and whatnot, and people start sounding like they just advocate their own workflow instead of a logic intrinsic to how Git was designed.