Home > Articles > Programming > Ruby

An Interview with Obie Fernandez on Rails 3

Russ Olsen talks to Obie Fernandez about his new book, The Rails 3 Way, 2nd Edition, the most important Rails developments over the last few years, and what he's up to at Hashrocket.
Like this article? We recommend

Like this article? We recommend

Russ Olsen: First, congratulations on the upcoming publication of The Rails 3 Way. The Rails 3 Way is actually a new edition of your 2007 book The Rails Way. I notice that virtually the first thing that you talk about in The Rails 3 Way is Bundler, which didn't exist when you were writing the first version of the book. What do you think are the most important developments in the Rails world in the past few years?

Obie Fernandez: Well, maybe it's the obvious answer, but I can't think of anything more important that the merge with Merb, resulting in Rails 3. That event cemented the position of Rails as the one dominant web framework. It reverberated across the plains of open source as proof that competing frameworks can cooperate and thrive. I think it also gave the community the freedom to invest more heavily in pushing Rails forward without worrying that it might be a waste of time. I never bought the technical reasons to hate on Rails—I considered them a push towards premature optimization. What we're seeing now is that you can squeeze a ton of performance out of Rails without sacrificing the ease of development that made it such a joy to use in the first place.

Russ: One of the things that is new in Rails 3 is the fact that it comes packaged in what seems like 500 separate gems. Do you think that this is a good idea?

Obie: Yes, as long as it's properly managed, and Bundler seems to do a good job with that. Modular, de-coupled design is a great thing and a big improvement from the mishmash we had before.

Russ: Is there anything in Rails 3 that you would have done differently?

Obie: I would have liked to have seen a little more thought put into ActionView. The rendering system, particularly around layouts and partials, is still very tricky and full of opportunities for improvement. It would have been nice to switch the entire test suite over to RSpec too, but I realize that's never going to happen. The existing Test::Unit-based tests are good enough.

Russ: Did you discover anything that you didn't know about Rails in the process of doing the second edition?

Obie: Too much to describe here properly. Rails has a very dynamic community, and the original edition of The Rails Way was finished in fall 2007. That's 3 years of advancements, during which I spent a lot of time growing my business instead of heads-down coding. There's just so much I learned by exploring and explaining the new stuff. ARel, Active Model, and Devise are just a few examples, and the list really could go on and on.

Russ: I'm still spending much of my time working on a largish Rails 2.X.X application. Do you have any advice for folks like me when we finally come to porting to Rails 3?

Obie: My strongest practical advice is to have a comprehensive integration suite in place before attempting to upgrade. Also, upgrade one aspect of your application at a time. For instance, start with Rails 3/Ruby 1.8.7, then go to Ruby 1.9.2. If you're upgrading to Capybara 0.4.0, leave that until after the Rails/Ruby upgrades. That particular leap is a beast of its own that has eaten my last 3 days.

Russ: The original Rails Way topped the scales at 912 pages. How did you approach the task of reworking such a large book?

Obie: Iteratively. I knew the whole book would need to be revised. What complicated matters is that I had to start the work much before Rails 3 was completely defined and ready.

The first step was to get the book's source material into a usable format. The first edition was authored in Microsoft Word, and I was not eager to repeat that horrible experience. Thanks to some crucial help from Eliza Brock and others, we were able to take MS Word output and convert it into OpenOffice XML and then use XSLT to turn that into LaTeX source files and store the entire project on github.

Once the source material was text-based and in source control, collaborating with others was much easier. I started hosting "TR3W sessions" in my living room, where Tim Pope, Jon Larkowski and other guests would hang out and help me go through the arduous process of the rewrite. I'd plug my MacBook into my big-screen TV and mirror the screen so that the other folks in the room could see what I was doing as I did it. I'd ask, "How does this read?" and people would give their comments and suggestions.

Tim was particularly helpful because he's such a speed demon with code. I'd point to a particular code sample and ask if it still worked, and almost before I got the words out of my mouth he had typed it in and executed it and verified its operation. His encyclopedic knowledge of Ruby and Rails was indispensable and saved the project hours of tedious research.

The revision process proceeded chapter by chapter, but we did jump around a fair bit to accommodate our moods. There's only so many weeks you can spend dissecting the finer bits of Active Record behavior before you want to jump into a lighter, easier topic such as caching or authorization. The little wins filled in the gaps between the bigger wins, and eventually most of the book had been revised.

Russ: I notice that you rearranged a fair bit of the content in the new edition, particularly in the early part of the book. Did you do this because of changes to Rails, reader feedback on the first edition or some other reason?

Obie: I've always wanted the book material to build on itself along the lines of how a Rails process bootstraps and handles a request. So Bundler and configuration settings had to come first. But for the second edition, I decided that it was important to discuss routing and REST before diving into the dispatcher. That was the main change in the early part of the book.

Russ: Do you have any other literary projects in the works? Any plans for a third edition?

Obie: No plans for a third edition yet. As for my grander literary ambitions, the answer is yes. I would like my career to point me in the direction of being able to write full-time well into my older years. Jerry Weinberg and Martin Fowler are two of my heroes in that respect, and to follow their lead, I can't stop writing now. I have a manuscript that is over two-thirds finished about the business of custom web development that I'll give attention to again in the coming months. Projects in earlier stages of development have to do with careers in web programming and other topics that I hope will give me exposure to an audience beyond the Ruby community.

Russ: Along with being an author, you are also the editor of Addison-Wesley's Professional Ruby series. Can you tell us about any other upcoming Ruby or Rails books in the series?

Obie: Well, it's an exciting time to be a fan of this series. Michael Hartl's Ruby on Rails Tutorial is selling like hotcakes and garnering a ton of critical praise. Tammer and Chad's AntiPatterns book is also selling well and helping Rails people of all stripes avoid (or fix) the kinds of mistakes that we've painfully learned over the last few years. As for upcoming titles, your new book Eloquent Ruby should be out early next year and will help our readers mature their understanding of Ruby idioms and style. We also have an exciting title in early development that is sure to be a winner: Durran Jordan, author of Mongoid, is working on a hard-hitting new book NoSQL The Ruby Way. He's got serious hands-on knowledge with production use of NoSQL in complex, high-scaling environments. I'm sure our readers appreciate the extent to which our authors are practitioners of their craft.

Russ: You are also the founder and guiding light of Hashrocket. What have you all been up to down there in sunny Florida?

Obie: Thanks for asking. We've been growing—not just in numbers, but also in the arts and discipline of software craftsmanship. I've got a great bunch of people with talent and enthusiasm for taking care of our clients like none I've ever seen before. It really makes me beam with pride to talk about our "Rocketeers."

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020