Reading Beyond Code
There is a strange pressure that comes with being interested in programming. It can feel as if every free hour should go toward learning another language, finishing a course, or reading the documentation for whatever tool everyone is discussing this week.
Even rest can start to feel like a task you failed to complete. You open a novel and an uncomfortable voice speaks up: you could be studying algorithms. You write something without a single line of code and wonder what it is even for.
I no longer want to measure every book that way. A book does not have to make me faster at the keyboard to justify the time I give it. The question I care about is different: what do I find when I read and write outside programming?
Not all learning has to look like a class
Technical books are necessary. When I need to understand an API, fix a query, or learn how a tool works, I want precise documentation, examples I can run, and explanations that do not hide the difficult cases. A novel cannot replace any of that. But it would be a poor view of programming to reduce everything a programmer needs to think about to what fits inside a manual.
Fiction lets me live for a while with incomplete information. A character does not come with official documentation. Their motives may contradict each other, and a decision that seemed absurd in chapter three can take on another meaning much later. It looks nothing like following a tutorial, yet in software we also make decisions with incomplete requirements and systems that carry histories nobody wrote down. Essays give me the other half: watching someone arrange an idea, present evidence, acknowledge an objection, and decide how far the argument can go. I can disagree and still learn from how the case was built. Reading is not about collecting other people's conclusions. It is also about examining how they reached them.
When we try to create something, we do not start from an empty space. We connect concepts, images, and experiences already stored in memory, and reading across different subjects and genres can supply raw material for new associations. The important word is can. Twenty novels do not guarantee twenty brilliant ideas. Creativity is not a loyalty card where every book earns a guaranteed reward. But an information diet that is too narrow does limit the comparisons available to me. If I consume only programming tutorials, most of my references will be other tutorials. When I wander into history, science, or psychology, I find other ways of describing a conflict, ordering time, or asking why someone acts the way they do. Maybe one of those connections ends in a clearer interface. Maybe it produces nothing visible and just keeps me company for an afternoon. Both possibilities seem valid to me.
The discomfort of changing my mind
One book I recommend is Think Again by Adam Grant. What I value is its focus on reconsidering, unlearning, and holding on to humility and curiosity. It does not treat intelligence as automatic protection against error: an intelligent person can become very good at defending a wrong idea.
That feels especially familiar in programming. Just walk into a conversation about languages, editors, or frameworks. Sometimes we stop discussing a decision and start defending an identity. We no longer ask what the project needs; we want to prove that our favorite tool was the right answer from the beginning.
Imagine you have spent months saying a certain language is bad because you watched a video mocking it. Then you find a project where that choice makes sense. Do you change your mind, or do you look for twenty reasons not to admit it? I am not staging the scene to make fun of anyone. Changing your mind is hard. It is hard for me too. That is why I value books that do not hand me one more certainty to show off, but better questions for examining what I think I know.
Reading fiction does not grant social superpowers
Some attractive claims get repeated too quickly. One says that reading fiction makes you more empathetic. It sounds good, spreads easily, and turns reading into a kind of moral vitamin. The problem is that the evidence does not support such a confident claim.
A 2018 meta-analysis by David Dodell-Feder and Diana Tamir found statistically significant but small effects of reading fiction on certain measures of social cognition: around g = 0.15 to 0.16. Replications that exposed participants to a single short story in one sitting (Panero et al., 2016) did not find the effect. The meta-analytic evidence, on the other hand, is consistent: the 2018 analysis and a more recent meta-analysis (Wimmer et al., 2024) agree on a small effect, g ≈ 0.14. The honest summary is a small effect, replicated at the meta-analytic level and disputed experiment by experiment. And causality remains in doubt: reading may have a small influence, or people who already have certain skills or interests may simply choose to read more fiction.
I prefer to keep the modest version: some studies find small effects on certain measures of social cognition. Nothing more. I do not need to inflate the evidence to defend fiction. A story can interest me, unsettle me, or show me a perspective I had not considered, even if I cannot turn that experience into a percentage of personal improvement afterward.
Writing shows me where the idea ends
Reading lets me follow another person's thinking. Writing forces me to find out whether I have a thought of my own.
While an idea remains in my head, it can seem complete. Then I try to put it on a page and the gaps appear. I use a word I cannot define. I repeat a conclusion because I still do not have an argument. I jump from problem to solution without explaining what happened in between. Writing makes those failures visible.
There is modest evidence pointing in this direction. A 2007 study with university biology students (Quitadamo and Kurtz) found that certain writing activities improved critical thinking in that setting. It is a concrete result, not a universal law. It does not prove that keeping a journal makes anyone better at every discipline, but it does remind us that writing can be part of the work of thinking, not just the presentation of a finished thought.
A few months ago I wrote El tiempo que compartimos (The Time We Shared), dedicated to someone very important to me. About a month and a half ago I wrote another one for that same person: De mí para ella (From Me to Her). I do not mention them as credentials. I mention them because writing on your own can exist outside a career, a grade, or a publication. You can write a scene, a letter you decide not to send, an explanation of something you just learned, or a question you still cannot answer. The point is not to imitate a famous author. It is to stay in front of what you think a little longer, until you notice what you can explain and what you were only assuming.
This reaches into code as well. If I cannot explain why I chose a solution without hiding behind complicated words, I may not understand the decision yet. Writing does not guarantee that my reasoning is correct, but it makes it harder to pretend that it is complete.
When reading becomes another dashboard
I have nothing against tracking books, marking pages, or joining a reading challenge. The problem starts when the record eats the experience. A streak can get you to open a book during a difficult week; it can also push you toward short texts just to keep a number alive. A summary can clarify an idea; it can also make you read with your mind only on what you will produce later.
Self-determination theory explains why: when autonomy, competence, and connection with others sustain motivation, controls and some rewards can weaken what used to be intrinsic. Not every goal is bad, but it is worth noticing what happens when an activity you chose for pleasure starts to feel monitored. If a streak helps you, use it. If it makes you read with anxiety, let it go. And rereading something you already know still counts as reading, even if an app does not celebrate it.
I am tired of metrics that take a human activity and demand proof of performance. How many books a year? How many pages a day? How many applicable ideas did you extract? Measurement can inform. It should not decide for us what is worthwhile. I also do not want to turn this recommendation into one more obligation for someone who already feels behind learning to program, or to sell nontechnical books as secret tools for greater output. That would repeat the problem in a different disguise.
If you are a teenager learning to program, you do not need to fill every afternoon with courses to prove that you care. There will be time to read documentation, practice, break things, and build projects. You can also read a novel because you want to know what happens, open an essay because a question is bothering you, approach psychology carefully without using it to diagnose your friends, or write something no one else will ever see. None of that automatically makes you a better programmer. It does not have to. Sometimes a wider view helps us reconsider an idea; other times, a book simply gives us a good afternoon.
That is enough. Not every book has to justify its existence by improving a metric.