Curiosity and the why

Nathan Chadwick · October 22, 2026 · 6 min read

TLDRRead the short version

I struggle to learn without the why. Steps without meaning bounce off. Context is how my brain opens the door.
Curiosity is not a personality flourish for me. It is a constant hunger for more information, more mechanism, more of the story behind the instruction.
"Just do it this way" works for compliance. It fails for understanding. Once I know why, the how finally sticks.
That same drive shows up at work, in the homelab, in health, in people. I am always pulling the next thread.
Curiosity is how I stay alive to the world. The why is how anything I learn becomes mine.

The missing sentence#

Give me a procedure without a reason and my brain stalls.

Not dramatically. Quietly. The steps sit there like furniture I am not allowed to move. I can copy them. I can even pass a test on them. They do not attach. A week later they are gone, or worse, I am following them without knowing what I would change if the situation shifted.

Give me the why, and the same material lands.

Why this control exists. Why that packet path matters. Why the hormone panel before the prescription. Why the boundary. Why the architecture looks ugly on the diagram but survives production. Once the purpose is clear, the details have somewhere to hang. They stop being trivia and start being a map.

That is why curiosity matters so much to me. It is not a cute About-page line. It is the difference between performing knowledge and actually having it.

Without the why, I cannot learn#

I have always been like this.

School rewarded memory. Work sometimes rewards speed. Both can treat the why as optional decoration: nice if you have time, irrelevant if you can click the buttons in order. For me the why is not decoration. It is the on-ramp.

If I do not understand the point of a thing, my attention will not commit. I will half-listen while hunting for the missing sentence. What problem does this solve? What breaks if we skip it? What are we protecting, enabling, or preventing? Until those answers show up, the content feels hollow, and hollow content does not stick in a brain that is built to chase meaning.

People sometimes read that as stubbornness. Or as needing everything explained before I will move. It is closer to this: my learning system is meaning-first. Rote is a temporary bridge. Understanding is the structure that stays.

Research on curiosity keeps finding the same pattern. When you are curious, the brain does not just want the answer. It prepares to encode. Memory improves for the thing you were hungry to know, and sometimes for the incidental material around it. Curiosity is not only motivation. It is a learning state.

That matches my life almost too cleanly. When someone opens with purpose, I can take in volume. When they open with "just follow these steps", I am already somewhere else, looking for the door they forgot to point at.

The brain that will not stop asking#

My mind is constantly curious.

Not in the polite, dinner-party sense of having a few hobbies. In the restless sense. There is always another tab open in my head. Another system to understand. Another paper, another protocol, another historical thread, another health marker, another product roadmap, another "wait, but how does that actually work". Information is not a chore I schedule. It is a pull.

I learn best when I can follow that pull. Homelab nights that start as "fix one VLAN" and end as three hours of firewall behaviour, multicast, and why Cast breaks across segments. Security work that will not settle for a vendor slide when the real question is what the attacker gets if this control fails. Training, sleep, hormones, nervous system: I do not want the slogan. I want the mechanism.

Need for cognition is the academic name for enjoying effortful thinking. Curiosity research calls related traits interest and deprivation curiosity: wanting to know because it is enjoyable, and wanting to know because the gap feels uncomfortable. I live in both. The gap is almost physical. An unexplained rule sits wrong. An unexplained emotion sits wrong. An unexplained outage sits wrong. The system keeps pinging until the picture is complete enough to stand on.

That is also why "because I said so" has never worked on me as a learning strategy. Authority can get compliance. It cannot feed curiosity. And without that feed, I am not really learning. I am waiting for a reason.

How this shows up in real life#

In infrastructure and security, the why is the whole job.

Anyone can recite that you should segment IoT, require MFA, or log privileged PowerShell. The useful engineer is the one who can say what failure mode each control is buying down, what it costs in friction, and when the trade-off stops making sense. Customers do not need a priest of best practice. They need someone who understands why the recommendation exists in their environment.

In health, the same pattern. A label without a mechanism left me looping for years. Depression as a description. No bloods. No deeper question. The moment someone treated the why as worth hunting, the story changed. I wrote about that properly elsewhere. The short version here is simple: I cannot build a life on instructions that refuse to explain themselves.

In relationships, curiosity is care when it is aimed well. What happened. What that tone meant. What the other person needed. And it is a trap when it turns into endless replay of unfinished emotional tickets. I know that version too. Sticky attention does not only chase knowledge. It chases unresolved meaning. The skill is knowing which threads deserve another hour, and which ones are rumination wearing a lab coat.

The gift and the cost#

Constant curiosity is a gift.

It is how I get good at things that do not come from a single course. It is how I stay interested in a world that keeps changing. It is how a sales engineer who used to be a lead infrastructure engineer can still get excited about a packet capture, a peptide paper, a master plan, or a nervous-system diagram at midnight. Breadth is not distraction when the through-line is "I want to understand".

It is also a cost.

You cannot know everything. The feed never empties. There is always one more why behind the why you just found. Depth in one tunnel means something else waits. People who learn by accepting the checklist move faster in the short term. I move slower at the start and further once the model clicks.

I am fine with that trade. I would rather own fewer things deeply than recite many things emptily.

What I am asking for, including from myself#

From teachers, managers, vendors, doctors, and partners: lead with purpose when you want me to learn. Tell me what we are protecting, fixing, or becoming. Then give me the steps. I will take the steps seriously once they are attached to a reason.

From myself: keep the hunger, and aim it. Curiosity without direction becomes noise. The why is not an excuse to never ship. It is the condition that lets shipping mean something. Learn enough of the mechanism to act. Act. Then pull the next thread.

The point#

Curiosity matters to me because it is how my brain stays awake.

The why matters because without it, information does not become understanding. It becomes temporary noise I can mimic until the exam, the change window, or the conversation ends.

I am always seeking more. More context. More mechanism. More of the story underneath the instruction. That is not indecision. That is how I learn. And when the why finally shows up, everything else has a place to land.