You Can Ship Something This Weekend

There are two kinds of people who say they want to build things. One kind has a folder of half-finished projects. The other kind has an idea they have been refining for eight months.

The first kind is doing better, and it is not close.

A big idea has a hundred decisions in it, and every decision is a place to stop. You cannot start the app until you pick the framework, cannot pick the framework until you know the data model, cannot know the data model until you decide what it does, and what it does keeps growing because it is all imaginary and imaginary things cost nothing to add.

A small idea has four decisions. You make them badly on Saturday morning and by Sunday night the thing exists.

The finished small thing teaches you more than the unfinished large thing, because only the finished one hits reality.

Here is the whole method.

Pick something that annoys you personally. Not a market, not an audience, an annoyance you have had in the last month. You are the user, which means you never have to guess what it should do.

Write down what it does in one sentence. If the sentence has an and in it, cut the second half.

Now remove everything. No accounts. No settings. No password reset. No dark mode. No admin panel. No database if a file will do. Every one of those is a weekend by itself and none of them is the thing.

Build the version that works for exactly one person. You.

Saturday morning: make the ugliest version that technically functions. No styling. Black text on white. It should work and look terrible by lunch.

Saturday afternoon: use it. Actually use it for the real annoyance. Half of what you planned turns out to be unnecessary and one thing you never considered turns out to be essential. This is the part that only happens after you build, which is why planning cannot replace it.

Sunday: make it presentable and put it online. Free hosting tiers are genuinely free for something this size. A public link is what turns a folder into a project.

AI coding assistants have removed most of the setup tax, and there is no prize for refusing them. Let one write the boilerplate, the configuration and the parts you do not want to learn today.

Read what it produces. The point is to finish, but the person who never reads the generated code stops being able to fix it, and the fixing is the skill.

“Planning feels like progress and produces none. Shipping feels like exposure and produces everything.”

Four small finished things say more about you than one large unfinished thing. They say you finish, and finishing is the rarest trait in this field.

Put them somewhere public. A repository is the version of a resume that cannot be exaggerated.

And if you are building toward a job rather than a company, the security ladder rewards exactly this kind of evidence.

What annoyed you this week that a computer should have handled. That is the project. Start Saturday.