The reference for writing fantastic Rails applications
You build web applications, and you love Ruby on Rails because it provides a framework for developing applications that are are fast, fun, and easy to change. Over time these applications can become bloated, development slows down, and changes to the codebase become painful.
This book was written to help you learn to detect emerging problems in your codebase; we'll deliver the solutions for fixing them, and maintaining an application that will be fun to work on for years to come.
In addition to the book (in HTML, PDF, EPUB, and Kindle formats), you also get a complete example application, and the ability to get your questions about Ruby on Rails answered by the thoughtbot team.
The book is written using Markdown and pandoc and distributed via GitHub. When you purchase, we give you access directly to the repository, so you can use the GitHub comment and issue features to give us feedback about what we've written and what you'd like to see. Give us your toughest Ruby questions with GitHub issues, and we'll answer. Last but not least, also included is a Ruby on Rails reference application. What the book describes and explains, the example app demonstrates with real, working code. Fully up to date for Rails 3.2.
This book is a work in progress. The book isn't finished yet, but that's the point! By getting involved now, you get access to updates as we make them as well as the ability to influence the content of the book.
I liked it, it shows a lot of patterns to improve rails codebase ( some things can be useful for plain ruby, but it is centered in rails ). Some parts of the book are a bit difficult to follow and you can get lost, I miss a clearer structure.
A good reference especially if you've been doing Ruby on Rails for years. You can refer the book when doing code cleanups, reviews and refactoring.
Warning: The book is a bit hard to follow, the structure is a bit weird. You don't have to read it from front to back. Pick a subject you're interested in and just have a look.
It is like a nice collection of good blog posts. It can be useful to check its content by titles ehen you need them. However, it doesn’t add a value when you read like a book, because the story focuses much technical solutions than the problems. So you learn their solutions and may not get the points which will lead you to your own solutions.
Wow. What a great book for any rails developer, specially if you are constantly refactoring code in ruby
The authors behind well known ruby gems as paperclip, voltage, shoulda, factorygirl, etc. made a great work in writing this book.
The first part describes many of the most common code smells in ruby, as duplicated code, large class, large method, shotgun surgery, etc, with a brief way on how to approach these.
The second part details the solutions started on the first part: Replace Conditional with Polymorphism, replace conditional with null object, extract value object, extract validator. etc
The third party describes the most important principles when developing in ruby/rails. Law Of Demeter, DRY, Composition over inheritance, Open/Closed are always perfectly summarised.
The whole book is of course full of examples illustrating each of the chapters.