← all posts

2 Mar 2026

On shipping things alone

People hear "solo developer" and quietly file it under compromise. No designer, so the design must be rough. No backend team, so the backend must be fragile. No QA, so the bugs must be everywhere. I get why people assume that. I just think it's mostly wrong.

On paper a team is faster, sure. More hands, more hours, work happening in parallel. Put a good team up against me on a spec sheet and they win every time, no contest.

But specs aren't usually what kill projects. Handoffs are. The design that ends up looking nothing like the thing that got built. The API that returns a shape the app never expected. The server everyone quietly assumed someone else was watching. Every seam between two people is a place the work can fall through, and big projects have a lot of seams in them.

When it's one person, there just aren't any. The design lives in the same head as the code that implements it. The API gets shaped by the same person who has to go consume it later. Nobody's waiting on anybody else. The whole product fits inside one mind at once, and that ends up being worth a surprising amount.

Not romanticizing it, though. Doing everything alone has a real cost. You're the bottleneck, by definition. Nobody's around to catch the blind spot you can't see yourself, nobody to tell you an idea is bad before you've already built it. When you're stuck, you're just stuck, and the only person who can unstick you is the same tired one still sitting at the keyboard.

And it doesn't scale forever, either. Eventually a project gets big enough that one person becomes the actual constraint, and then you need other people, and you're back to managing seams on purpose because the alternative is worse. I know that much. I'm not out here trying to do fifty engineers' worth of work by myself.

But for the part I actually care about (taking something from nothing to live, used by real people, with no committee deciding what gets built), doing it alone is underrated. Not despite being one person. Because of it.

Most of what's on this site got made this exact way. One person, start to finish. Slower than it sounds, and somehow faster than you'd think.