Home > Articles > Programming > Ruby

Refactoring Ruby: An Interview with Jay Fields

Neal Ford interviews Jay Fields about his new book with Shane Harvie and Martin Fowler, Refactoring: Ruby Edition, why they wrote the book around Ruby and not Dynamic Languages in general, and why he'd take a powerful language over a powerful tool anyday.
Like this article? We recommend

Like this article? We recommend

Neal Ford: Why choose Ruby as the target and not do a broader book on Refactoring in Dynamic Languages?

Jay Fields: I considered it. The thing is, I've never delivered a production application in any other Dynamic Language. I'm pretty passionate about the opinion that you should only write about things that you've spent real time working with.

It's entirely possible to distill someone else's experiences. Martin Fowler is amazing at capturing knowledge and creating helpful content that will live on outside of one person's mind.

However, Martin Fowler is not the norm. The amount of garbage generated by average programmers making terrible assumptions is appalling. I refuse to be an author who's books are based on speculation. To assume that I could write about refactoring Perl, Python, or any other Dynamic Language without actually doing it would lead to, at best, a waste of the readers time, at worst, I would be to blame for mistakes in production codebases.

I've personally used every refactoring in Refactoring: Ruby Edition. If the refactoring is in the catalog, I've found a context in which I thought it was appropriate. When you read the book, you can count on the fact that what you are reading about has been successful in the past. There's no speculation.

Programming is hard enough when you follow good advise.

Neal: Do you think that the lack of sophisticated tool support discourages people from doing needed refactorings in large code bases?

Jay: Yes. Some people take the leap. When I'm doing Ruby I miss "rename method" and "extract variable" (I use TextMate). But, in general I find that with a more powerful language I miss the refactoring support less. Plus, the interesting refactorings can't be automated anyway. Would a powerful tool be helpful, absolutely, but it's definitely not required.

However, none of that really matters. The people making decisions give Ruby a look and dismiss it because of missing tool support without giving it the time it would take to realize that you don't strictly need a powerful tool if you have a powerful language. It's a shame. But, then again, it gives all of the rubyists an edge.

Neal: Given that you've worked on large scale .NET, Java, and Ruby projects, do Ruby projects tend to end up with less, the same, or more refactorings?

Jay: Ruby projects tend to have far less and much smaller refactorings.

Java and .NET both require you to have strong knowledge of patterns. Patterns are cool and fun to refactor towards and away from. Unfortunately, they are also a sign that we are trapped by our language.

You often run into a roadblock when using Java or .NET and you introduce an elegant pattern to solve the issue. You pat yourself on the back and probably show some team-mates your beautiful implementation. A few weeks later, a corner case breaks the whole thing down. You spend 2 days refactoring away from the previous perfect solution to another, less elegant, but appropriate pattern. It's a lot of "introduce variable", "remove middle man", moving files and deleting files. The result is beautiful... for Java or .NET.

We don't have that in the Ruby world. You solve problems with less code. You metaprogram your way out of repetition, or delegation, or structural duplication. When corner-cases arise, a few tweaks usually do the trick. Which leads back to why tool support isn't strictly required. But, you have to make the leap to experience it.

Neal: What percentage of the refactorings you've identified are different from the original Refactoring book? What do you think drives the differences?

Jay: I like to tell people that 30% of the content is new. It might actually be more. There's not a sentence in the book that hasn't been judged by the authors. The book definitely started out as a code example port, but it's very far from that in it's final form. Stuart Halloway gets credit for pushing us to create new content. I think a port of the original would have been valuable for the Ruby community; however, I'm much more proud of the final product.

Martin and I differ on whether you should bother to read this version if you read the original. Yes, a lot of the content is extremely similar. However, some of the Ruby specific stuff isn't available anywhere else. Several of the refactorings that Shane and I spent months describing were really helpful to us and can save a Rubyist a lot of time. At worst you can skim the information you already know and still get the benefits of reading the new content.

Neal: What is the fastest land animal?

Jay: Me, looking for a drink after a day of discussing process instead of coding.

Neal: Do the powerful features of Ruby (i.e., meta-programming, runtime evaluation, etc.) make it harder to think about refactorings? Do you think that discourages refactoring?

Jay: I think problems are solved differently. When you have more power you tend to create different solutions. Sometimes they are later determined to be "hacks". But, most often the solutions are less code, easier to understand (more straight-forward, less pattern), and perfectly adequate. And, most code with those characteristics doesn't need to be refactored very often.

I don't think it's harder to think about refactorings in Ruby though. In fact, with less code, it's usually more more obvious how things need to change.

Neal: Do you think we'll ever have tools for refactoring as sophisticated as the ones for Java? Why or why not? Does it matter at the end of the day?

Jay: I think there are people who benefit from sophisticated refactoring tools, so I imagine they will be created. But, like I said previously, when your language is powerful, it really doesn't matter at the end of the day. I've been doing a lot of Clojure these days and it's only reinforced this belief. Clojure refactoring support might actually be worse than Ruby, and I still find myself significantly more productive than when I work with Java or .NET.

I'll take a powerful language over a powerful tool anyday.

Neal: Which refactoring that you guys identified surprised you the most?

Jay: It took so long to write the book that I can't remember specific refactorings that surprised me. However, I do remember being surprised by how many additional refactorings we identified. Once we started writing new material additional material kept emerging. I really started thinking that there would be less than 10% of new material. I was definitely wrong, and I'm glad I was.

Neal: Given all the work and innovation you've done for Domain Specific Languages in Ruby, do DSLs lend themselves to refactoring as much as traditional Command/Query APIs?

Jay: That's really a question that requires a lot more context. I'd say in general there's little difference when it comes to refactoring; however, outside factors such as who is using the DSL impact whether it's even possible to refactor a DSL. If you own all the DSL using code, you have freedom. If others rely on the code, a refactoring can be tricky business.

Neal: What is the role of testing for refactoring in Ruby? Do different levels of testing (unit, functional, integration, user acceptance, etc) affect decisions about refactoring? What about newer testing frameworks like RSpec and Cucumber?

Jay: I really don't see any difference in what level of testing I do based upon the language. In Ruby and any other language, Refactoring without tests is a silly idea and an easy way to look like a fool. The Ruby community does tend to have a vibrant testing community; therefore, refactoring is probably more prevalent. However, the unclear view of testing best practices plagues the Ruby community just like everywhere else.

The newer testing frameworks are good for pushing us to the next level of maturity; however, the Ruby community is just as good at failing with the new tools as the Java community is at failing with JUnit. There are contextual testing best practices, but they're so young it's impossible to declare any of them effective widely.

No one has figured out how to test well in any language.

Neal: Do you think that refactoring Rails projects is easier or harder than non-Rails projects? Why?

Jay: I think the only Ruby work I ever did was with Rails, so I won't bother to speculate. (I'm sticking to my stance from my first answer.)

Thanks for taking the time Neal. It's always a pleasure.

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