97 Things Every Programmer Should Know
by Kevlin Henney · first published 2010
43% recommend57% neutral
Why HN recommends it
Short, varied essays by many experienced practitioners cover topics like bugs, error handling and design. Its pragmatic, bite-sized ideas suit programmers at any level.
Summarised by Claude from recommending comments
Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice. With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2009–2025C# in Depth
Jon Skeet
Recommended by 29 · mentioned by 3929 recommend · 39 mention29 recommend · 3929 recommend
2008–2025Head First design patterns
Eric Freeman, Elisabeth Freeman, Kathy Sierra, Bert Bates
Recommended by 65 · mentioned by 10065 recommend · 100 mention65 recommend · 10065 recommend
2007–2026On Writing Well
William Zinsser
Recommended by 137 · mentioned by 170137 recommend · 170 mention137 recommend · 170137 recommend
2007–2026The Elements of Style
William Strunk, Jr., E. B. White
Recommended by 131 · mentioned by 231131 recommend · 231 mention131 recommend · 231131 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
2007–2026The Pragmatic Programmer
Andy Hunt, Dave Thomas
Recommended by 353 · mentioned by 589353 recommend · 589 mention353 recommend · 589353 recommend
2008–2026Clean Code
Robert C. Martin
Recommended by 298 · mentioned by 739298 recommend · 739 mention298 recommend · 739298 recommend
2007–2026Introduction to Algorithms
Thomas H. Cormen, Charles E. Leiserson, Ronald L. Rivest, Clifford Stein
Recommended by 274 · mentioned by 712274 recommend · 712 mention274 recommend · 712274 recommend
Fortunately, there's a book: 97 Things Every Programmer Should Know https://books.google.com/books/about/97_Things_Every_Program... http://www.worldcat.org/title/97-things-every-programmer-sho...
on “Latency numbers every programmer should know (2012)” ↗97 Things Every Programmer Should Know (ed. Kevlin Henney) is sort of nice reading. All pretty smart ideas so far, imho. Though I haven't finished reading it. (Like a lot of O'Reilly books these days, it's available in a free (legal) form…
on “O'Reilly is selling any eBook for $9.99 today” ↗> 97 Things Every Programmer Should Know > Any programmer wishing to be a great programmer should read this! https://www.amazon.com/Things-Every-Programmer-Should-Know/d... This book is an assemblage of short papers running on themes as different…
on “Ask HN: Which everyday skill is important to master as a software developer?” ↗…the following one (it's on my shelf) : - The Art of Computer Programming, Volumes 1-4, by Donald E. Knuth Some books are more generals and provide insightfull tips that I found quite helpfull : - 97 things every programmer should know, by a lots of people - The pragmatics programmer, by Andy Hunt and Dave Thomas - Clean code, by Robert C. Martin If you want improve you skill about a particular programm language, the best is…
on “Which books, courses, projects have improved your programming skills immensely?” ↗1) The Art of Unix Programming 2) TCP/IP Illustrated 3) 97 Things Every Programmer Should Know
on “Ask HN: What three books impacted your career the most?” ↗1.) The Pragmatic Programmer 2.) The Passionate Programmer 3.) 97 Things Every Programmer Should Know
on “Ask HN: Programming books that are desk worthy? (reference material)” ↗Christopher Alexander wrote "A City is Not a Tree" in 19651[1]. Software consultant and author of 97 Things Every Programmer Should Know Kevlin Henney has a talk titled "A System is Not a Tree"[2]. Microbiologists have known for a long time that bacteria exchange DNA in multiple ways, and their evolution is not at all neat. It makes…
on “A bird that’s breaking the tree of life” ↗…an "Ask HN" on things programmers should know. There's "things programmers should know" according to HN: https://hn.algolia.com/?query=%22programmers%20should%20know... And as previously mentioned, 97 Things every programmer should know: collective wisdom from the experts, Kevlin Henney, ed., O'Reilly, 2010 http://www.worldcat.org/title/97-things-every-programmer-sho... Most of the latter is practices, with a few technical recommendations:…
on “Latency numbers every programmer should know (2012)” ↗97 Things Every Programmer Should Know by Kevlin Henney: Chapter 71. Read the Humanities https://www.oreilly.com/library/view/97-things-every/9780596...
on “Google's Plan to Disrupt the College Degree Is Absolute Genius” ↗…infrastructure, networking, understanding how things fit together. Virtually everything interests me (perhaps that is a problem?). My reading queue, to give you an idea of my interests: * Beautiful Data * 97 Things Every Programmer Should Know * Learning iPhone Programming * Hello, Android * Programming Clojure * C# in Depth (when it's released) So, HN: Project Suggestions? Has anyone else returned from a sojourn in the wilderness? How…
on “Ask HN: Finding an OSS programming community?” ↗Related to this: https://leanpub.com/97-Things-Every-Programmer-Should-Know-E...
on “Things Every Programmer Should Know” ↗This is a neat trick, the best I've seen for commenting out huge blocks. But yeah, there is no reason for commented out code. From "97 Things Every Programmer Should Know" http://programmer.97things.oreilly.com/wiki/index.php/Commen... > Commented-out code is not executable code, so it has no useful effect for either reader or runtime. It also becomes stale very quickly.…
on “The //* /*/ //*/ comment toggle trick” ↗I'm just going to link to Don't rely on "Magic Happens Here" from the O'Reilly book "97 Things Every Programmer Should Know". http://programmer.97things.oreilly.com/wiki/index.php/Don%27... Then I'm going to ask the programmer/engineer to flip the model around and ask that they look at Operations in the same way they wish…
on “The Myth of the Non-Technical Startup Employee” ↗Interesting. I have on my shelves a copy of O'Reilly Associates' 97 Things Every Programmer Should Know, copyright February 2010, ergo an increase of roughly seven things per year.
on “O'Reilly site lists 165 things every programmer should know” ↗…influenced lots of people and were relevant back then, are relevant now and will be in the next 20 years. It shouldn't be books as I see it but articles, short texts, essays(maybe books of articles, like "97 Things Every Programmer Should Know") What I came up by now is this: "Go To Statement considered harmful" - by E. W. Dijkstra "Can Programming Be Liberated from the von Neumann Style? A Functional Style and Its Algebra of Programs" - by…
on “Ask HN: Major Texts of Our Industry?” ↗