- Series: Theory in Practice
- Paperback: 206 pages
- Publisher: O'Reilly Media; 1 edition (November 26, 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 (21 customer reviews)
- Amazon Best Sellers Rank: #96,066 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ Free Shipping
+ $3.99 shipping
+ $3.99 shipping
The Art of Readable Code: Simple and Practical Techniques for Writing Better Code (Theory in Practice) Paperback – November 23, 2011
|New from||Used from|
Frequently bought together
Customers who bought this item also bought
About the Author
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.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
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.
As an engineer I find that many of the tips are applicable outside of programming, too. 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.
I don't think this book will ring any bells for someone just starting out. If only we had the foresight, right? But anyone who is "self taught" should go through this; they'll surely find tips to avoid problems they've previously created for themselves.
Every scientist should read this book. They tend to write the worst imaginable code. They "just want it to work" and they test this and that and leave code with patches like "if(1 == 1)" and variable names like "flag". Then when things "get serious" you have to pay thousands to get someone to not only rewrite the code, but also re-interpret the functionality.
Most recent customer reviews
I agree with almost all the suggestions, and had
implemented many of them myself years ago.Read more
Amazon - Please do not require comments if none are necessary.