| Home | Biography | Speaking | Articles | Books | Music |
I finished this book a couple of weeks ago - I forgot to write my usual book review and since I have some free time now I thought, “hey, time to write that review!”
Overall, I think the book serves its purpose. It does a decent job in laying out the tools and processes developers should follow to make the software they write better. This includes testing, continuous integration, DI/IoC, and other related topics. The book is written well and I think it’s a book that any developer can gain something from by reading it (although I think it serves the less experienced crowd better).
That being said … there were some statements and points made in the book that I didn’t get or that I think are errata. That’s fine - I’ve had my own share of mistakes in my books - but I think that they should be pointed out, especially with a book that’s trying to get developers to write better code:
What I liked in the book overshadows what I didn’t like or disagreed with. Even if I disagreed with a statement, at least that shows that he got me to think about a point he was making. Pick it up and read it if you can. It doesn’t go as far in-depth as I would’ve liked, but it’s still a good read.
Published: 08.21.2008 10:33:42 AM CST