I can't wait for it being finished. It was awesome to see such DCI examples which I can relate easily to my daily work. Showing a granular thought process as a kind of reasoning for seemingly more complex code is very helpful for convincing my colleagues to change our code architecture style.
I found this book kinda lacking, it's true that I don't have the latest version of it but still; the examples were a little bit vague. On another note the book have a lot of resources and start a discussion on how to create applications in general and with Rails in particular.
Beginning of the book is all right. However at some point author jumps from pure Ruby to Ruby on Rails, which is not exactly what I expected from the book. Maybe the title should be different? I think the book would benefit greately if the author stayed with just Ruby.
Jim offers some pretty powerful ideas about forwarding and delegation using ruby. I came away knowing more than I when I started the book. A comprehensive example of how the ideas could improve a business problem would help them stick.