The call started with my boss.

One day the head of our healthcare foundation called me in. He had a younger friend, he said — a startup CEO who ran a distribution company. This guy had used AI to automate huge parts of his business. The boss thought he was practically a genius. Then he added something I didn’t forget.

“You’re the only person at this hospital who’ll understand what he’s talking about. Keep that in mind.”

That line stuck with me. For months I’d been quietly tinkering in the treatment room, building small tools for myself. This was the first time someone looked at it and saw something worth taking seriously. He handed me the CEO’s number and told me to call. He didn’t understand this stuff himself, he said. Go talk to the person who does.

Two amateurs on the phone

So I called a man I’d never met.

We talked for a while. I fumbled through descriptions of the little tools I’d built. He told me what he’d been doing on his end. And somewhere in the middle of it, I felt an odd kinship. We had started in the same place. Neither of us had ever learned to code. We were just two people who got fed up with something and started poking at it.

That matters more than it sounds. I’d spent months assuming “real” software people lived in some other world. Here was someone running a company on tools he’d built without a single class. He wasn’t a genius from a far-off place. He was me, a few steps ahead.

Then he said one thing that changed my whole setup.

“Forget that tool. Try the one called Claude.”

That was March 12th. I hung up, got approval to pay for it, and signed up that same day. From then on I ran both side by side — the Gemini I’d been using and the Claude I’d just bought — giving them the same jobs and watching what each one did.

I didn’t need long to decide

The comparison was over fast.

Gemini was good at telling me about code. I’d ask, it would answer, and then the work was still mine — copy the answer, paste it, patch it, fix what broke. I was the one stitching everything together. Claude worked differently. I described what I wanted, and it just went and did it.

It hit harder because of what I’d been fighting days earlier. The earlier tool I’d used was clumsy in a way that drove me crazy. Ask it to change one thing and it would wipe out everything else that was working fine. Claude touched only what I named. What I told it to leave alone, it left alone. It didn’t invent extra work I never asked for.

That alone felt like the ground had shifted under me.

I’m not exaggerating when I say it was a new world. Things that used to take days — saving copy after copy, inching forward, undoing my own mistakes — now took a few sentences. My pace picked up. Ideas I’d only ever filed under “wouldn’t it be nice if” started appearing in front of me as fast as I could describe them.

What the better tool actually changed

Here’s the part worth sitting with.

The phone call didn’t make me smarter. I learned nothing new about code that day. I still didn’t know what a variable was. What changed was the gap between saying what I wanted and having it exist. That gap had been wide and full of friction. Suddenly it was almost nothing.

When the cost of trying something drops that far, you try far more things. The earlier tools made every experiment expensive, so I rationed my ideas. The right tool made experiments cheap, so I stopped rationing. That shift — not talent, not knowledge — is what unlocked the next year.

If you’re stuck, don’t assume the problem is you. Sometimes you’re just holding the wrong tool, and the fix is to swap it, not to try harder.

I’d resisted switching for a while. I’d already learned one tool. Starting over with another felt like wasted effort. It wasn’t. The day I let go of the familiar thing was the day everything sped up.

A new wall, right on cue

A single phone call swapped out the tool in my hands. And the moment the tool got good, a completely different kind of wall appeared.

Everything I’d built so far lived inside the hospital. None of it ever reached the outside. The internet, public access, anything beyond our own walls — I’d never once opened that door. I’d even promised my department head it would stay internal, and I’d meant it.

Then something came up that forced me to cross that line. That’s the next story.