3 ms·
Huge, huge amounts of kudos to you to ask here about this. My advice to a librarian buying programming books: just stop! There is a deluge of crap that is sim
by kazinator 4y ago
Huge, huge amounts of kudos to you to ask here about this.
My advice to a librarian buying programming books: just stop!
There is a deluge of crap that is simply full of wrong information. So even when the topic is still fresh and relevant, those books are still wrong. An expert in the area could have a spot-the-error field day with most of it.
To be able to know what the nuggets of gold are in all the dirt, you'd have to have a background in it, or have access to a consultant who does. I would say, multiple consultants due to the amount of stuff that is out there. You can easily find heavily experienced developers who have no clue at all about a vast amount of stuff that they don't work with.
The valuable books that will stand the tests of time might not even be of interest to the public library audience; they may be more at home in a university library.
Basically, the public library is not a good venue for conveying up-to-date programming information that focuses on doing specific tasks with specific versions of tools on specific platforms. It's not a good use of the library's budget, staff time and space to be on that treadmill at all. Making effectively purchases in this area (skimming the cream of what's out there) requires knowledge that librarians typically don't have, and even if you manage to pick out the momentarily good stuff, a lot of it will have to be prematurely discarded to make space for new material.
- solarmist 4y agoCan’t that be said almost verbatim about any academic field?
- kazinator 4y agoIt can't even be said about the academic side of computing. Programming books aren't academics; they are about the entirely arbitrary and ever-changing conventions of some stuff that is made up of pure information, which someone pulled out of thin air. An actual computer science text from 1990 can be very useful; so could a book about electronics from 1990, or mechanical engineering. A programmming book from 1990 is like the repair manual or schematics for some appliance from 1990. Except in the case of the appliance from 1990, at least it was similar to many others: a repair manual for another make and model could actually be useful. We have to imagine a world in which two refrigerators have absolutely nothing in common; the parts look completely different, are hooked up differently and have different names.
- solarmist 4y agoI just mean there’s tons of shit books published in every field. Computers probably have 10x more, but it’s not a new phenomenon. Look at medical books that make it into libraries. Same for psychology or any social science. Tons of history books fall into editorializing so similar can be said of them. And for technical books, (woodworking, drawing, knitting, sewing, etc) they tend to fall into cycles of fads with books that are basically clones of each other.