7 of 12 people found the following review helpful
paper beats screen,
Verified Purchase(What's this?)
This review is from: Pro Git (Paperback)
This material is available online, and so the order-one question is whether anyone should buy a paper copy.
I think paper beats screen (to use a RPS sort of phrase), so I purchased a paper copy. I am glad I did. Within an hour, I had come to understand things about git that had escaped me, despite studying a great many websites and manpages. My copy is gradually accumulating marks in the margin, postit notes for important pages, and so forth. Thus, its value (to me, anyway) grows. As is always the case with book, the reader can *find* things in it, because the mind remembers things like "halfway down the left-hand page, five or seven or nine pages past the chapter start". Bookmarks in HTML or PDF are a laughable substitute for this.
I also bought the book to support the author, since he has been so kind as to put the material online for free, and I'd like to buy him a coffee, from the royalty from my purchase.
You'll notice that I've not yet *reviewed* this book. Is it any good? Does he know what he's talking about? Can he explain things? Does he cover the right material, in the right order? Yes, yes, yes, yes, and yes. The book is very nice, gem-like in spots. I'd recommend it to anyone. If git were simpler, or less powerful, or if there were a lot of good existing books, there would be no need for this book. Git is far up there on the importance-and-complexity axis, but down near the origin on the explanation-in-books axis. This book made a big change in the graph.