This book is a lot less "here's how to write testable code, with lots of examples" and is more philosophical in that it conveys *why* testing is important and how to get into the habit/frame of mind for testing. There are some explicit code examples in the book, mostly to illustrate points rather than to provide reusable template code. However, the book is quite inspiring and does a good job of enticing the reader to become a better programmer, with or without testing (preferably with, of course). The biggest surprise for me was that the book didn't just cover aspects of unit testing, but also ideas such as technical debt and the advantages of developing in an environment as close to production as possible. My biggest concern is that half the book is essentially copy/pasted from the authors blog, even as far back as 2008 (if memory serves, I could be wrong on the date). However, the author has updated the information, and it is surprisingly relevant and fits into the book much better than I expected after seeing the first "the following is a blog excerpt" chapter introduction. Overall, I would recommend this book, though potential readers should not expect a cookbook with a lot of example code.