What Reading Gave Me Wasn't Knowledge — It Was the Habit of Thinking from Multiple Angles

What Changed Wasn’t My Knowledge

Honestly, I used to think people read books to “learn things.”

I read during my commute and right before bed. It started as a battle against sleepiness, and somewhere along the way it turned into the time my mind actually sharpens.

After enough years of this, something quietly surprised me: the biggest gain wasn’t “more knowledge.”

Knowledge is searchable. Technical problems get solved by Qiita or official docs. The thing only reading gives you sits somewhere else entirely.

The Nature of Intellectual Richness

What reading gave me is “the ability to form my own answers.”

When I read, questions just show up uninvited: “Is that really true?” “What about in my case?” Following those doubts — asking, looking up, sitting with them — I end up arriving at answers that are mine, not borrowed.

Repeat that process enough times, and something shifts. You start being able to interpret the same event from several angles at once.

I call this “intellectual richness.” Or, more practically, how many perspectives you can hold for a single thing.

What Does “Multiple Perspectives” Mean?

Picture a familiar workplace moment:

Deadline approaching. A teammate says: “I don’t think I can finish this task.”

Single perspective: “Why didn’t you say something sooner?” → Blame.

Multiple perspectives:

Was there an atmosphere that made speaking up hard?
Was the estimate itself too optimistic? Was my review the bottleneck?
Isn’t the fact they could be honest actually evidence of psychological safety?

Same event. Same five seconds. But adding angles changes what you do next. Instead of blame, you reach for system improvement. That’s the practical payoff.

Where It Helps in Engineering

Code Review

Start with “why did they write it this way?” Code that looks inefficient often has invisible constraints behind it. Understanding intent before suggesting changes gets you better buy-in and far better team learning.

Requirements Definition

Instead of implementing what the client asked for verbatim, dig into “why is this feature needed?” and “what’s the actual problem to solve?” Finding the real problem under the surface request is just multi-perspective thinking, applied.

Incident Response

Steer the conversation toward “why did it happen” and “how do we prevent recurrence” — not “whose fault is it.” Another moment where single-perspective thinking (the blame game) does real damage.

Curiosity Comes Later

“Having questions is important” — sure. But what if you don’t have curiosity in the first place? You might be feeling that contradiction right now.

In my experience, curiosity arrives as a result of reading, not as a prerequisite.

Read a book → Questions arise → Self-questioning → Form your own answer
  → See reality through that answer's lens → New interpretations are interesting
    → Want to know more (= curiosity) → Read another book → ...

You don’t need curiosity to start. Just open one book. The cycle handles the rest.

Small Practices for Continuous Reading

Here’s what I personally try:

Commute reading — Replace phone time with book time. That’s it.
15 minutes before bed — Don’t aim for full comprehension. Skimming counts.
Note the lines that snag you — Saving “seeds for self-questioning”
Alternate technical and philosophical books — Switch brain modes to dodge burnout

If you’ve been telling yourself “I should read more” for months, maybe pick one book today and read three pages. The trick is starting — not finishing.

“No Effort Goes Unrewarded” — How the Concept of Accumulating Luck Changed My Work — How a book changed my definition of effort
“Breathing Through the Years” — Janet’s Law and Working with Time on Your Side — Habits for keeping the brain active
“Black Box Thinking” — Life Is Too Short to Experience Every Failure Yourself — The importance of accumulating and analyzing failure