This book jumped into the weeds way too fast. Which is good and bad. The label "power user" is appealing and I see the merit in knowing internals. But not with source control. It's a tool. I want to be able to use it productively and quickly and not have to remember MORE THAN two dozen commands. I'm not afraid of branching or merging, but then again, I don't care how these branches and merges are represented as objects on the filesystem.
And that's the problem. This book starts with the assumption that you're interested in the details and will cherish an under-the-hood look. Actually, for me, I really don't care. The details are certain to change. I'm convinced I'll be throwing this book out in a few years because it's outdated. I wouldn't be surprised if Git's hyphenated low level command structure disappears in a few years making this book nearly unusable - these commands are more developer tools than user tools.
With all the negative stuff out of the way, the book does contain a lot of good information. It's easy to read. It hits on a few interesting ideas on managing git. I found no issue following along with the examples - all of them worked fine for me.Get more detail about Version Control with Git: Powerful Tools and Techniques for Collaborative Software Development.
No comments:
Post a Comment