I only partially agree. Git is a complex project, developed to help with the management of the Linux kernel source code. Because of that, the original audience

I only partially agree. Git is a complex project, developed to help with the management of the Linux kernel source code. Because of that, the original audience was technically very advanced and maybe didn't need any higher layer of abstraction, nor a proper product development roadmap. The problem appeared when people like I started basing our workflow on it ^_^. There are a few good books[1] and tutorials[2] out there, but I totally agree that the official documentation is only useful as a technical reference. [1] Mastering Git, https://www.packtpub.com/product/mastering-git/9781783553754 https://www.packtpub.com/product/mastering-git/9781783553754 [2] Atlassian Git tutorials, https://www.atlassian.com/git/tutorials https://www.atlassian.com/git/tutorials