Why 10k in 30 days

Most build-in-public content I see shows up after the fact. The title is some variant of how I got to 50k. Numbers go up and to the right. The engineering looks linear in retrospect. That's not how it actually goes when you're in it.

I want to do the inverse. Real-time. With no idea if any of it is going to work.

What I'm testing

I write code for a living. I'm decent at it. The interesting question (at least for me) is whether my engineering ability translates to building an audience from zero.

Two pieces of that question. Pick a number. Pick a topic.

The number is 10,000 followers, in 30 days. Hard but not crazy. Some people hit it. Most don't. Round enough that there's no hiding behind a moving goalpost.

The topic is shipping working software, daily, in public. Because if the ability is real, this is the cleanest test of it. Code either runs or it doesn't. The tool either replaces a manual step or it doesn't. The tool is the proof.

How it works

One tool a day. One video a day. The tool I shipped that morning will be used to make the video that afternoon.

By day 30 the entire content pipeline is running on tools that didn't exist on day 1. Every new tool replaces a manual step in producing the next video. By the end, the engineering and the content are the same thing, the way they should be when you're actually building software for a job.

This mirrors how I work in production. Build a thing, ship it, the next thing builds on top. Three months in, you don't recognize your own stack. The compounding is the point.

Why public

I've let too many side projects die quietly. Public work has a way of keeping you accountable.

A daily deadline plus an audience watching is a forcing function. The deadline isn't I'd like to have this done by Friday. It's the thing has to be in 9:00 AM PT tomorrow's reel or there is no reel. That changes how you build. You ruthlessly cut what isn't load-bearing. You write the worst version first. You ship rough.

Working in public also forces honesty about state. If a tool I shipped on day 7 stops working on day 12, everyone sees it. There's no quiet rollback. The bug is part of the story. I'd rather that than a polished case study three months from now where the embarrassing parts have been edited out.

What I'm actually trying to learn

Three things. In order of importance to me, none of them is the follower count.

1. Whether the engineering to content loop holds. The premise of this whole experiment is that good software is good content if you film yourself using it. No talking-head retrospectives. No whiteboard explainers. The thing I build is the demo. I'm betting that holds. 30 days will tell me whether it actually does, or whether I've been romanticizing a pattern that doesn't survive contact with the algorithm.

2. What works at zero. I have no audience. No goodwill. No prior viral moment. So anything that grows from this is mechanically attributable to something I did: a hook that connected, a tool that resonated, a format that spread. By day 30 I'll know what that something is. Or I'll know that none of it works and the platforms genuinely don't reward what I'm making, which is a different kind of useful answer.

3. My own pace. Can I ship a real tool every day for 30 days while also producing a video, while also still doing my actual job? I genuinely don't know. The metric I care about more than 10k is what my Day 30 self looks like, whether I'm walking out of this with a sharper system for shipping creative work, or with burnout that takes a month to recover from.

The 10k number is the visible KPI. These three are the ones I'd actually trade follower counts for.

Why share now (not after)

I have no idea if this works.

Most public-build content gets written from a finished position (here's the framework I followed), which makes it useless to anyone in the messy middle. The interesting part isn't the takeaway. It's the moment-to-moment: which tool decisions paid off, which ones didn't, what the metrics actually do day over day, how it feels when day 11's reel underperforms and the next day's tool is half-built.

If 10k happens, the case study writes itself. If it doesn't, the post-mortem is more useful than yet another success story.

Either way, every tool that ships in the next 30 days is real, freely available, and useful regardless of the follower count. The series is a bet on me. The tools are a bet on the people who use them.

How to follow along

Two places, two formats. Pick whichever fits.

Instagram and TikTok: follow on Instagram or TikTok. Daily reel out around 9 AM EST. ~30 seconds. One tool per day, demonstrated by being used to make the video itself. If you want to watch this happen in real time, this is where it happens.

The email list: link at the bottom of the series page. At the end of 30 days I'll send one email: the case study. Every tool, every metric, what worked, what flopped, what surprised me. If you only want the punchline, the email is enough, you can skip the daily firehose and get the synthesis.

That's the deal. Shipping starts on day 1.