It was truer in the 1980s-1990s, when programming was not a prestigious or high paying job and computers were much cruder and required much more skill to get adequate performance from them. Generally, aspiring hackers were very well read people.
There were, of course, corporate programmers doing business programming back then too but they weren't considered hackers and wouldn't even have wanted themselves to be considered hackers.
As anecdata: My wife has a "brainy" occupation and her brilliant sister does not. Correspondingly, my wife has no interest in "brainy" books in her free time whilst her sister is always recommending new 900 page tomes.
Now even knowing some great books exist, it can be quite difficult to find those works in the goldilocks zone of being worthwhile while accessible enough. So difficult even that the part where you are searching becomes so time consuming that it still ends up missing the mark on stimulation or learning per hour.
And so generally I find programming or working on other intellectual projects more worthwhile than reading, and reading books has kind of drifted into being a low stimulation activity I do when I'm tired or don't have the focus time for projects.
How do you get around that? How do you find and select what is actually worthwhile to read?
In my view, software development is mostly skimming and pattern recognization. Very little actual, deep reeding in my opinion.
You're not actually learning anything then. Memorizing trivia, sure. But not actually learning.
Correction: you love the feeling of consuming information, not learning.
People can learn from watching a documentary just as well as they can learn from reading, but reading teaches you how to interpret language as you continue reading, and other forms of information delivery convey understanding of their own mediums in their own ways. I would not have learned how to quickly spot a terrible documentary over a great one if I had not watched so many in my life. It doesn’t mean I didn’t learn anything because I watched and listened instead of read, it just means that I didn’t read the documentaries.
Pro tip: don’t correct people about their own lives.
Part of disagreement probably stems from what type of 'learning' we're discussing. In my view, at the broadest sense that we can define 'learning', is incorporating information about our surroundings into our internalized world model. The type of learning I see most valuable personally, is the type that expands this horizon the most, or helps us think in frameworks that break down the least in different contexts.
This type of foundational building often requires deep thought, but is also often deeply rewarding if you get it right. This doesn't require reading by itself, but ruminating and neural rewiring can often be produced by it, if you consume the right content for you. I think it's important to have different experiences, many of which come from consuming different mediums, as well as doing things in real life, but a significant part of knowledge to this day has been passed down by books.
Even if we mean 'learning' to be more similar to 'gathering information', I think it can be most efficiently done by reading, or doing. I don't hold as much disagreement there, nor any judgement, but I wouldn't equate the two. Perhaps a bit pedantic, but I read 'liking learning' beyond the means by which it's achieved, and 'hating reading' reads temperamental to me.
What initially attracted me to programming was the ability it gives one to create. As a kid the idea that a “regular” person like myself could make computer programs — and not just simple CLI toys but full on lovingly crafted, end user friendly complex GUI applications — blew my mind. Programs weren’t like every nearly every other product which only ever came out of some factory that nobody saw themselves.
As such my interest in programming comes with a slant towards practical usability. I don’t do well with abstract concepts without a rock solid grounding real world use case, even though those are intellectual candy for a few subgroups of programmers.
Perhaps the fact that our jobs are intellectual is the problem. I find that at the end of the day I don't have the capacity for intellectual pursuits and I find physical hobbies / activities more relaxing. I suspect the opposite is probably also true.
The rise of vibecoding and the disdain many in the industry hold for the skill of software development should fully disabuse you of any vestiges of this notion...
Every single day, here, on "Hacker" news I see folks describe coding as just a means to an end, and that things like code quality, architecture, etc, don't matter.
Welcome to late stage capitalism, where if you can't immediately monetize it its not worth doing (consider how this might explain the rise of gambling as recreation).
https://devoneriksen.com/products/theft-of-fire-orbital-spac...
But take a look at anything by Asimov. I have a collection of his short stories and it is a nice read. Oh, and any short story collection by Chekhov.
One suggestion I would make is to read something from before 1980. No real reason why, but books from 1900 - 1980 work better for me personally, not sure why.
For the record I do like reading. I just don't like all the reading. I tried learning rust by reading the book. Ugh. Horrible for me. Much better experience working on a project of my own. I saw that for some people it worked. Good for them. It didn't for me, and I had to find a different path. I learn by tinkering. Others might learn by copying, or by drawing boxes and arrows. Who am I to judge their firmware?
This is not a bad thing. That's good! Variety in ways of thinking is one of humanity's strengths.
If you find someone who is good at programming but doesn't like reading, try to find out how. You might be able to learn some of their abilities that complement yours.
Novels are fiction by the way.
For some reason I suddenly got an urge to read long deep fantasy. Storm light archive is perfect for this, I recommend play some fantasy reading music on background. It's a bliss, especially in summer afternoon with cold coffe.