Reading Will Make Your Career and Life Better.
Last week I shared an article by Ed Wisniowski over at Dirty Fingers titled Reading is Your Executive Secret Weapon. In it, Ed describes how authors shape an idea through their writing, then hand down lessons and mental models through books, not just news or blogs. He also points out how much you can learn about someone by asking a simple question: What are you reading?
That question hits home with me because someone’s bookshelf will give insights to a person in ways that a person cannot. A bookshelf shows curiosity, values, and the kinds of challenges someone is focused on. It also shows whether someone is willing to sit with complexity long enough for it to change them.
Right now I am reading Outlive by Peter Attia. The underlying theme is not just living longer, it is extending the quality years of life. The goal is more years of quality health with independence, capability, and energy and not simply more years managed by prescriptions and limitations.
Outlive is dense. It is not my natural wheelhouse, and that is part of why I like it. When I finished the cholesterol section, I could not recite the details like a doctor. But I did come away with a sturdier base understanding for how different lipids relate to risk, and how inflammation and the health of blood vessels factor into outcomes. More importantly, it sparked curiosity. The book does what non-fiction books are supposed to: build a foundation strong enough that you can return to it, question it, argue with it, and layer new knowledge on top of it as your understanding grows.
That is what depth feels like. It is not just information. It is information organized into a system that starts to shape your instincts.
I also noticed something else happen as I read it. The ideas started bleeding into my day to day conversations. I mentioned the book to a friend, and we ended up talking about glucose, wearable health tracking devices, and why some people respond differently to the same inputs. He tied parts of the discussion to his own experience with gluten sensitivity and glucose monitoring. Because we could anchor the conversation to a shared reference point, we were not just swapping opinions. We were building a shared mental map with different opinions and perspectives. The book created a stronger connection, and a more productive conversation.
This is not really about Outlive. It is about how books enable connections and thoughts. Shared reading gives you shared vocabulary. Shared vocabulary gives you speed, precision, and understanding. When two professionals have the same foundational understandings and principles, they can move from “what do you mean” to “what tradeoff are we choosing” much faster.
That matters in technology because our work is not defined by syntax anymore. Syntax is the easy part. The hard part is judgment.
I look at the state of many entry level and mid level engineers today and I see a learning culture built around quick tutorials, bootcamps, and increasingly AI driven approaches. Those tools can be useful, and they absolutely can help someone become productive faster. But there is a trade hiding in that convenience. Tutorials are often optimized for simplified examples, not for building the deeper understanding that explains why it works, when it fails, and what it costs. There’s often no consideration around how other enterprise level demands need to be considered in an approach.
Cue the old man comments - I remember having shelves full of Wrox books and spending hours with documentation. Not because it was fun in the moment, but because it forced me to build my own mental model. Documentation and books have a way of showing the whole terrain: the boundaries, the constraints, the edge cases, the language the industry uses, and the historical context that explains why the current approach exists at all.
Today, when I talk to engineers about dependency injection, many can implement it quickly. Fewer can explain the underlying why it is done, or the impact on coupling, testability, object lifetime, composition roots, or the conditions where a pattern becomes a liability. That gap shows up later, when systems get messy and tradeoffs get expensive. Books close that gap because they force you to think in principles, not recipes.
Ed and I have this in common: we both read widely, and we both treat reading as part of our professional practice, not as a hobby we do when we have spare time. Ten years ago, he lent me The Mythical Man Month by Fred Brooks, which I never returned (sorry, Ed). That book is decades old, and it is still relevant because it is not teaching a framework. It is teaching how complex work behaves when humans, schedules, and coordination collide.
The challenges described in The Mythical Man Month still exist today, which is why its lessons remain worth applying across our industry. Teams that internalize those principles tend to build software in a more predictable way. That is another reason books matter for career development: tools change, but principles compound.
Reading also strengthens your ability to focus. In a world where most of our attention is constantly fragmented, the simple act of sustained reading is practice for sustained thinking. That is not a soft benefit in tech. It is a competitive advantage. In Deep Work, Cal Newport makes a similar case in his work on deep focus, arguing that the ability to concentrate on cognitively demanding work is what enables faster learning and higher value output.
And it is not just technical books that matter.
Nonfiction outside your domain expands your problem solving range. Reading in health, psychology, history, economics, leadership, and biography gives you more analogies and more ways to frame problems. It broadens the set of solutions you can imagine. It also makes you more effective in the parts of the job that are not code: influencing, coaching, prioritizing, communicating, and navigating ambiguity.
Fiction matters too. It is one of the few ways adults regularly practice stepping into someone else’s imagination. There is research suggesting that reading literary fiction can temporarily improve theory of mind, which is a way of saying it can sharpen your ability to infer what others may be thinking and feeling. It is a practice of perspective. In leadership, perspective shows up as better collaboration and better decision making across boundaries.
Even the personal benefits are not separate from the professional ones. Reading is associated with reduced stress, and lower stress directly affects the quality of your thinking and decision making.
There is also a basic, underrated mechanism: reading exposes you to more words, more sentence structures, and more precise ways to express an idea. That tends to improve vocabulary and communication over time, which matters when your job increasingly depends on explaining complex ideas clearly.
As a business professional, how does one start to gain the maximum benefit from the ideas that Ed described?
It starts by choosing depth on purpose. It means treating reading like training, not like entertainment you only do when you can get around to it.
It means reading across the entire spectrum. Yes, read blogs and short articles. They are great for discovering ideas quickly, and you can often engage directly with the author. But when something matters, graduate it into a book, a long essay, or primary documentation so you can understand the full shape of the topic.
It means writing alongside reading. Writing is where you find out what you actually believe. If you cannot explain an idea in your own words, you do not own it yet. Reading builds the raw material. Writing turns it into usable judgment. Writing this article alone has made me fully flush out all of the ways reading has helped me, and forced me to look into how it has helped others as well.
Part of being a leader is modeling the behavior. Ask your teams what they are reading. Share what you are reading. Normalize curiosity. Create space for reflection, even if it is informal. Over time, this builds a culture where people are not just shipping features, they are improving how they think.
I encourage anyone to read. Read books. Read blogs. Read magazines. Read history. Read science. Read novels. Pick topics that are close to your job and topics that have nothing to do with it. Go to the library. If you want career growth, do not just chase the next tool. Build the kind of mind that can evaluate tools, tradeoffs, and ideas with depth. Books are still one of the most reliable ways to do that.
