The steep learning curve and lack of good documentation has always been a problem with complex open source software like Chef so it is good to see an author providing material.
With technical books it important to understand the scope of the book. Is it a Reference book, an introduction or what.
The title says it is a Cookbook and that is what it is. It is a tutorial for getting up and running in chef. It is very comprehensive in provide the commands and the tutorials to learn to do stuff in chef. It is a "doing" book that you need to follow along.
Personally I think it could be improved by adding more diagrams and explanations and a bit more structure to the information. It just flows over the pages so it would be better if each piece of tutorial started at the top of the page so you can reference it more easily later. He only give a couple of lines of explanation before launching in to the commands to do the particular task so a bit more explanation of the why as well as how what be good.
In summary, good information to a currently poorly served area but not a book for absolute beginners.
Cookbooks are related to quite common software so it's not hard to find them applicable. What I was missing was something like a walkthrough to create such a cookbook (Chapter 4 is not enough): for instance some of the particular recipes could have been presented in a more thorough way to show the way to create such a cookbook.
I really like Chapter I (Chef Infrastructure) - it's a nice overview, but in my opinion in needs more love (to get more elaborate). What I didn't like? Section about testing the cookbooks is far too brief (as the topic is quite complex).
The best proof of this book's value is that I was getting back to it quite often.
After picking up basics of Chef framework, Chef Infrastructure Automation Cookbook is a must read. Among Chef framework itself, it also covers techniques such as testing, as well as integration with tools and technologies like Vagrant and AWS, with excellent examples. Management of cookbook dependencies is lot easier with tools like Berkshelf, and author follows that practice from the beginning to the end.