97 Things Every Programmer Should Know: Collective Wisdom from the Experts

Kevlin Henney’s edited collection, "97 Things Every Programmer Should Know," is exactly what it says on the tin — a curated set of brief essays by a diverse roster of seasoned programmers. The book isn’t about flashy new frameworks or bleeding-edge tech. Instead, it’s a practical, sometimes blunt, reminder of the fundamentals that keep code usable, teams sane, and projects moving forward.

Each essay is short, usually a page or two, making it a perfect quick read rather than a deep dive. But don’t mistake brevity for fluff. These are distilled insights from folks who’ve been there, done that, and want you to avoid the same pitfalls. The advice spans everything from crafting clean code to mastering your tools, from debugging to collaborating with humans (yes, humans!).

One of the biggest takeaways is the emphasis on simplicity and maintainability. Writing code that just works isn’t enough; it needs to be readable and adaptable. The book pushes back against overengineering and complexity, which is refreshing in a world obsessed with shiny new patterns. It’s a call to write code future-you won’t hate.

Testing and debugging get their fair share of attention. The contributors advocate for rigorous testing habits and smart debugging strategies — not as optional extras but as core parts of the craft. It’s a reminder that bugs aren’t a sign of failure but an opportunity to learn and improve.

Professionalism and teamwork also feature heavily. Several essays highlight the importance of continuous learning, code reviews, and open communication. Programming isn’t just about typing code; it’s about working with people and evolving your skills. The book doesn’t sugarcoat this — it acknowledges that collaboration can be messy but insists it’s essential.

Another practical angle is tool mastery. Knowing your IDE, version control, and debugging tools isn’t just for show; it’s about squeezing out every bit of productivity and avoiding unnecessary headaches.

That said, the book’s format is both its strength and its weakness. The short essays mean you get a wide variety of perspectives, but none go very deep. Some advice may feel like common sense or rehashed wisdom. If you’re already a seasoned developer, parts of it might seem like preaching to the choir. Also, the alphabetical organization is a bit random, so it’s not a book you read cover to cover but more a reference or a source of quick inspiration.

Despite being over a decade old, the core ideas hold up well because they focus on timeless principles rather than trendy tech. The human side of programming, the push for clarity, and the professional habits are as relevant now as ever. If anything, the book is a good antidote to the hype cycle that constantly bombards developers with the next big thing.

In short, "97 Things Every Programmer Should Know" is a practical, no-frills collection that reminds you what really matters when you sit down to write code. It’s less about reinventing the wheel and more about making sure your wheel doesn’t fall off mid-ride.