With this book, you get 97 short and extremely useful programming tips from some of the most experienced and respected practitioners in the industry, including Uncle Bob Martin, Scott Meyers, Dan North, Linda Rising, Udi Dahan, Neal Ford, and many more. They encourage you to stretch yourself by learning new languages, looking at problems in new ways, following specific practices, taking responsibility for your work, and becoming as good at the entire craft of programming as you possibly can.
This wealth of practical knowledge contains principles that apply to projects of all types. You can read the book end to end, or easily browse through to find topics of particular interest. 97 Things Every Programmer Should Know is a useful reference and a source of inspiration.
Tap into the knowledge of expert programmers who have earned stellar reputations
Learn the basic wisdom every programmer needs, regardless of the language you use
Take advantage of the online presence that has evolved from this book project
Review By: Scott Brookhart 09/17/2010This book is a collection of ninety-seven, two-page-long bits of advice from active programmers and developers. Each unique viewpoint provides sound practices that can be used in day-to-day programming and developing activities. Though not organized this way, these short tips are categorized into nineteen different categories. These tips are not language-dependent or dedicated to a particular programming type, rather the advice is general and comes across as common sense. However common these tips may be, the book is worth reading and keeping handy to reference when needing an approach and philosophy to programming and developing.
Programmers usually must be competent with one or more computer languages (usually more); understand the general approach to getting work done in an organized way following processes; able to speak with customers about the software in development; keep up with the latest technologies; make sure that the computer application meets all of the requirements of accessibility, usability, scalability, and reliability; and still make time for family. Real-life programmers keeping up with the tasks listed above are the ones who've written these tips in order to help fellow programmers. That is the main reason you should add this book to your library, if nothing else, to hear what has helped others in our trade become better at what they do. We all want to be better at our job. Sometimes it requires taking a step back from the deep dive into code to think about what we're trying to accomplish and how we can do things more efficiently or take a more sensible approach.
I recommend this book to coworkers. I also would hope that as a result of reading this, my coworker would take a step back and consider his trade and his approach to delivering a sound product.