TL;DR: Experience is a liability when it kills curiosity. AI proficiency is a byproduct of hundreds of hours spent in invisible iteration.
The Expertise Trap
Deep experience often triggers intellectual rigor mortis. You have seen the “right” way to do things for a decade, so you stop looking for the better way. A beginner mindset is not about being a blank slate (which is just another word for useless). It requires enough of a foundation to know when you are headed in the right direction, or perhaps a parallel path with new perspectives, before getting back on track.
If you have twenty years of experience but no curiosity, you are just a legacy system waiting for a decommission date. The ROI on a “beginner” attitude is higher because it allows for rapid pivoting. You need the basics to provide a compass (to avoid spending days debugging a syntax error), but you need the mindset to explore the paths that lead to breakthroughs.
The AI Sweat Equity
There is a myth that prompting is a low-skill activity. It is not. Most people really good at prompting have iterated and learned. The developers currently running multiple agents and building software 4 to 10 times faster than they did last year have been in months of practice to get there.
This is iteration 0 work. It is messy and mostly undocumented (because the tech moves faster than the README files). What makes it daunting for those first starting is that the people who are now good at it did it without formal training. There is a tendency to forget how much effort went into the initial struggle.
Building the Mental Infrastructure
Learning new technical skills requires toggling between different cognitive states. Barbara Oakley (author of Learn Like a Pro: Science-Based Tools to Become Better at Anything and Learning How to Learn, among other great books) describes this as the tension between focused and diffuse modes. Focused mode is for the granular syntax: the structure of a prompt or a script. Diffuse mode is where the beginner’s mindset lives. It is the relaxed, curious state that allows your brain to make the non-linear connections required to solve a problem that does not have a documentation entry yet.
She emphasizes chunking: breaking complex concepts into small, functional units until they become second nature. This prevents cognitive overload when the system throws an error you have never seen before. Curiosity is a tool that keeps you in the diffuse mode long enough to see the “big picture” before diving back into the details. I took her class on Coursera at the start of my AI journey, and I recommend everyone do the same, even if your interests are in other areas. It applies to learning anything, and you will thank yourself for doing so.
They say “oh, it’s easy, you just do this”, which looks like magic to the beginner. It is not entirely different from visiting a new area and asking a local for directions. Every time they start with “Oh, that’s easy”, there is a good chance you are going to get lost following their directions.
Locals navigate by landmarks that either do not stand out to an outsider or have disappeared from all but the local’s memories. They tell you to turn where the oak tree used to be or past the shop that changed names five years ago. They have internalized the route so deeply they forget the friction of finding it the first time.
And sometimes, that makes the trip more fun. Stop looking for the “perfect” prompt or the “right” workflow. Spend more time being “lost” in the tool. The goal is not to avoid the detour: the goal is to have a strong enough foundation to know how to get back to the main road once the detour stops being productive.
A Simple Roadmap
If you haven’t begun your journey with Generative AI, or feel a bit lost, here’s a simple roadmap to help you along:
- Pick one model and stay there: Stop comparing benchmarks and just use one tool (Claude, GPT, or an LLM via API) for a week straight to understand its specific “personality.”
- Iterate on a single prompt 50 times: Don’t just accept the first output. Change one variable at a time until you understand exactly what triggers a hallucination vs. a logic block.
- Read the system prompt documentation: Most users treat AI like a search engine. Read the actual technical guides on “system roles” and “temperature” to understand the controls.
- Practice manual orchestration: Before you try to automate a multi-agent system, act as the agent yourself. Copy the output of one model into another and manually fix the “gotchas” in between.
- Fail on purpose: Try to make the model break. If you don’t know the edges of the tool, you won’t know when you are standing on a cliff.
© Scott S. Nelson