Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Books Programming

The Most Mentioned Books On StackOverflow (dev-books.com) 92

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.
This discussion has been archived. No new comments can be posted.

The Most Mentioned Books On StackOverflow

Comments Filter:
  • by Anonymous Coward on Wednesday February 08, 2017 @11:40AM (#53825925)

    A best seller!

  • by Snotnose ( 212196 ) on Wednesday February 08, 2017 @11:44AM (#53825953)
    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.
    • by Anonymous Coward

      Grandpa, I can't come to the home today. Got stuff to do.

      Also, I'm telling mom you're on Slashdot, you know you're not allowed on Slashdot. You're in big trouble!

    • by creimer ( 824291 ) on Wednesday February 08, 2017 @11:59AM (#53826113) Homepage

      I'm C, C++, embedded code, device drivers.

      I've always wondered what the offspring of a Linux kernel and BSD kernel would look like.

    • by lgw ( 121541 )

      I've been amazed how many "design patterns" are really just "here's how to cope with this weakness in C++ patterns", that apply to no other language.

      Anyone have enough experience with C++14 to comment on whether the 11/14 modernization attempts have addressed most of these patterns? Or was the committee off in the weeds?

  • Knuth? (Score:4, Interesting)

    by arth1 ( 260657 ) on Wednesday February 08, 2017 @12:01PM (#53826133) Homepage Journal

    No love for TAoCP?

    • It makes the list with "Math" and "math/CS" tags.
  • by creimer ( 824291 ) on Wednesday February 08, 2017 @12:07PM (#53826189) Homepage
    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.
  • by Anonymous Coward

    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.

    • by Tablizer ( 95088 )

      came out before the internet was even a thing

      In theory the "WebTubes" shouldn't influence our programming languages and techniques much, but for some reason it did. The way state is typically managed and kept (or not kept) in web apps, however, did end up influencing the languages, along with the emphasis on string handling for marshaling of info and variables to and from HTTP and HTML. In a mature environment, API's and session-friendly thread handling would hide or simplify most of such nitty gritty.

      Perha

    • The web wasn't a thing in 93. The Internet was definitely a thing,

      simtel. wuarchive. sumex-aim. sunsite. All the big ftp sites, and searches were Archie. That and netnews. alt.barney.dinosaur.die.die.die

      • by plover ( 150551 )

        All the big ftp sites, and searches were Archie.

        Gopher, you heathen. Now go jump in a volcano.

        • I dabbled in gopher, but did a lot more in ftpsace and netnews than gopher. It grew and died in a very short timespan. I started my first professional webserver 93 or 94 or so, the EMWAC webserver on a DEC Alpha running WinNT 4.0

          I did install and run an oddball Mac gopher client that for some reason used 3d rendering for pages and gopher daemons. Was cool, i played for like an hour, and then never ran it again.

      • by zaft ( 597194 )

        That and netnews.alt.wesley.crusher.die.die.die

        FTFY

    • by creimer ( 824291 )

      Back then you could buy the Internet Yellow Pages at the bookstore to find everything on the Internet.

      https://www.amazon.com/Internet-Yellow-Pages-3rd/dp/0078821827/ [amazon.com]

  • Blowing smoke? (Score:4, Interesting)

    by Tablizer ( 95088 ) on Wednesday February 08, 2017 @12:14PM (#53826277) Journal

    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.

    • by plover ( 150551 )

      The value I got from Design Patterns is that these were describing the solutions to actual problems I had already had to solve on my own (often not as well), and they covered the side effects of those solutions, some of which I hadn't thought too much about before reading the book. (The observer pattern creates hidden long-term maintenance dependencies on the semantics of the data published by the subject, for example. That was really useful to me when I hadn't yet recognized the problem.)

      However, once it

  • by Anonymous Coward

    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

  • by Anonymous Coward

    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.

    • by CByrd17 ( 987455 )

      It did make it, just not into the top 10.

      It's number 11.

    • This is the one paper book that I still keep at-hand for programming. There is no substitute, it is the best. Simple and clear.

      It's too bad that C++ is so flexible that such a straight-forward book cannot ever be written for C++.

  • by Anonymous Coward

    I figured most tech geeks would be referencing a book such as, "How to meet women", much more regularly than programming literature.

  • by cant_get_a_good_nick ( 172131 ) on Wednesday February 08, 2017 @01:04PM (#53826775)

    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". [salon.com] Yes, you were cool. RIP....

  • by SuperKendall ( 25149 ) on Wednesday February 08, 2017 @01:20PM (#53826953)

    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++ [amazon.com]. 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 [github.com] 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...

  • 50 Shades of Gray Code.
  • 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.
  • by Anonymous Coward

    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.

  • 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.

    • Like Knuth, this has fallen off my list of must-reads. There's a lot of it that's only relevant to 1960-era software development, some stuff that's wrong (the part on information hiding, for example), and some stuff that's common knowledge. If someone is going to read it anyway, they should get the Silver Anniversary edition, which has corrections and some good new insights.

"We don't care. We don't have to. We're the Phone Company."

Working...