← All articles

The Curious Engineer Wins in the Age of AI

AI changed the tools, not the trait that matters most. Curious engineers still have the edge.

Josh Hamilton4 min read
Editorial illustration of a magnifying glass revealing the gears inside a puzzle box.
Reading appearance

Preferences stay in this browser.

Keep or share this article
Download Markdown

Use your browser’s print dialog to print or save a PDF.

You can also select and copy the citation above.

Look up a technical term →

I recently started a new role, and it is the first time I have done that in a world where AI now handles a lot of the day-to-day work I used to do myself.

I have been an engineer for more than 12 years. I remember when solving a problem meant opening Google, scanning Stack Overflow, and filling a browser with tabs until something clicked. That workflow shaped a lot of my early career.

Today the process looks very different.

Now I can open a terminal, load up an AI tool, describe the problem clearly, and get help in minutes instead of hours. The interface changed. The speed changed. The leverage changed.

But the trait that matters most did not change at all.

The engineers who will win in the age of AI are still the most curious ones.

Early in my career, people often told me I seemed like the person who knew everything about the codebase.

The truth is I did not.

I was just good at debugging. I was willing to dig. I was willing to sit with messy code, follow the thread, and keep pulling until the system started to make sense.

When teammates complimented my knowledge of the codebase, I would usually tell them the same thing: the answers were right in front of all of us. I was not magically more informed. I was just more willing to look.

That mindset still matters now, maybe more than ever.

The engineers who struggled most were usually not the ones with the least ability. They were the ones who tapped out too early. They would say, “I do not know that part of the codebase,” or, “I have never worked in that area before,” and immediately go searching for the one person who had.

Now that “person” is often an AI model.

That changes the workflow, but it does not remove the need for initiative. If anything, it raises the ceiling for people who are willing to explore. You can ask better questions, inspect unfamiliar systems faster, and debug across parts of the stack that used to feel out of reach.

That is why I think the old excuse of “I cannot do this because I do not know that area” is getting weaker by the day.

You may not know it yet. That part is fine.

What matters is whether you are willing to investigate.

AI does not reward passive engineers. It rewards engaged ones. The people who get the most out of these tools are the ones who know how to chase context, test assumptions, refine prompts, and keep going until they understand what is actually happening.

That is the same instinct that made strong engineers stand out before AI. The difference now is that the feedback loop is dramatically faster.

What used to take me 30 tabs and half a day can now take a few focused minutes. I still need judgment. I still need to verify what I am seeing. I still need to understand the system well enough to know whether the answer is useful.

But the path to clarity is shorter.

So this is the shift I keep coming back to:

AI is not replacing the value of curiosity. It is amplifying it.

The engineer who waits to be told will fall behind. The engineer who digs, asks, tests, and learns will keep compounding faster than ever.

In this era, the advantage does not belong to the person who has every answer memorized.

It belongs to the person who refuses to stop looking.

Your private notes

Only on this device. Notes are never published or sent to a server. Keep up to 100 notes, with 10,000 characters per article. A full store never discards an older note.

Enable JavaScript to keep private notes.

Keep the curiosity going

career

What engineers are feeling right now

My take on why so many engineers feel the pressure, but few of us say it out loud.

4 min read
career

Use your git history to write a resume that reflects real work

A practical workflow for using `.git` with Claude or Codex to turn shipped commits into accurate, role-tailored resume bullets.

7 min read
ai

Productivity is high but motivation is low

The uneven emotional math of shipping faster with AI while feeling less attached to the work.

4 min read

Article image

Open original image ↗

Keyboard shortcuts

Shortcuts stay out of text fields. Extra shortcuts are off until you enable them on this device. Ctrl or Command K is always available.

?
Open this help
Ctrl / ⌘ K
Open site search
Alt A
Browse articles
Alt R
Open your reading list
Alt T
Browse topics
Escape
Close dialogs or leave article focus mode