You should read Ruby Science

No, I don’t think so.

Hi, I see that this book, is using Rails 3.2 and with Rails 5 coming soon. I wonder if it’s a good idea to buy it. Do you plan to do a update of the book?

I’d say Ruby Science is valid past any version of Rails. It is an exemplary book on thinking in OO terms in Rails apps, but not depending on specific framework features.

I agree with @pedrosmmoreira. The techniques in Ruby Science are mostly about Ruby regardless of framework. There’s a chapter on Single-Table Inheritance, but I don’t expect that advice to be obsolete due to the arrival of Rails 5.

This book had a strong impact on the way I approach coding. I would highly recommend it. If you think about whatever your billable rate (or equivalent salary) as a developer is and then imagine making improvements that will provide dividends on every hour you spend into the future, the cost suddenly looks pretty trivial.

3 Likes

Thanks @geoffharcourt. You are right.

I’m currently reading Ruby Science. It’s very handy to read a ‘problem’ (eg. extract method), and then watch the weekly iteration on that specific problem.

Love the book, great read.

This is probably my favourite book from you guys and I’ve read them all.

and it’s even more helpfull to combine the book with the Refactoring trail on upcase. This way you can put the stuff you learn immediatly into practice.