Split into seven chapters, all equally sprinkled with phrases that are disjointly written and that don't get a point across, and some that make you think the book was written using some speech-to-text software ("Vendor locking" anybody?) , this book which "is for PHP developers who work in teams on complex projects" has given me an aversion to seeing three little words printed alongside each other ("the PHP code").
He mentions some of the huge omissions on things like code sniffing/syntax checking, unit testing, PEAR, etc (and there's a lot missing). He also points out what he sees as one of the largest problems of the book:
The book focuses on what the author thinks and his thoughts on the subject are written in such a manner, that once you put in the immense effort in trying to understand what he is attempting to communicate, that you are left with the impression that there are no alternatives; that X & Y & Z are the true and tested ways of doing things in PHP and there are no two ways about it.
Overall, Ken wouldn't recommend the book to much of anyone and suggests that the money put towards the cost of the book would be better spent on something with much more return.