The Most Mentioned Books On StackOverflow (dev-books.com)
An anonymous reader writes: People over at DevBooks have analyzed more than four million questions and answers on StackOverflow to list the top of the most mentioned books. You can check out the list for yourself here, but here are the top 10 books: Working Effectively with Legacy Code by Michael C Feathers; Design Patterns by Ralph Johnson, Erich Gamma, John Vlissides, and Richard Helm; Clean Code by Robert C. Martin; Java concurrency in practice by Brian Goetz, and Tim Peierls; Domain-driven Design by Eric Evans; JavaScript by Douglas Crockford; Patterns of Enterprise Application Architecture by Martin Fowler; Code Complete by Steve McConnell; Refactoring by Martin Fowler, and Kent Beck; Head First Design Patterns by Eric Freeman, Elisabeth Freeman, Kathy Sierra, and Bert Bates.
A best seller!
I'm C, C++, embedded code, device drivers. If you ignore books like the Microsoft build engine (I don't do Windows) I've got probably 90% of those dealing with my problem domain.
Granted, most of these are not the current editions (haven't bought a book in over 10 years now), but I've got em.
No love for TAoCP?
If I'm unfamiliar with a subject, I'll read a Dummies book. Sometimes I'll read an Idiot book. Both are excellent resources for diving into a new subject.
Hard to believe the original came out before the internet was even a thing back in 1993. I still have my copy from 1995 when I was but a teenager in college. Twas money well spent.
I didn't get Design Patterns. It was still unclear on when to use what, and why. Many of the alleged limitations of the alternatives are language-specific. Sure, Java sucks at some things, C++ at others, etc. The real issues in comparing among design choices are subtle and complex.
Table-ized A.I.
Only picks up books with valid amazon.com links. There are many more books mentioned than that, I often recommend books but dont put links, just title and author
Minimal? I have 2 of those books and have been coding in C++ exclusively since 1997. The hell do you need all of them for?
I feel like The C Programming Language book didn't make it because no one refers to it by it's name. It seems like every C question ever results in a reference to that book.
I figured most tech geeks would be referencing a book such as, "How to meet women", much more regularly than programming literature.
The Stevens Networking book is still up on the list, I'm very glad.
I remember a story about him and his kid. They went to go to Wayne's World 2, and in the movie they show his book. His son, "dad you're so cool, that's your book". Yes, you were cool. RIP....
One thing I didn't see on the list but I consider a must-read book for any programmer, is The Design and Evolution of C++. It helps if you've worked with C++ but is not a requirement; the book is really good more because you learn how a programming language comes to be, and the thought that goes into how it works.
If you dislike some parts of C++ you will find fun supporting material here also... but really it's a great way to help you see all programming languages form the other side.
On a side note if you do like this you may want to look sometime into some of the Swift commonly rejected changes document, that gives you insight into a modern programming language as it forms. An amusing aspect is that it used to be called the "Commonly Proposed" document, as you can tell from the URL and file name...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
50 Shades of Gray Code.
They can take my LifeAlert pendant when they pry it from my cold dead fingers.
The hell do you need all of them for?
To broaden your skillset? To be more effective at what you do? To write more maintainable code? To make fewer errors? To interact with your peers? More specific to C++ and those particular books, to prevent race conditions, to have strong error handling, and to make more efficient use of multiple core processors? Perhaps most importantly, so that when the company hires a snot-nosed kid who actually does know and practice these things, that he won't show you up as the fossil you're describing yourself as?
I've been programming since 1976, and I think it's fair to say that computers have changed since then. If you think that programming now is anything like programming 20 years ago, you haven't been paying nearly enough attention.
John
He has been trolling about OO since usenet and Design Patterns since Kent's wiki and I see he still fails to grasp the basics after nearly 20 years and hundreds of people to educate him.
I'm surprised I have some of the top 10 since I have relatively little tech books.
I can totally recommend Head first design patterns. Some chapters are a bit repetitive as they explain the specific pattern too many times but it's got a teaching style that makes you think and so the knowledge acquired stays with you.
Notice how the suggested books are old. That's because nobody bothers writing computer books anymore. The information gets out of date too quickly and nobody wants to pay for tech info when they can get it "free" off the Internet from blogs, etc., even if it takes forever to find and piece together. Nothing can compete against free.
Modern C++ Design bent my brain. I had to read it at least 3 times at first. Then I started using his loki library. It made for incredibly better code when all was said and done.
Anyone not willing to improve their skillset or understanding of their own toolbox will just stagnate.
The list is incomplete without Fred Brooks "The Mythical Man Month".
I still think it's required reading before you're allowed to participate in any aspect of code.