The Recursive Learning Loop

When you don’t understand something, you ask the same tool to explain it. When you want a different approach, the same tool shows you options. When you’re stuck, the same tool unsticks you.

No other tool has been its own instruction manual, study guide, and tutor. Courses are training wheels on a bike that can balance itself—if you just start pedaling.

*“Each independent filmmaker I spoke to said that, in the case of these films, AI had enabled them to tell a story they otherwise wouldn’t have had the budget or time to tell.”*Let’s talk about how I actually use Claude Code to learn as I build. I’ll teach you some concepts in this article, and in future issues I’ll go super deep into use cases such as creating new greenfield projects or modernizing brownfield legacy codebases.

How to maximize learning rate

First, some theory.

There’s a fundamental meta optimization question beneath the desire to optimize the acquisition of new skills.

The TLDR of the science on skill acquisition is something called deliberate practice.I write more about it here.

• Focus: Deliberate practice is about targeted effort. Identify specific areas of weakness and work on them with full concentration. You’re not just doing something over and over mindlessly; you’re refining your approach every time, intentionally.
• Feedback: Seek immediate feedback. Whether it’s from a coach, mentor, or even self-reflection, you need to know what you’re doing wrong to correct it. Don’t just rely on how it feels—get concrete insights into your progress.
• Fix It: Integrate your learnings from the feedback and try again intentionally. Use mental representations (the mental image of what a successful performance or execution looks like) to improve.

Here, Claude Code (and yourself) are the ones giving the feedback.

And Claude Code has access to search the internet and reason.

It’s not perfect—nothing is, that’s why you have your human brain for critical reasoning and judgement. But damn have I found I’ve been able to get up and running on new domains quickly.

For example, I didn’t really know anything about capturing video testimonials dynamically from customers and having it auto update into a widget on my website. I didn’t even know where to start.

I just asked Claude Code what I should do and what key decisions I need to make, and 10 minutes later I was set up on a solution called Senja and had my testimonials up on my website.

6 Patterns That Turn Claude Code Into Your Personal Tutor

Here are 7 conversation patterns I use constantly in my Claude Code sessions. Each one turns Claude Code from “a tool I operate” into “a tool that teaches me while I operate it.”

I was building Clarity and kept hitting moments where I didn’t understand what Claude Code had just done.

Instead of Googling, I just… asked it.

And realized it was a better teacher than any documentation I’d ever read.

Pattern 1: “Explain What You Just Did”

After Claude Code does something complex, type:

Explain what you just did and why you chose that approach over the alternatives.

This is the single highest-leverage learning move.

Claude Code explains its reasoning, names the patterns it used, and often mentions approaches it considered but rejected.

I used this when Claude Code refactored one of my files into three separate ones for a feature I was building.

I had no idea why.

The explanation taught me about separation of concerns better than any article—because it was my code, not some generic example.

Claude Code isn’t explaining the concept in the abstract.

It’s explaining why your specific code benefits from this specific reorganization.

So it’s way more likely to stick.

Or, said more simply, how can I MAXIMIZE my learning rate?

The reason this works: context.

I’ve learned that with the new AI tools, you don’t need to know how to write code. You need to know how to direct the thing that writes code. And the only way to learn that is practice.

Can I optimize my skill acquisition rate?

Pattern 2: “Show Me Three Ways”

Show me three different ways to accomplish this, with the tradeoffs of each. Which would you recommend for my specific situation and why?

Two things happen. First, you stop accepting the first solution blindly. Second, you learn that most problems have multiple valid approaches — and the “right” one depends on context.

I asked this when building our landing page. Claude Code showed me a static HTML approach, a React approach, and an Astro approach. Five minutes of reading those tradeoffs taught me more about frontend architecture than a week of tutorials.

Pattern 3: “What Does This Mean?”

What does [specific term or concept] mean in this context? Give me a few metaphors to grasp it. Explain like I'm a smart founder who doesn't code regularly.

That last line matters.

“Explain like I’m a developer” gets jargon.

“Explain like I’m a smart founder who doesn’t code regularly” gets the concept without the syntax noise.

Every concept sticks better because you encountered it while building something real, not while reading a textbook.

Pattern 4: “What Should I Learn Next?”

This one surprised me the most:

Based on what we've been building together, what are the three most important things I should understand better to be more effective working with you? Be brutally honest and relate it to my goals.

Claude Code analyzes your conversation patterns, identifies where you’re getting stuck, and recommends specific concepts to learn.

It’s a tutor who’s been watching you work and knows exactly where your gaps are.

When I ran this after a week of building Clarity’s content system, it told me to understand file structure conventions, git branching, and markdown formatting better.

It was dead right.

Those were my three biggest friction points.

Pattern 5: “Review My Thinking”

Before you ask Claude Code to build something, describe your plan first:

Before you build anything, here's what I'm thinking:

[Describe your approach in plain English.]

Am I thinking about this the right way? What am I missing?

This is founder mode.

You’re proposing a strategy and getting feedback before execution. Claude Code tells you what’s solid, what’s off, and what you haven’t considered.

The compounding here is enormous.

You start developing intuition without writing a single line of code. Over time, your plans get tighter and you need fewer corrections.

That’s not learning to code.

That’s learning to think—which is more valuable.

And you protect yourself from becoming dumber, which is happening to a lot of people using AI.

Bonus.

Before committing to an approach:

When you see something you don’t understand, don’t skip it. Don’t Google it.

LEARN WHAT THE WORDS AND THINGS MEAN!

Your future self will thank you.