She Did Everything Right and Still Got Stuck for Hours

She did everything right.

My wife Alma is the most resourceful person I know.

She's not a developer. But she's sharp, she's determined, and when she decides she's going to figure something out.. she figures it out.

Yesterday she went to an AI workshop. Came back fired up.

Downloaded Claude Code. Downloaded Obsidian. Cloned a GitHub repo full of skills and setup files. Fed everything in herself.

Got interrupted halfway through. Had to go handle family stuff.

Came back later, picked right back up, asked the AI if it had enough to keep going.

"Yep." And it walked her through the whole thing.

Hours later.. still stuck.

Same loop. Cycle after cycle. MCP connections not working. JSON file in the right place. Following every instruction to the letter.

She reached out to me.

I looked at it for about 30 seconds.

"You're in the browser. You need to be in Claude Desktop."

That was part of it. Then we switched, and it still wasn't connecting, because Claude Chat was trying to spin up an MCP server to the file system.. which it can't do.. even though it was confidently telling her exactly how.

Didn't need an MCP server at all. Needed Claude Code, which has file system access natively.

Two minutes. Done.

Here's what I want you to notice.

The AI wasn't wrong about the steps. It just didn't have the lived experience to recognize what environment it was operating in and what that meant for the approach.

It had knowledge.. but needed discernment.

Discernment is what you get after you've been burned enough times to know what it feels like before it goes wrong. It's the thing that made me look at that setup and immediately know the surface mattered more than the steps.

You can't prompt for discernment. You can't Google it. You accumulate it.. through pain.. losses and wins.

If you're early in your AI journey, this is the most valuable thing I can tell you:

Find a human who has the scars.

A YouTube channel. A free group. A paid community. A mentor. Something.

Because hours of spinning, files you don't recognize, errors you've never seen, not knowing if you just broke your whole machine.. that's the real cost. And all it takes to short-circuit it is five minutes with someone who's been there.

The investment pays back fast.

🚀

- James

1 comment