Programming Books C Java PHP Python Learn more Browse Programming Books
  • List Price: $34.99
  • Save: $4.34 (12%)
FREE Shipping on orders over $35.
In Stock.
Ships from and sold by
Gift-wrap available.
The Art of Readable Code ... has been added to your Cart
+ $3.99 shipping
Used: Good | Details
Sold by -Daily Deals-
Condition: Used: Good
Comment: This Book is in Good Condition. Used Copy With Light Amount of Wear. 100% Guaranteed.
Sell yours for a Gift Card
We'll buy it for $8.72
Learn More
Sell It Now
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

The Art of Readable Code (Theory in Practice) Paperback – November 23, 2011

See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
"Please retry"
Rent from
"Please retry"
$19.05 $24.19

Frequently Bought Together

The Art of Readable Code (Theory in Practice) + Clean Code: A Handbook of Agile Software Craftsmanship + Code Complete: A Practical Handbook of Software Construction, Second Edition
Price for all three: $97.50

Buy the selected items together
Shop the new
New! Introducing the, a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Series: Theory in Practice
  • Paperback: 206 pages
  • Publisher: O'Reilly Media; 1 edition (November 23, 2011)
  • Language: English
  • ISBN-10: 0596802293
  • ISBN-13: 978-0596802295
  • Product Dimensions: 7 x 0.4 x 9.2 inches
  • Shipping Weight: 12 ounces (View shipping rates and policies)
  • Average Customer Review: 4.6 out of 5 stars  See all reviews (17 customer reviews)
  • Amazon Best Sellers Rank: #620,271 in Books (See Top 100 in Books)

Editorial Reviews

Book Description

Simple and Practical Techniques for Writing Better Code

About the Author

Although raised in the circus, Dustin Boswell realized early on that he was better at computers than at acrobatics. Dustin received his B.S. from Caltech, where he got hooked on Computer Science, and then went to UC San Diego for his Master's Degree. He worked at Google for five years, on a variety of projects including web crawling infrastructure. Dustin is now an internet startup junkie who spends his free time hiking the Santa Monica mountains and being a new dad.

Trevor Foucher has been shipping software projects for over 10 years, including Windows 2000 and OneCare at Microsoft, and Webmaster Tools at Google. He's been an individual contributor, manager, and tech lead. His goal is to make code more readable and reliable.

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

4.6 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 17 customer reviews
The book has a good mix of examples and commentaries without waisting too much time with unnecessary theory.
Following the type of organization and common sense set forth by the authors in, say, a 600-part parametric CAD model, will also do wonders to productivity.
It is straight to the point, has a lot of funny and relevant cartoons, and packs great pieces of advice on how to write readable code.
Rodrigo De Castro

Most Helpful Customer Reviews

37 of 43 people found the following review helpful By W. Doran on December 12, 2011
Format: Paperback
Good coding practices/style is well worked territory. There are many book and web pages devoted to the subject. This book walks through well treaded territory: variable names, loop structures, code block organization, subroutine structures, etc. For an experienced programmer, there is nothing new in The Art of Readable Code. This is especially unfortunate because they start off with a measurable metric for readable code: how long does it take a programmer previously unfamiliar with the code to understand it. This seemed like a great idea and got me to buy the book. However once you get into the text, when comparing code snippet A with snippet B, instead of showing the two versions to a group of programmers and timing them, they give their opinion about which version would take less time to understand by some mythical programmer looking at the code for the first time. Now, I don't really disagree their opinions any of the topics in the book (ok, I like the ternary operator more than they do), but it is just opinion. I would love for someone to take the examples in this book and do the experiments. This would be hard, and maybe expensive, but the authors and I would surely learn something. That would be great book to read.
2 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
5 of 5 people found the following review helpful By N. Krumpe TOP 1000 REVIEWERVINE VOICE on December 14, 2011
Format: Kindle Edition Verified Purchase
I teach an introductory Java programming course. I spend a lot of time (my students might say that I spend too much time) reminding them that well placed comments, meaningful variable names, indentation, judicious use of blank lines, and so on all lead to code that is easier for them and for other programmers to read and understand. But, when these words come from me, I'm afraid that it comes across as "just another requirement to follow".

Along comes "The Art of Readable Code". The authors have written a very enjoyable, highly readable book about readability. They go beyond simply stating a set of guidelines, instead explaining the motivation behind each suggestion. I love that they show both good and bad from-the-field examples of how programmers write code. I found myself nodding in agreement with much of what they said. I also think they do a much better job than I when it comes to explaining that readable code is not simply a set of requirements to follow, but that there are simple compelling reasons behind readability, not the least of which is to make life easier for others who will read your code.

I have decided that I will begin making this a required reference for my students. Our school subscribes to Safari Online Books, which gives our students free access to O'Reilly books such as this one. Even if my students couldn't get it for free, I think it's a book I would want our computer science/software engineering majors to have handy as a reference. I bought the Kindle edition for myself, and found that it is very readable on the Kindle Fire...and much more relaxing to read this way than from the Safari site (and currently only about half the cost of buying the physical book).

From now on, I will let this book deliver the message to my students about readable code.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 4 people found the following review helpful By Robert H. Stine Jr. on December 31, 2011
Format: Kindle Edition
Insightful and practical coding advice from Dustin Boswell and Trevor Foucher. For years I've been saying that good code easy to understand. Obviously readable code is easier to maintain; the authors point out that it is also easier to test, easier to modify, and easier to reuse. My only quibble is their disparagement of the tertiary operator, which I think can improve code clarity, but without doubt this is an outstanding book on programming.

Other reviewers have described this book as introductory, offering nothing new. Well, the book is not rocket science, but it makes a great case for practices that should be followed but usually aren't. I'm a programmer; I've worked at many software start-ups, and what I see all too often is brittle code, gazillion-line methods, god classes, and pointless tight coupling.

Also, the authors introduce a notion of an economy or budget of mental effort: if what should be simple to understand is a chore, then it is going to be easy to miss problems in the tough stuff. Across the board, the authors articulate compelling cases for doing things the right way, which could be handy for discussions with your colleagues and boss.

Finally, the concrete coding example at the book's end should be educational for even experienced programmers.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 4 people found the following review helpful By Matthew B. Doar on December 21, 2011
Format: Paperback
The more code I write, the more care I take to make it readable for my future self. So I've thought about this subject for a while now. The authors of this book have managed to capture all of my thoughts, and a bunch more.

It's well-planned, written and edited. Not too long (184 pages) and the cartoons don't get in the way, and even occasionally add value. I admired the way that the authors recognized a few classic flame-war subjects, made their opinions known and then moved right along. I think the examples for each idea are all good ones.

I recommend reading it with a body of code in mind, so you can think about live examples of all the issues that the authors raise.

Disclaimer: I requested a copy of this book from O'Reilly so I could review it.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews

What Other Items Do Customers Buy After Viewing This Item?