Make Bad Art

There is a particular kind of paralysis that strikes people who care about quality. They sit down to write, to code, to design, to build — and they freeze. Not because they lack ideas, but because the ideas aren't good enough. Not yet. Not polished. Not worthy of being seen.

So they wait. They research more. They outline. They plan. They consume another course, read another book, watch another tutorial. They sharpen the axe until there's no axe left.

And they never swing.

I've done this. You've probably done this too. It's a seductive trap because it feels productive. Planning feels like progress. Perfectionism disguises itself as high standards. But it's not high standards. It's fear wearing a nice suit.

The antidote is counterintuitive: make bad art.

The Pottery Experiment

There's a famous story — originally from the book Art & Fear by David Bayles and Ted Orland — about a ceramics teacher who tried an experiment with his class.

He split the students into two groups.

Group A was graded on quantity. On the last day of the semester, the teacher would weigh all the pots they'd made. Fifty pounds of pots earned an A. Forty pounds a B. Thirty a C. It didn't matter if the pots were ugly, lopsided, or barely functional. Just make pots. Lots of them.

Group B was graded on quality. They only had to produce a single pot. One. But it had to be perfect. The most flawless, beautiful, exquisitely crafted pot they could manage. They had the entire semester to work on it.

You already know what happened.

At the end of the semester, the best pots — the most technically skilled, the most beautiful, the most creative — all came from Group A. The quantity group.

While Group B sat around theorizing about the perfect pot, conceptualizing ideal forms, and second-guessing their glazing technique, Group A was busy. They made pot after pot after pot. They failed early. They failed often. They learned what worked by discovering what didn't. Each pot was a little better than the last. By the time they'd churned through dozens of attempts, they had actually learned the craft.

Group B, with all their planning and theorizing, had tried to think their way to mastery. They had one pot to show for it. And it was mediocre.

Why Volume Beats Perfection

This isn't just a cute parable. There's a deep mechanism at work here, and it applies to everything — writing, coding, designing, investing, building companies.

1. You don't know what good looks like until you've made enough bad.

Your taste develops faster than your skill. This is Ira Glass's famous insight: there's a gap between your taste and your ability. You can feel that your work isn't great, but you can't fix what you haven't made. The only way to close the gap is to produce a volume of work. The gap closes through reps, not reflection.

2. Feedback requires a finished thing.

A half-built project teaches you nothing. A shipped project — even a terrible one — teaches you everything. You learn what breaks. You learn what users actually care about. You learn where your assumptions were wrong. But you only learn this if you finish and release. The world can't give you feedback on something that lives in your head.

3. Perfectionism is procrastination with better branding.

Let's be honest about what's happening when you refuse to ship until it's perfect. You're not optimizing. You're hiding. Shipping means exposing your work to judgment. Not shipping means staying safe. Perfectionism is the most socially acceptable form of cowardice because it sounds like you just have high standards.

4. Iteration beats planning.

The best version of anything is version 10, not version 1. But you can't get to version 10 without shipping version 1. The companies that win aren't the ones with the best plan. They're the ones that executed a decent plan, got feedback, and adapted faster than everyone else.

The Builder's Trap

I see this constantly in the tech world. Someone wants to build an app. They spend three months picking the perfect tech stack. They design the database schema to handle a million users before they have one. They set up CI/CD, linting, monitoring, observability — the full production infrastructure for something that doesn't exist yet.

Then they lose motivation and move on.

Meanwhile, someone else hacks together a working prototype in a weekend using whatever tools they already know. It's ugly. The code is a mess. It doesn't scale. But it works. People can use it. And from that ugly, imperfect, embarrassing first version, they learn what to build next.

This is what Paul Graham means when he says "do things that don't scale." The point isn't to build something scalable. The point is to build something real. Scalability is a problem you solve later — if you're lucky enough to need it.

The same applies to writing. The writer who publishes a mediocre blog post every week will be a better writer in a year than the one who spent that year drafting the perfect essay they never published. The musician who records a rough track every day will outgrow the one who spent months mixing a single song.

Volume is the teacher. Not theory. Not planning. Not inspiration. Volume.

The Paradox of Quality

Here's what makes this counterintuitive: the path to quality runs through quantity.

You'd think the person obsessing over quality would produce better work. But they don't. Because quality isn't something you can think your way into. It's something you develop through the physical act of making things.

Every potter in Group A got their hands dirty. They felt the clay resist. They watched pots crack in the kiln and asked why. They tried a different technique the next day. Their fingers developed memory. Their eyes learned to see imperfections before they happened. This embodied knowledge — the kind you can only get from doing — is what separates someone who knows about pottery from someone who knows pottery.

The Group B students understood pottery intellectually. The Group A students understood it in their bones.

This distinction matters in every creative field. You can read every book about writing and still not be able to write a clear paragraph. You can study every design principle and still produce mediocre interfaces. Knowledge about a craft is not the same as knowledge of a craft. The difference is reps.

What Bad Art Actually Looks Like

Making bad art doesn't mean being careless. It means being willing to be bad as a stepping stone to being good. There's a difference.

Bad art with intention looks like:

• Writing a blog post you know isn't your best work, but publishing it anyway because the act of finishing matters more than the result
• Shipping a feature with rough edges because users need it now and you can polish it later
• Recording a podcast episode that's awkward and unpolished because episode 50 will be great and you need to get through episodes 1 through 49 first
• Launching a product that only does one thing, badly, because you need to learn if anyone wants it before you build the rest

Bad art without intention looks like:

• Not caring about improvement
• Refusing to learn from mistakes
• Shipping the same low quality repeatedly without reflection

The difference is trajectory. Bad art with intention gets better. Each piece is a data point. You're running experiments, not just producing garbage. The quantity approach works because each repetition is a learning opportunity — but only if you're paying attention.

The Compound Effect of Shipping

There's a compounding dynamic here that most people miss.

When you ship frequently, you don't just get better at the craft. You build an audience. You build a reputation for consistency. You build confidence. You develop taste faster because you're getting more feedback. You discover adjacent opportunities you never would have found if you were still planning.

One published blog post leads to a conversation that leads to an idea that leads to a project that leads to a career pivot. But only if you published that first post. The one that wasn't good enough.

Naval Ravikant talks about specific knowledge — the kind you develop by following your curiosity and doing the work only you can do. You can't develop specific knowledge by theorizing. You develop it by doing the work, repeatedly, in public. Each piece of bad art is a step toward finding the thing that only you can make.

Permission to Be Bad

Here's what I want you to take away from this.

You do not need to be good yet. You do not need to have it figured out. You do not need to wait until you've read enough, learned enough, or planned enough. You will never feel ready. Readiness is a myth sold to people who are afraid of starting.

The ceramics students who made the best pots didn't start by being good at making pots. They started by making terrible pots. Lots of them. And the terrible pots weren't wasted effort — they were the entire curriculum.

Your first blog post will be bad. Your first app will be buggy. Your first video will be awkward. Your first business will probably fail. This isn't a prediction of defeat. It's a description of the process. Every master was once a disaster. The difference between the master and the person who quit is that the master kept making pots.

Start Today

If you've been sitting on an idea — a project, a blog, a product, a creative endeavor — and you've been waiting until you're ready, until the timing is right, until you know enough, until you have the perfect plan:

Stop waiting. Make the bad version. Ship it. Learn from it. Make the next one.

The semester is already running. The question isn't whether your pot will be perfect. The question is whether you'll have made enough pots by the end to have actually learned something.

Make bad art. Make lots of it. The good art is hiding on the other side.