The Art of Readable Code and over one million other books are available for Amazon Kindle. Learn more

Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
More Buying Choices
Have one to sell? Sell yours here
Start reading The Art of Readable Code on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

The Art of Readable Code [Paperback]

Dustin Boswell , Trevor Foucher

List Price: CDN$ 36.99
Price: CDN$ 30.94 & this item ships for FREE with Super Saver Shipping. Details
You Save: CDN$ 6.05 (16%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 1 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
Want it delivered Thursday, June 20? Choose One-Day Shipping at checkout.

Formats

Amazon Price New from Used from
Kindle Edition CDN $15.69  
Paperback CDN $30.94  

Book Description

Nov 23 2011

As programmers, we’ve all seen source code that’s so ugly and buggy it makes our brain ache. Over the past five years, authors Dustin Boswell and Trevor Foucher have analyzed hundreds of examples of "bad code" (much of it their own) to determine why they’re bad and how they could be improved. Their conclusion? You need to write code that minimizes the time it would take someone else to understand it—even if that someone else is you.

This book focuses on basic principles and practical techniques you can apply every time you write code. Using easy-to-digest code examples from different languages, each chapter dives into a different aspect of coding, and demonstrates how you can make your code easy to understand.

  • Simplify naming, commenting, and formatting with tips that apply to every line of code
  • Refine your program’s loops, logic, and variables to reduce complexity and confusion
  • Attack problems at the function level, such as reorganizing blocks of code to do one task at a time
  • Write effective test code that is thorough and concise—as well as readable

"Being aware of how the code you create affects those who look at it later is an important part of developing software. The authors did a great job in taking you through the different aspects of this challenge, explaining the details with instructive examples."
—Michael Hunger, passionate Software Developer


Customers Who Bought This Item Also Bought


Product Details


Product Description

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.


Customer Reviews

There are no customer reviews yet on Amazon.ca
5 star
4 star
3 star
2 star
1 star
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 4.5 out of 5 stars  13 reviews
27 of 33 people found the following review helpful
3.0 out of 5 stars Nothing New Dec 12 2011
By W. Doran - Published on Amazon.com
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.
5 of 5 people found the following review helpful
5.0 out of 5 stars Great advice for all programmers Dec 14 2011
By N. Krumpe - Published on Amazon.com
Format:Kindle Edition|Amazon 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.
4 of 4 people found the following review helpful
5.0 out of 5 stars Worth reading, great for lunch-time discussions Dec 21 2011
By Matthew B. Doar - Published on Amazon.com
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.

Listmania!

Create a Listmania! list

Look for similar items by category


Feedback


Amazon.ca Privacy Statement Amazon.ca Shipping Information Amazon.ca Returns & Exchanges