- Paperback: 258 pages
- Publisher: O'Reilly Media; 1 edition (February 22, 2010)
- Language: English
- ISBN-10: 0596809484
- ISBN-13: 978-0596809485
- Product Dimensions: 6 x 0.5 x 9 inches
- Shipping Weight: 10.6 ounces (View shipping rates and policies)
- Average Customer Review: 3.8 out of 5 stars See all reviews (44 customer reviews)
- Amazon Best Sellers Rank: #697,196 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.
97 Things Every Programmer Should Know: Collective Wisdom from the Experts 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
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
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
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.
This book lists collected essays from experienced programmers. The essays are short and only two pages long. They are easy to read and follow, but they are sorted in alphabetical order by their titles. Hence, the back-to-back essays are not necessarily content related, and you can just read any one of them as you please. For those who prefer to read related things in certain order, there is a section in the beginning of the book that lists essays with associated page numbers in predefined categories like: Bug and Fixes; Build and Deployment; Code Guidelines and Code Layout; Error Handling; and etc. Overall, it has an easy layout.
There is now a Kindle Edition of this book that was not available when I purchased it a few months ago. If you own an Amazon Kindle, or an iPad or any other E-Book reader, you may find e-book to be a better choice. Since the essays are short, you can read small portions easier on the e-book when you are on your breaks or on the road.
If you are in your golden age of programming, you may not find this book very useful. However, if you are just started and hungry for more, you will find enough satisfying information that makes this book worth having. Either way, hope this mini review help you further in your decision.
While some of the things here were a bit obvious, reading this book was a great learning, and I would honestly suggest it for any developer, tester, or project manager. Even product developers and producers could benefit greatly from its reading.
I agree with everything there
Many right thoughts/experience in single book