10,000 Iterations, Not 10,000 Hours

The Lie We Were Told

Somebody once told us it takes 10,000 hours to master something. Malcolm Gladwell made it famous. Practice for a decade, grind through the repetition, and eventually you become world class.

I bought into that for years. I spent over 20,000 hours inside a computer learning to code. I sharpened my axe every single day. And I did get good. But I also burned out, ran out of money, and watched entire industries shift underneath me while I was heads down perfecting skills that were about to become commodities.

Here is what nobody told me: hours don't matter if you never stop to look at what you built.

Iteration Is the Real Skill

The people I know who are building the most interesting things right now are not the ones who practiced the longest. They are the ones who iterate the fastest.

Build something. Look at it. Ask yourself what is working and what is not. Change it. Build it again. That loop, that cycle of creation and reflection, is where the real learning happens.

I watch this play out every week in our workshops. Someone shows up on Wednesday having never touched a terminal before. By the end of the session they have a working project. Not because they crammed 10,000 hours of coding knowledge into two hours. Because they ran through dozens of iterations in real time with Claude doing the heavy lifting.

They described what they wanted. They saw the result. They said "actually, make it bigger" or "change the color" or "add a section for testimonials." Each one of those micro-adjustments is an iteration. Each one teaches you something about what you actually want, which is a lesson no amount of passive practice can deliver.

Why This Matters Now

Before AI, iteration was expensive. Every change meant rewriting code, waiting for a build, debugging something that broke. The friction was so high that most people only iterated a handful of times before shipping whatever they had.

Now the cost of iteration is almost zero. You can try something, hate it, throw it away, and try something completely different in the time it used to take to open your code editor. That changes everything.

It means the person who is willing to try 100 versions of something will always beat the person who spent 100 hours perfecting their first attempt. Speed of iteration beats depth of practice. Every time.

The Pause Is the Point

Here is the part most people skip. They build something, it works, and they move on. They never stop to ask: is this actually what I wanted? Does this serve the person I am making it for? What would I change if I could change anything?

That pause between iterations is where all the insight lives. It is the difference between mindless repetition and deliberate creation. You can run through 10,000 iterations and learn nothing if you never stop to reflect on what each one taught you.

The best builders I know treat every iteration like a conversation. They are not just shipping features. They are asking questions. They are listening to what the thing they built is telling them.

What This Looks Like in Practice

Last week I rebuilt the pricing page for Light School. The first version was fine. Clean layout, clear pricing, all the information was there. But something felt off.

So I iterated. I changed the headline. I moved the testimonials above the pricing cards. I tried a version with no pricing cards at all, just a single button. I tried making the whole page a letter instead of a landing page.

None of those changes took more than a few minutes with Claude Code. But by the time I landed on the version that felt right, I had learned more about what I was actually trying to communicate than I would have from a week of staring at the original design.

That is the power of fast iteration. It is not about getting it right the first time. It is about getting it right eventually, and getting there faster than you thought possible.

Forget the Hours

If you are still counting hours, you are playing the old game. The new game is iterations.

How many times did you try? How many versions did you throw away? How many times did you pause, look at what you made, and decide to go in a completely different direction?

That number matters more than any hour count ever will. 10,000 iterations will teach you more than 10,000 hours of grinding ever could.

So stop sharpening the axe. Start swinging it. Look at where it lands. Adjust. Swing again.

The people who iterate fastest will build the future. Everyone else will be reading about it.

Previous The Internet Is Fun Again