Yes! And the book is free. You can download it in PDF if you want.

For some reason I've always been able to visualize version control systems and workflows pretty well and understand how they work. I used to host a CVS server when I was in college back in 2001 so my teammates and I we could collaborate on our lab projects. Then moved on to Subversion, which I used for a very long time. Then I worked at a small company who used Canonical's Bazaar and finally joined a big corp who used Git.

Throughout the years I simply developed some good practices that I applied to Git and that seemed to be enough. But, I'd occasionally get into this detached head state that I didn't really understand. And this happened often with my teammates at that job. They'd end up with bizarre scenarios. So I started reading the book and experimenting and was soon pretty solid in Git and ended up being the SME on that topic for our team. Everyone would come to me when they got stuck.

I'm still learning new shit about Git even 8 years later lol. But, the step from being a newbie to a normal user is really big.

Hi Linus!

I mean understand and know when or how to use every feature and command, I don't mean using git clone https://github.com/foo/bar occasionally.

Cloning a repo to build the source code isn't even remotely hard.

When you manage the repo of an entire team who work together on different release versions of a product using a very specific workflow with squash commits and cherry-picking? And when team members fuck up the repo's history with a bad git pull/push? Yeah, it gets more complicated.

"check the comments in the code."

(there are none)