This book helped tie together my understanding of OOP best practices in Ruby and has produced immediate benefits in the quality of code I'm writing. It contains great examples of refactoring code, along with checklists, red flags and questions to ask yourself throughout the design process.The author does a great job of following the development and improvement of a sample app throughout the book (an app for a bike shop). The continuous narrative helps you see how the pieces fit together, though a few examples from other domains would have been helpful in some places. At the same time, that's really an exercise for the reader.I found Chapter 4's discussion of creating a public interface particularly helpful in determining the proper responsibilities of objects by "Asking for 'What' Instead of Telling 'How'." The continued discussion of messages when identifying duck types in Chapter 5 helped reinforce the concepts. The chapters on modules and testing also helped tighten up my thinking on a few topics.As I've shifted from hobbyist to freelancer to full time developer over the past few years, there have been a few books or tutorials that have really helped me improve (along with bugging friends and countless hours of troubleshooting), and this is definitely one of them. Highly recommended. I was skeptical that this book would be anything but a refresher. Thirteen years writing software, most of it object oriented, suggested my experience would make it all review. Especially since the necessary "trivial" examples of a book cannot compare to real world.Surprisingly POODR stands in both worlds, presenting relatively simple problems while remaining imminently practical. It has challenged my beliefs about how unentangled a production application is capable of being. I will be pushing myself to stay true to the concepts in upcoming implementations.Let's see where this takes me.
The tone in this book is super condescending and preachy but otherwise the lessons are good.
—Matt
too boring, too general.p.s. if you're a ruby/oop newbie, maybe, it's ok to read it.
—AlyssaBianca
If you do any sort of object oriented development then you should. Read. This. Book.
—Mandalizbeth
Awesome. Every object-oriented programmer should read this book.
—Andm
One of the best books on the Ruby programming language!
—sofia
