I train programmers, and strongly recommend they buy books or do other types of money/time investment to make themselves better (and more highly-paid programmers).
They won't do it.
I've had multiple programmers literally shocked and avoid my outstretched book. Once I got a question, said "I just read the answer to this in this book right here"... and the programmer refused to read the book to answer his question.
I don't get it.
This, coupled with companies lack of investment in their expensive engineers, is mystifying.
None of the above has anything to do with the FSF.
Maybe books are too low density. Like the “quantity of information” per amount of words is lower than a blog post for example.
I dunno, I’m not really a reading type but I do own programming-related books. It’s the only type of book I own. I learned a lot from books like The Clean Coder, The Pragmatic Programmer and some 90’s book about Design Patterns with c++ examples and I don’t even write c++
If anything, a good book (or video course) will be a high-density, concentrated pill of everything you need to know about the subject to know what everything is and how it interacts. By comparison, reading blog posts and random YouTube videos is more akin to "grazing" - sure you can learn, but not as fast and you'll be missing context until the lightbulb goes off.
Good programming books are some of the highest information density of any writing you can find. College professors tend to prefer the lower density versions which might be biasing people.
The recommendations I got from lecturers at university were thick academic textbooks. The 'good programming books' popular on HN etc. - without taking anything away from them - tend to be more waffley blog-turned-book type things.
Aside from classics from the former category that are also popular in the latter. Sipser, the dragon book, Spivak, etc.
This comes to personal preferences, I generally prefer reference books vs educational books. Find a good fit between what you’re working on and what the book is trying to do and they can be extremely helpful
Best example that comes to mind is the first edition of SQl in a nutshell. It was thin reference that covered SQL and the major differences between different SQL databases that I picked up back in 2002 ish. Quite useful if your working with several at the same time, but not something to teach you SQL. I haven’t looked at a recent edition because I am not in that situation any more, but I presume it’s still useful for that purpose.
Granted most books are significantly more verbose, but the physical limitations of books can promote extremely precise writing with minimal extraneous information.
It's my experience that this is often the case. I don't like high-theory books, so that means that things like the dragon book aren't likely to be in my sample.
They won't do it.
I've had multiple programmers literally shocked and avoid my outstretched book. Once I got a question, said "I just read the answer to this in this book right here"... and the programmer refused to read the book to answer his question.
I don't get it.
This, coupled with companies lack of investment in their expensive engineers, is mystifying.
None of the above has anything to do with the FSF.