Home > Articles > Programming > Ruby

Eloquent Ruby: An Interview with Russ Olsen

  • Print
  • + Share This
Pat Eyler interviews Russ Olsen about his new book, Eloquent Ruby, recommended programming practices, why it's beneficial to learn a new programming language, and why it's sometimes worthwhile to color outside the lines.
Like this article? We recommend

Like this article? We recommend

Russ Olsen (@russolsen) has just written Eloquent Ruby, which is already receiving praise from many in the Ruby Community. Since we don't normally think about programming eloquently, Russel and I took a bit of time to talk about what it means and how to do it. Enjoy!

You can also read an earlier interview with Russ, or my review of his earlier book Design Patters in Ruby.

Pat Eyler: Why Eloquent Ruby?

Russ Olsen: Eloquent Ruby grew out of my experiences trying to bring programmers new to Ruby up to speed on the language. It turns out that this is both very easy and very hard, in that order. The easy part is to teach the basics of the language. On one level Ruby is a very straightforward object oriented programming language. There classes and methods and instance variables and all the rest, and if you are a Java or C# programmer you can pick up those parts of Ruby in short order. Surprisingly, figuring out the more exotic aspects of the language is not that much more difficult. If you are a Java or C# programmer, then dynamic typing, code blocks and monkey patching will seem strange, but it's amazing how quickly most people grasp these ideas.

It's after they have the basics down that the hard part begins, usually in the form of some very pointed questions: What possible advantage is there to dynamic typing? What is a code block good for? Why would you ever want to change a class definition? Method_missing? Really? The questions are Ruby specific, but the problem is as old as the first programming language: There is a world of difference between knowing about a programming language and being able to use it the way it is meant to be used. The idea behind Eloquent Ruby is to speed people through that "I know the grammar but I kind of don't get it" no-man's land. In the book I talk about how Ruby programmers really use the language and why we do it that way.

Pat: What does it mean to program eloquently?

Russ: It means making the best use of your programming language. If you think about it, programs have two different functions: On the one hand they are mechanisms, little intellectual gears and widgets that do things when you feed them into a computer. But programs are also meant to be read by humans; maybe by the author this week, possibly by another programmer next week and conceivably by the 43rd poor soul who comes along in a few years. An eloquent program does both jobs well: It functions correctly and with a minimum of fuss, while at the same time communicating how it does its thing to the people who need to maintain it.

Pat: Learning another language makes us better speakers of our own languages. How does learning another programming language help us program better in our current language?

Russ: Every programming language is, in some sense, a fresh answer to the question, "How do you write code?" I think learning a new programming language is an exercise in starting over, in taking a fresh look at what's important and what's not. Programmers are people, and we tend to acquire habits; we do things a certain way just because that's the way we do them.

Learning a new programming language is a great way to break out of your habits. On the one hand, when you learn a new language, you will be spending at least some time way outside of your comfort zone; all by itself that tends to shock you out of your daily programming routine. On the other hand, learning a new programming language tends to get you talking to or reading new people, people who will look at the programming world a different way. As someone who has spent the past few years doing mostly Ruby and a little bit of Java, I know that the Ruby experience has changed the way that I do Java.

Pat: Eloquent speakers tend to be well read. How does code reading impact eloquent programing?

Russ: Reading other people's code is one of the keys to picking up a new programming language. If you think about it, no one learns English or Chinese by simply reading a book about English or Chinese and going off to invent their own sentences. A key part of learning a new spoken language is to talk to and read native speakers. In the same way, since every programming language is part technology and part culture, knowing how the language works is key, but knowing how people really use it is important too. For example, when they first stumble over method_missing, most new Ruby programmers assume that it's some kind of obscure error handling facility. You really have to go out and see what people are doing with method_missing to understand just how powerful being able to respond to calls to non-existent methods is.

How do you go about learning from other people's code? I wouldn't just sit down with a great mound of code and start reading. Instead I would start with a problem, with some code that needs to be written. Then go off into the Ruby standard library or into Rails or some other well respected source and try to find out how they have solved the same sort of problem. Personally, I like the "peek at the answer" approach. Take a look at how someone else has done it, get the general idea and then put the other guy's work away and try to do it yourself. If you get stuck, you can always check back to see where you went wrong. Best practices are all well and good, but the best best practice is to think for yourself.

Pat: Another factor in becoming an eloquent speaker is to spend time speaking. Code katas seem to be an approach to doing this with programming. What kinds of programming practice do you recommend?

Russ: When I was in college I had a part time job in the Dean's office. One of the things they would have me do every semester was to compile statistics on the student body, which in those days we did by hand. So I would spend an afternoon sorting through this huge pile of student records, averaging SAT scores and GPAs.

It was boring, but it was also interesting, because I could see a lot about the personal backgrounds of my fellow students, things that the average civilian wouldn't know about. The thing that struck me was that every one of the students was different. Some of them played the cello and some played baseball. Some were clearly very well off and some were from places that I wouldn't think of going into at night. And these were all people who were going to the same school, studying more or less the same thing.

That's a long way of saying that I don't think there is a single answer to the question of "how do you do it?" For example, I love Dave Thomas' idea of code kata and I'm really glad he put the time in getting it started. But it wouldn't work for me—I just have never done well with even the minimal structure that the katas provide. My favorite way to learn a new programming language is to think of some impossible task—build a whole database management system complete with SQL or something equally wild—and just give it a shot. I pretty much have a 100% failure rate with these projects, but the value is in what I learn as I fail.

But maybe the kata thing works for you—it certainly seems to work for a lot of people. So do that. Or do something else. It doesn't much matter what exactly you do—it's the doing that matters.

Pat: Finally, if you could recommend one practice to programmers, what would it be and why?

Russ: Actually I have two bits of advice: The first is follow the rules. Every programming community has a set of best practices, ways of doing things that have been hammered out through experience. You need to pay attention to those rules, especially when you are new, just learning. Mostly you want to color between the lines, because the lines were put there for good reasons.

But you also want to understand the why behind the rules. I tried to do that in Eloquent Ruby as much as I could, to the point of explaining why Ruby programmers indent with two spaces. Don't just take the rules as handed down from above; get inside of them, figure out why they are there.

Which brings me to my second bit of advice: Don't be afraid to break the rules. Like the pirate code, programming best practices are more a set of guidelines. If you know the rules and you know the why behind the rules, then every now and then you can color outside of the lines, confident that you are doing it for a good reason.

  • + Share This
  • 🔖 Save To Your Account

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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