If you want to master git skillfully, it is absolutely enough to read pro git. If you want to read more when you are full and have nothing to do, this book is also OK.
80% of the technical books in the world just copy the technical documents once, with a few words of explanation, and few have insights.There are some things about the author in this book. It can be seen that the author is professional, but his description is not vivid enough. For example, when he was a consultant, he gave a proposal to the customer, and there is a lack of practical examples. You have learned a command, but you don't know how important it is and how often it is used.I believe that as a version library consultant, the author must have a lot of practical experience in this field. It will be 100 times better to talk about the problems that customers often encounter. Just talking about theory is zero.
The highest level of technical books is to be able to combine theory with practice, so that they can understand deeply and thoroughly. No matter how thick the theory is, it doesn't work. After reading it, they still don't know how to use it.Unfortunately, there are not many technical writers who know this truth, and they all think that only theory is lofty, which is really bad.
