• List Price: CDN$ 38.89
  • You Save: CDN$ 9.26 (24%)
Only 1 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
97 Things Every Programme... has been added to your Cart
+ CDN$ 6.49 shipping
Used: Very Good | Details
Sold by wobcanada
Condition: Used: Very Good
Comment: The book has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.
Have one to sell?
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

97 Things Every Programmer Should Know: Collective Wisdom from the Experts Paperback – Feb 22 2010

4.0 out of 5 stars 4 customer reviews

See all 3 formats and editions Hide other formats and editions
Amazon Price
New from Used from
Kindle Edition
"Please retry"
"Please retry"
CDN$ 29.63
CDN$ 18.26 CDN$ 12.76

Harry Potter Book Boutique
click to open popover

Frequently Bought Together

  • 97 Things Every Programmer Should Know: Collective Wisdom from the Experts
  • +
  • 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts
Total price: CDN$ 62.97
Buy the selected items together

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Product Details

  • Paperback: 258 pages
  • Publisher: O'Reilly Media; 1 edition (Feb. 22 2010)
  • Language: English
  • ISBN-10: 0596809484
  • ISBN-13: 978-0596809485
  • Product Dimensions: 15.2 x 1.4 x 22.9 cm
  • Shipping Weight: 299 g
  • Average Customer Review: 4.0 out of 5 stars 4 customer reviews
  • Amazon Bestsellers Rank: #327,426 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description

About the Author

Kevlin Henney is an independent consultant and trainer. His work focuses on patterns and architecture, programming techniques and languages, and development process and practice. He has been a columnist for various magazines and online publications, including The Register, Better Software, Java Report, CUJ, and C++ Report. Kevlin is co-author of two volumes in the Pattern-Oriented Software Architecture series: A Pattern Language for Distributed Computing and On Patterns and Pattern Languages. He also contributed to 97 Things Every Software Architect Should Know

Customer Reviews

4.0 out of 5 stars
Share your thoughts with other customers

Top Customer Reviews

Format: Paperback
What I have liked from the very beginning of the book, was the way the content description was organized. There are two tables of content ' first one, regular one, second one divides book into different categories, thus you can read just essays related to particular topic. Another great advantage of the book is the way essays were prepared ' two pages per each of them. No wasted space, no elaborates, just the core of the problem that is discussed. The same thing refers to the index ' I like books where you can find things within index easily and accurately.

Technical part of the book is the one side of he coin, second one is the content. 97 Things' is a book that covers topics you can find in many other books (Pragmatic Programmer, Agile Developer, Developers Notebook, Productive Programmer). What distinguish this book is the way topics are presented. Authors do not go deeply into details, they just sketch the issue, provide readers with the starting point and don't give them 'silver bullet'. Many times you will fell like ' 'hey, I knew that already' ' but that's OK, because you started to think about the again. I liked the book, I liked the topics, however different style of each essay might be confusing a little bit. If you like consistent style over the whole book, this will be a drawback. Another thing is ' if you have read books like Pragmatic Programmer or Practices of an Agile Developer, rethink buying this book. You might feel disappointed. If you haven't read them ' it might be a good starting point for getting a better programmer.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback Verified Purchase
Good guide or instructions for someone who is entering into the programming world. It would nice to provide scenarios with code examples.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback Verified Purchase
Excellent book with good points for the novice and the expert. Its simple to focus on but has some powerful parts to it.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Paperback
Well written and contains many short but very good tips.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: HASH(0xa0eaf8a0) out of 5 stars 41 reviews
35 of 35 people found the following review helpful
HASH(0xa1167984) out of 5 stars Great bathroom or bus commute reading for programming beginners March 22 2010
By M. Helmke - Published on Amazon.com
Format: Paperback
I have read programming books for years. There was a time when I could write a "Hello World" program in each of seven or eight languages. That time has passed, mainly because I haven't been intimately involved in any specific software project for many years. Still, I have this habit of reading programming books and enjoying them, perhaps in the hope or expectation that one of these days I'll find myself with a project in front of me, time to work on it, and motivation to learn a new language or tool to make the project's vision a reality. Well, here's the newest book of programming foundational tips that I have read.

97 Things Every Programmer Should Know is a collection of short, two page essays, each by an experienced programmer. The book is a collection of tips and tricks for writing code that works, that is maintainable both by the author and by others, and that will best fit the situation. While the book doesn't measure up to some of my all time favorites in the genre like The Art of Unix Programming or The Pragmatic Programmer, it wasn't meant to. This is not an in depth guide to underlying philosophies of coding practices and standards, but quick hit and run articles that would be easy to fully grasp and absorb in short five minute bursts, such as during work or study breaks (which is how I read the book).

Some of the topics included in this book will seem obvious such as "Don't Ignore That Error" and "Comment Only What The Code Cannot Say," and some tips are going to serve only as reminders to best practices that are sometimes ignored (to our own peril) like "Check Your Code First Before Looking To Blame Others" and "Make Interfaces Easy To Use Correctly And Difficult To Use Incorrectly," there are some real gems in the book that aren't so obvious like one author's instruction to "Read the Humanities" because they are a great tool to help programmers learn to effectively interact with people and not just software and the advice that says "Don't Just Learn the Language, Understand Its Culture" so that you will write effectively and idiomatically within each language, rather than writing the same thing using different words.

I can't say that this is a must-have book for experienced programmers, but anyone at the novice to intermediate levels would certainly benefit from what the book contains. I've enjoyed reading it.
60 of 67 people found the following review helpful
HASH(0xa1194bf4) out of 5 stars Abstract and aphoristic Feb. 21 2010
By Trevor Burnham - Published on Amazon.com
Format: Paperback
If you're just entering the programming world, this collection of 2-page essays might be a useful resource. But if you've been reading programmer blogs for a while, or you've worked on a couple of projects, then there's little of value here. Very few of the essayists choose to tell stories; instead, they say things like "Remember that humans always make mistakes," "Read other people's code" and "Always leave the campground cleaner than you found it."

Speaking of which, where is the code? A book on programming without code is like a day without sunshine! To give one example: The second essay, "Apply Functional Programming Principles" by Edward Garson, assures you that you'll write cleaner, clearer code after working with a functional programming language, but his assurances feel awfully airy without any examples. Maybe this is inevitable in a book that's language-agnostic. Books like Code Complete and Clean Code are hopping with code samples (in C++ and Java, respectively); as a result, they do a far better job of engaging the reader and making abstract concepts stick.

A notable exception is "Code in the Language of the Domain" by Dan North, which uses code to illustrate a concept and uses it well. You might want to read that one, but you don't need to buy the book to do so: All of the essays in this book are Creative Commons-licensed and can be read on the book's official website.

Here is why Joel Spolsky's books are so good: He tells stories. He gives examples. He restrains himself from bombarding the reader with familiar aphorisms. You're imbibing his experiences, not just listening to him ramble. If you haven't already read Joel on Software and More Joel on Software, definitely do so. Also check out the deep interview collection Coders at Work. It's the 98th thing every programmer should know.
4 of 4 people found the following review helpful
HASH(0xa10a7cfc) out of 5 stars A Starting Point For Your Conversations March 17 2010
By Michael T. Fisher - Published on Amazon.com
Format: Paperback Verified Purchase
This book is a compilation of short essays ranging on topics as diverse as Bugs, Error Handling, Customers, Refactoring, and Expertise. The purpose of the short essay is not to answer all your questions or be a definitive guide to programming. Rather the purpose is to provide a starting point for a conversation. To this end, I think a practical way to use this book whether in academia or a development team would be to assign groups of essays to be read ahead of time to stimulate classroom or team meeting discussions. Read my full review of the book here,
2 of 2 people found the following review helpful
HASH(0xa10a7ce4) out of 5 stars Some Beneficial Advice and Maxims Oct. 8 2013
By Noah Moerbeek - Published on Amazon.com
Format: Paperback Verified Purchase
97 things every programmer should know is a light easy read that is broad enough to appeal to anyone who works in code or on software projects in general.

I found essays like "How to Implement Doing it Right vs Getting it Done" to be very helpful and wise. That essay included pratical advice that we were able to apply by changing our design for our in house bug tracking software to include a technical debt tracker. "Coding with Reason" included some decent maxims that I hope my programmers implement, and I will be checking for in future code reviews. It is for these excellent essays among others that the book is worth reading.

As a software development manager who also gets involved in the business side of things I was amused at how occasionally at the contradiction that exist between the business world and the software development world. In the essay "The Professional Programmer" that emphasized among other things that programmers should not tolerate bug lists and take responsibility for training themselves (I agree). However, I know that often times programmers have little control over their time and I know that our fallen nature inclines people who self study (if they do it all) often times to study what they like rather than what is useful to the company. In my knowledge of Business management the opposite advice is given, that in order to keep a motivated workforce the employer needs to provide training and/or training opportunities. Essays pushing pair programming made a good argument for it, but excluded what practical ideas can be implemented if such a thing is not possible.

Sometimes I did not always agree with all the essays nor did I think that certain maxims should be elevated to the level of dogmas. Where the book suffered was that some of the essays selected seemed to reiterate points that where already made in other essays.

I would recommend this book and I will even be using it for our in house book club.
2 of 2 people found the following review helpful
HASH(0xa20960c0) out of 5 stars Better than the other 97 things books Nov. 17 2011
By David - Published on Amazon.com
Format: Paperback
Just like all of this series, these are free articles that can be found online, so if you what the hard copy, I recommend buying it used. The steep price is most likely just the publisher taking a huge cut, and I'd much rather pay the people who wrote it.

What do you get when you get 97 tidbits of hard-learned experience? Some great insight to learn from other's experiences.

This is a good casual read that can be done in two hours. Since all the articles are short, it can be read in quick phases. It also can spark your interest in certain topics to go find full books on it.