Orientation / Lesson 00

Chicken First

Begin with practice. Let theory arrive after contact with the work.

In this lesson:

Two ways to learn: theory first (egg) or practice first (chicken)
Why theory-first breaks down for complex skills like working with AI
How this curriculum is built around practice
Permission to be messy while understanding forms

This is not a lesson about working with AI. It is a lesson about how to learn to work with AI. Read it first — it shapes how you should approach everything that follows.

Two Ways to Learn

There are two fundamentally different ways to learn something.

Egg First (Theory → Practice)

You study the concepts. You learn the framework. Then — later — you try to apply it.

Example:

Study what a “good test” is
Learn testing patterns and best practices
Then, finally, write some tests

The problems with egg-first:

It’s abstract. You haven’t felt any of it yet.
You’re applying theory to situations you’ve never experienced.
By the time you practice, the theory has faded.
You see what you were told to see, not what’s actually there.

Chicken First (Practice → Understanding)

You do the thing first. You build something. You pay attention to what happens.

Understanding emerges through the doing. Then — later — you name what you learned. You articulate the patterns. The naming becomes your theory.

Example:

Write code with AI
Watch what your tests catch and what they miss
Understand, through practice, what a test actually does
Now the theory is yours, because you lived it

What chicken-first gives you:

It’s concrete. You’re living it, not imagining it.
You discover what’s actually true, not what you were told.
It sticks, because it’s in your muscle memory.
You can teach it, because you know it from the inside.

Why Egg-First Fails for Complex Things

Most education is egg-first: learn the theory, then apply it.

That works fine for simple, mechanical skills — changing a tire, the quadratic formula, SQL syntax. The instructions are the skill.

But for complex, emergent skills — anything requiring judgment, taste, or presence — egg-first breaks down. The theory is abstract; the practice is real.

You can read about “good partnership with AI” for weeks. Until you’ve cycled a hundred times, paid attention, and felt what works and what doesn’t, you don’t know it. You know the words. You don’t know the thing.

Real Understanding Comes From Doing

The people who deeply understand something almost always learned it chicken-first.

Great programmers didn’t start by studying what good code is. They wrote bad code, watched it break, wrote better code, watched it work. Over years, understanding emerged.

Great writers didn’t start with narrative theory. They wrote badly, got feedback, wrote again — across hundreds of pieces.

Great designers didn’t start with design principles. They made ugly things, kept working, and made beautiful ones.

In every case, the theory came after. The chicken came first.

This Curriculum Is Chicken-First

This curriculum is not “here’s how to work with AI — now go do it.”

It’s “go do this thing, pay attention to what happens, and then we’ll name what you learned.”

Every lesson follows the same shape:

A concept, introduced briefly
An exercise you actually do
A reflection on what you experienced

By the end, you won’t just know these concepts intellectually. You’ll have lived them — and the names will be labels for experiences you’ve already had.

You’ve Probably Lived This Already

Think about anything you truly understand — cooking, a sport, a craft, the job you’re good at. Chances are you learned it by doing, and the explanations only made sense afterward.

A common version: someone wants to learn to code but stalls on “which language should I learn first?” That’s egg-first thinking — theory before practice — and it’s paralyzing. The moment they switch to “I want to build this thing” and start building, the language becomes secondary. It gets learned through the building, and eventually it’s just the tool that fits the work.

Working with AI is the same. You won’t learn it by studying how to work with AI. You’ll learn it by working with AI, cycling, and noticing what actually happens.

Permission to Be Messy

Chicken-first learning is messy.

You’ll do things “wrong” at first. You’ll run clumsy cycles. You’ll miss the signal. You’ll be confused.

That’s not failure. That’s the mechanism.

Egg-first learning expects you to get it right from the start, because you studied. Chicken-first learning expects messiness, because messiness is how understanding develops.

Give yourself permission to be bad at this for a while. The understanding comes through the doing — including, especially, the parts that don’t work.

How to Use This Curriculum

Approach every lesson chicken-first:

Read the lesson — enough to get the basic shape of the concept
Do the exercise — don’t skip this; it’s where the learning happens
Reflect — what did you experience? What surprised you? What differed from what you expected?
Repeat — understanding deepens with every cycle

Don’t try to understand everything before you start. You can’t. You’ll understand it by doing it.

The Difference in Practice

Egg-first: “I should learn testing, so I’m reading a book about testing.”

Chicken-first: “I want to build something solid, so I’ll write tests that lock in what matters — and through doing that, I’ll understand what testing is.”

One is studying. One is building.

One produces knowledge. The other produces understanding.

Exercise: Identify Your Chickens

Time: 20 minutes

Think of something you learned well — something you actually understand and can do.

Ask yourself:

Did I learn it egg-first (theory → practice) or chicken-first (practice → understanding)?
If chicken-first: what was the chicken? What did I do first?
If egg-first: do I actually understand it, or do I just know the theory?

Notice the difference. Most things you truly understand, you learned chicken-first.

An Old Invitation

This way of learning has an old name. The Buddha told his students: ehipassiko — “come and see for yourself.” Don’t believe the teaching; test it against direct experience. If it doesn’t hold up, discard it.

The same invitation applies here. Don’t believe this curriculum. Run the cycles. Notice what actually happens. Keep what survives contact with your experience and discard what doesn’t.

The truth isn’t in the lessons. It’s in the doing.

Key Takeaway

You don’t need to understand the theory before you practice. That’s backwards. You practice, you pay attention, and understanding emerges. This curriculum is designed that way on purpose.

Do the thing. Pay attention. Let understanding arrive.

The chicken comes first.

Next: the rhythm you’ll be practicing inside for the rest of the curriculum. The loop.