You keep hearing "learn less, do more." But what if learning was always a form of doing?

"Stop reading. Start shipping."

It's one of the most repeated lines in the indie hacker world. And it's half right, which is the most dangerous kind of wrong.

You've been building something. Maybe you've shipped, maybe you haven't yet. Either way, the message follows you everywhere: bias to action, learn by doing, stop overthinking, just ship. You've seen founders who read about startups for years without launching anything. You don't want to become that person.

So you ship fast. You skip the reading. You build first and ask questions later.

Sometimes it works. But often you build the wrong thing entirely. Or, more rarely, the right thing, the wrong way. And you spend twice as long fixing what you could have avoided by spending some time understanding the problem first.

The Binary That Doesn't Exist

People frame "knowing vs. doing" like a choice. Pick one.

But think about what knowing actually requires. You read. You study. You research your market. You analyze what worked for others and why. Each of these takes time, effort, and intention. You don't absorb knowledge by osmosis. Nobody downloads it into your brain. (We haven't built the Matrix yet.)

Acquiring knowledge is an act. It just happens to be an act that doesn't produce a visible artifact, so people dismiss it as the opposite of action.¹

The real question was never "should I know or should I do?" It was always: what is this activity for?

Purpose Is the Variable

A founder who reads 20 books about startups before writing a line of code might be wasting time. Or might be doing the most important work of the project. It depends entirely on why they're reading.

Reading because it feels productive without the risk of shipping? That's avoidance wearing a learning costume. I wrote about that trap before: pattern recognition becoming a comfortable substitute for pattern creation.

Reading because you identified a specific gap, something you need to grasp before you can build well? That's preparation. The axe-sharpening that makes the chopping fast.

Same behavior. Same bookshelf. Completely different purposes.

This is why "just do more" misfires as advice. It treats the symptom (inaction) without diagnosing the cause (unclear purpose). A founder who ships blindly has the same problem as one who studies endlessly. Both are running half a cycle.

What Bridge Engineers Already Know

Before a single beam goes up, a bridge engineer spends months. Studying soil samples. Analyzing wind loads. Running stress calculations. Reviewing material properties. Reading about failures of similar bridges in similar conditions.

Most of the project timeline is this invisible work. Spreadsheets, tables, papers. No steel, no concrete, no visible progress. To anyone watching, it looks like someone staring at numbers.

Often, the actual construction is the shorter phase. The knowing is where the bridge gets built. The doing is where it becomes visible.

Imagine telling a bridge engineer: "Stop studying load tables. Just start building."

The bridge falls down. The stakes make it obvious. Skip the knowing phase and the doing phase produces something that collapses under its own weight.

Yet in the startup world, we say exactly this. "Stop researching. Just build." The stakes are lower, sure. Nobody dies. But the structure is the same. Skip the understanding, and what you build won't hold up.

Know, Build, Know Again

The effective version of "bias to action" is a cycle, not a direction.

Study a problem deeply enough to form a point of view. Build something based on that point of view. The build reveals what the knowledge missed.

Go learn the missing piece. Build again.

Some knowledge only arrives through building. You won't understand your users by reading about them. You have to ship something and watch what happens. The "bias to action" crowd is right about this. The mistake is using it to dismiss the other half entirely.

Every "knowing" phase sharpens the next "doing" phase. Every "doing" phase reveals what the next "knowing" phase needs to focus on.

The cycle breaks when one phase disconnects from the other. Learning that never reaches building is escapism. Building that never incorporates learning is thrashing.

But...

The cycle has a subtler failure mode. You can cycle between knowing and doing efficiently, purposefully, and still build nothing that compounds. Each loop produces a small output. A micro-app. A thread. A prototype. The loop spins, you ship, you learn, you ship again.

A year later, you have fifteen small things and no big thing.

The cycle works when each loop feeds the next one. When what you learned in loop three shapes what you build in loop seven. When it stops being a series of isolated sprints and starts compounding into something with a trajectory.

Which raises a question: what kind of knowing compounds best?

The Knowing You Can't Plan

Earlier I said purpose is the variable. That's true for the knowing/doing cycle within a project. But some of the most valuable knowing arrives without a purpose at all.

You run a logistics operation and spend months learning route optimization, driver scheduling, real-time dispatch under pressure. Then you build a software product and realize the delivery routing problem is structurally identical to user onboarding: both are about sequencing steps to minimize drop-off at each transition.

That pattern didn't come from reading about UX. It came from watching drivers quit routes that had too many awkward turns.

This is the kind of knowing the "just ship it" crowd can't account for. It wasn't gathered as preparation for anything. It was gathered by living a different kind of life, working across different kinds of problems, paying attention in rooms you weren't expected to be in.

And now AI has made this kind of knowing more important, not less.

A prototype that took a week now takes an afternoon. Code that took days appears in minutes. When building is that cheap, a thousand founders can ship the same landing page this week.

The one whose landing page actually converts is the one who knows something the others don't. Who ran a different kind of business before, or studied a completely unrelated field, or spent years paying attention to problems outside the startup bubble.

When the cost of doing drops to near zero, the value of knowing doesn't drop with it. It goes up. The cheaper the build, the more your understanding is what differentiates.

That's compound interest on curiosity. And you can't manufacture it by "biasing to action."

One Question Worth Asking

Before you read that next book, take that next course, or start that next prototype, try one question:

"What will I do differently because of this?"

If you can name the concrete action this knowledge enables, you're inside the cycle. The knowing is feeding the doing.

If you can't, pay attention. It might be genuine exploration, which has its own value. Or it might be avoidance.

Sometimes the answer is obvious. Often it isn't. The ambiguity is worth sitting with rather than resolving with a rule.

What It Actually Looks Like

The "learn less, do more" crowd points at a real failure mode. Knowledge hoarding exists. People do hide in preparation because creation feels risky.

But the fix was never to pick a side.

The best work happens when you can't quite tell which phase you're in. Reading about an unrelated problem gives you the architecture for the thing you're building. Shipping a prototype teaches you something about your users that no research could have surfaced.

The line between preparation and creation stops mattering. The two feed each other faster than you can categorize them.

That's when knowing and doing become the same thing. Not as a philosophical claim, but as something you feel in the work itself.

Rabbit Hole

If this resonated, you might also enjoy:

  1. John Dewey spent decades arguing that separating knowing from doing is both philosophically mistaken and practically harmful. He saw the two as aspects of a single process, a view that remains underappreciated a century later. See Democracy and Education (1916), particularly the chapters on experience and thinking.