Home > Articles > Programming

Fluent Learning: An Interview with Rebecca M. Riordan

C# compiler developer Eric Lippert interviews Rebecca M. Riordan, author of the new book Fluent C#..
Like this article? We recommend

Like this article? We recommend

Eric Lippert: The first thing that struck me about your book is that its “look” is very different from every one of the hundred other technical books on my shelf. It has a strong “steampunk” design aesthetic, it uses large display fonts, and so on. What motivated these design choices?

Rebecca M. Riordan: Firstly, and most importantly, there are pedagogical reasons for the heavy emphasis on graphics. Most of us are familiar with the idea that most people favor one sense over another, and appealing to a person’s favorite sense helps them learn. Demographically, most people respond best to visual input, but research has shown that in fact everyone learns better when information is presented to as many senses as possible, partly because our brains simply enjoy the complexity of multiple forms of input, and the more fun our brain is having, the more likely we are to remember whatever it is we are doing. Also, information is more likely to be recalled if it is accessed using the same pathway that was used to store it. It turns out that there’s a great deal of variation in how people think about problems, and we can’t simply say “this is this kind of information, so I need to teach it in this way.” By presenting information in multiple ways, it’s just statistically more likely that it will be available along the pathway the user is using to “look” for it.

Secondly, the Fluent books really are very different than anything else on the market, and I wanted them to look very different to emphasize that fact.

As for the steampunk design aesthetic, that was a combination of personal preference and practicality. I personally like steampunk very much, and it seemed to me to be a fun (and slightly whimsical) fit for presenting technical information. From a practical viewpoint, the Victorian images are widely available and old enough to be in the public domain, which made sourcing the raw images reasonably straightforward.

Eric Lippert: What challenges did you face, having chosen an unusual form factor for a modern technical book?

Rebecca M. Riordan: The biggest challenge was on the production side. Particularly since this was the first book in the series; we stumbled a lot over simple logistical issues like getting Mac versions of the fonts and how to handle the technical review and copyediting when the manuscript was in InDesign rather than Word. The second book was easier. I’m hoping/praying/wishing really hard that the process will continue to get easier as we go along.

Eric Lippert: I’ve edited a number of “beginner level” programming books; in doing so I’ve often noticed that authors have a difficult time choosing in what order to present complex material. Some authors concentrate on getting the reader to create working code right away even if the reader might not understand it all. Some concentrate on getting the fundamental concepts down first. Some simply present the material in the order they learned it themselves. Did you have some sort of high-level policy for deciding how to order the presentation of various concepts?

Rebecca M. Riordan: There’s most definitely a policy for how the information is presented. It’s the result of the couple of years I spent researching cognitive theory and instructional design, before designing the Fluent series. It turns out we actually know quite a lot about how the brain learns and how to teach, but it just hasn’t filtered through to the technical writing community.

One of the things I learned is that we think in patterns. It’s almost impossible to remember, much less recall, anything unless it’s attached to something else. I think the greatest failing of technical literature—including many of the books I’ve written myself—is that we do such a rotten job of presenting the pattern of the information, how all the bits fit together. Our collective failure to do so makes learning so much harder than it needs to be, and that seems like such a shame to me, and such a waste. So the Fluent books, on both the macro and micro level, start with the overall pattern, and then present details in that context.

Once the patterning is in place, I don’t think the specific order in which information is presented matters quite so much. If I’ve done my job well, the reader should always know how this bit of new information fits with what they’ve already learned; in other words, they always know its context, so the issue is simply one of making sure that they know everything they need to know in order to understand this new bit. Of course, I say “simply”, and it’s not simple at all. Thinking through issues like “can they understand control templates if they haven’t learned about resource libraries yet?” is non-trivial, at least for me.

Eric Lippert: C# is now a quite large, fully-featured general-purpose programming language. Were there aspects of the language that you felt were particularly difficult for beginners?

Rebecca M. Riordan: Concepts like lambdas and delegates are complex and can be scary, but in my experience, beginners seem to stumble most often over programming syntax that is almost-but-not-quite like natural language. Boolean operations are a prime example—the logical “or” and the natural language “or” are polar opposites—and I spend a lot of time in the book on those sorts of issues. But some very smart people have devoted their careers to making programming languages in general and C# in particular clean and logical. I think it’s just a matter of finding and presenting the underlying structure of the language in a meaningful way.

Eric Lippert: Indeed, we do try hard to make C# both clean and logical, though that is not always easy as a language evolves. When you were working on the book, did you learn new things about the language yourself?

Rebecca M. Riordan: I always learn things when I write. It’s one of the things I love about what I do for a living. With this particular book, I spent a lot of time winnowing out the underlying structure of the WPF class library, which I’ve been using for years but never really thought about clearly. I also had to do some careful research for the patterns and practices sections. Prior to writing the book, I’d really only explored the patterns that I’d used in various applications, and that kind of ad hoc knowledge isn’t nearly good enough when you’re taking responsibility for providing other people with the overview they need to explore on their own.

Eric Lippert: You’ve written a number of books about databases; what led you to switch gears to write about programming languages instead? 

Rebecca M. Riordan: Funny, it doesn’t really feel like switching gears to me. My first few books were database books, but recently I’ve written on a number of subjects from interface design (Seeing Data) to web development (Head First Ajax). I think of myself as a writer and software designer, not a database person. There’s a wide range of subjects that interest me personally and professionally, and when a subject interests me, my first instinct is to start thinking about how to teach it to somebody else. It’s part of how I learn.

Eric Lippert: How did your earlier experiences writing books influence how you approached writing this book?

Rebecca M. Riordan: The Fluent series is a direct result of my dissatisfaction with my earlier books. They’re not bad books, mind you. I’m a competent technical writer. But it all seemed so much harder than it ought to be, both to write and to learn. Like so many of us in this industry, I spend a lot of my time on the bleeding edge, studying and learning just to stand still. I decided there just had to be a better way. So I went down to the local Borders and found a wonderful book aimed at elementary school teachers, What Every Teacher Should Know about Effective Teaching Strategies by Donna Walker Tileston and discovered that there is a better way.

It turns out that there are people who know an awful lot about how we learn and how to teach effectively; they’re just not the people writing technical tutorials. (And I don’t mean to cast aspersions on my colleagues. Nobody gets to know everything.) So, a couple of years, several hundred books, papers and studies of cognitive science and instructional design (and information design and graphic design and book layout...) and several false starts later, Fluent Learning is the result of my research into what these amazing folks in the teaching profession have figured out.

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