Like ExtremeProgrammingExplained, this book has very short chapters. Short chapters work well for those of us who must read in short iterations (train commutes, kids' naptime). Short chapters also work well with the way Beck steps through his two TDD Examples. I found the brief summaries at the end of each chapter very effective. Short feedback loops.
As with his other books, I enjoyed his concise, humble, and pragmatic writing style.
The one thing I believe the book lacked was enough source code. After reading AgileSoftwareDevelopment/PrinciplesPatternsAndPractices, I had grown accustomed to seeing full snapshots of the source code as it evolved.
I'm still in Part 1 and the writing style reminds me of Why's (Poignant) Guide to Ruby. In fact, I'm thinking that this might work better posted online with comic illustrations. As a book, it just seems a bit too informal. For me, the second example drew out the particular approach too far. I would have preferred a change in style if the contents were worth communicating. I'll probably update this when I finish but these are my second impressions. -- JasonYip
![[Home]](/wiki.gif)