Sign in with Facebook
Friend Reviews
To see what your friends thought of this book,
please sign up.
This book is not yet featured on Listopia.
Add this book to your favorite list »
Community Reviews
(showing
1-30
of
148)
I really, really enjoyed this book.
As Avdi also points out in the book, it is important not to think of it as a "best practices" book. It's more of an exploration, a journey away from way most people build Rails apps to discover which alternative techniques work and which don't.
Some of these experiments end with the realization that the effort needed to introduce flexibility was simply too great to make the technique worthwhile. In my opinion, this is a good thing! Without these experiments, i...more
As Avdi also points out in the book, it is important not to think of it as a "best practices" book. It's more of an exploration, a journey away from way most people build Rails apps to discover which alternative techniques work and which don't.
Some of these experiments end with the realization that the effort needed to introduce flexibility was simply too great to make the technique worthwhile. In my opinion, this is a good thing! Without these experiments, i...more
Clear and well-written exploration of techniques that can be used in rails applications that can help with testability, separation of concerns, reducing coupling, and overall clean design. In reality each of those list items is interconnected, as Avdi succeeds in demonstrating.
Examples of some of the interesting parts was the idea of Exhibitors, factory methods using public_method, default arguments as a sort of dependency-injection mechanism, and bunches more. I definitely wish more rails progr...more
Examples of some of the interesting parts was the idea of Exhibitors, factory methods using public_method, default arguments as a sort of dependency-injection mechanism, and bunches more. I definitely wish more rails progr...more
Well-written although overkill for a blog! We used some patterns discussed in this book. I wouldn't follow some of the examples especially the tests! Although they can be sufficient to test logic in your app and I understand why NullDB or not interacting with databases for testing views logic is important (speed for instance), I think that as the app grows, you'd need to throw away some best practices.
Provided some great food for thought about how I'm currently building apps and "the rails way."
A book full of good ideas. A bit short though and in parts a bit off (the overengineered tagging part). The book is more an eyeopener for developers only familiar with rails standard way of doing things, than a reference or a pattern catalogue.
Good read. Code examples sometimes look over-engineered and are difficult to follow but the reasoning behind them is really well described. The book contains great summary section which acts as a good reference.
Great read. Every developer working with Rails should read this book. It got a little tedious at the end, but the summary scenarios and the appendix resources will make sure I come back to it at least once a week.
May 21, 2013
Igor Kapkov
marked it as to-read
May 20, 2013
Belehe
is currently reading it
May 02, 2013
Dan
is currently reading it
Apr 28, 2013
Saulius Grigaliūnas
is currently reading it
May 15, 2013
Daniel
is currently reading it
Apr 22, 2013
Louise
marked it as to-read
Apr 16, 2013
Emmanuel Joubaud
marked it as to-read
Apr 16, 2013
Orien
marked it as to-read
Apr 08, 2013
Henrik Loevborg
marked it as to-read
Mar 28, 2013
Arkadiusz Holko
marked it as to-read
view all 4 comments
Mar 09, 2013
Kode
marked it as to-read
Feb 27, 2013
Miguel Parramón
marked it as to-read
Feb 15, 2013
Rajashree Malvade
marked it as to-read
Feb 11, 2013
Sergey
is currently reading it
There are no discussion topics on this book yet.
Be the first to start one »
