The book has some good advice, and some advice that I'll have to really think about before I decide whether I agree or not. The problem arises with the aggressive, combative way that the book is written. It often casually says something is terrible, but provides no examples. Or provides a single, simple example that isn't indicative of how the thing actually happens in a production code base.

Most of the advice in this book can be found elsewhere, from writers who don't make every sentence sound arrogant. I'd rather read those. ( )