I’ve written nearly 300 short-form scripts. Most of them are mediocre. That’s exactly the point.
Not a single one of them was wasted. Because somewhere around rep 80, I started to see what actually hooks people. Around rep 150, I stopped second-guessing the format. By rep 250, the patterns were so obvious I could feel a bad script before I finished writing it. That sense of judgment — that intuition — didn’t come from reading about content creation. It came from doing enough reps to generate real data.
That’s the volume game.
What it actually means
Volume isn’t about doing random things mindlessly. It’s about removing the bottleneck between you and feedback.
Most people optimize too early. They spend more time planning, researching, and perfecting before the first rep than they’ll ever spend reviewing what they learned after 100 reps. The problem is that you don’t know what to optimize until you’ve seen what the output actually looks like.
Volume is the entry point to quality, not the opposite of it.
The formula is simple: reps + closed loop. Do the thing, see what happens, adjust. Do it again. The loop only runs if you’re running reps. A perfect plan you’ve never executed gives you zero data. 100 imperfect attempts give you everything.
The evidence, from my own numbers
I’m not going to tell you to just “do more reps” without showing you what that looks like in practice.
297 reel scripts. The first 50 were terrible. But I couldn’t have told you why without having written them. Each batch taught me something the previous batch couldn’t — because I didn’t have the comparison point yet. Around rep 100, I started tracking patterns in a log. By rep 200, I had rules I could actually use.
150 PRs merged at EDRA Labs. Zero rollbacks. That track record didn’t come from shipping slowly. It came from shipping often enough that I knew the codebase cold, caught my own mistakes before review, and built a sense of what breaks things. Velocity creates intuition. Caution just delays it.
125 WPM on touch typing. I wasn’t “gifted” at typing. I practiced every day for months. The reps aren’t glamorous — they’re a typing test, a drill, same keys over and over. But somewhere past the point where you stop thinking about where your fingers go, the skill becomes automatic. That threshold only exists on the other side of enough reps.
Every set logged since August 2021. Progressive overload is literally volume science. You don’t get stronger by lifting perfectly once. You get stronger by accumulating enough stimulus over enough weeks that the body has no choice but to adapt. The gym figured this out before productivity Twitter did.
Why most people never play
“Preparing to do the thing isn’t doing the thing. Scheduling time to do the thing isn’t doing the thing. Reading about how to do the thing isn’t doing the thing. The only thing that is doing the thing is doing the thing.”
People avoid volume for one reason: embarrassment is the cost of entry.
Volume means shipping things that aren’t great. It means posting the mediocre script, merging the suboptimal PR, putting up the unpolished project. And most people would rather not show up at all than show up imperfect.
The perfectionism trap sounds like this: “I’ll post when it’s good.” “I’ll ship when I’m ready.” “I’ll start when I know enough.” These are ways of staying comfortable while feeling productive. The planning feels like progress. It isn’t.
The other trap is confusing one domain of knowledge for the skill itself. Reading about how someone else built 10,000 users on an extension is interesting. Building the extension, shipping it, seeing it get picked up by exactly no one, figuring out what was wrong, and iterating — that’s the thing that actually makes you capable of doing it again.
How to run it
The setup is simple, and that’s intentional:
Pick one domain. Commit to a rep count, not a quality bar. “I’ll write 30 scripts this month” beats “I’ll write great scripts this month” every time. A rep count is binary — you either hit it or you don’t. A quality bar is subjective and will always find a reason to delay the next rep.
Make reps visible. I track scripts in a log with date, hook, and what I noticed after. For PRs, I can see the number. For the gym, it’s the logbook. The number matters because it keeps you honest. “I feel like I’ve done a lot” is not data.
Close the loop every 10–20 reps. Volume without review is just noise. Every batch of reps should produce at least one rule, one pattern, one thing you’ll do differently. If it doesn’t, you’re not paying attention. The reps generate the data. The review extracts the signal.
Keep the bar low enough to never miss a day. The goal isn’t one heroic session. It’s compounding. One more rep than yesterday, every day, for a year, beats three intense weeks followed by a month off.
The number doesn’t lie
Here’s what the volume game actually produces over time: skill you can feel, judgment you didn’t have to be taught, and a baseline that makes your floor better than most people’s ceiling.
The people waiting to feel ready are still waiting.
You only improve what you measure.
Maximization over optimization.
The reps are the measurement. Start counting.