Solo Builder

The agent reported success. The job “completed.” Then the next step in your pipeline received nothing, and you spent an evening chasing the mystery. Here’s the liberating truth most solo builders don’t reach until it costs them: your agent’s failures are almost never dramatic. They’re mechanical, and mechanical means diagnosable. The bug was one missing closing bracket. The fix was reading one number in a log file. There is no genius in it — and that’s exactly the good news. ...

The simulator said it worked. The phone crashed. That gap, between a green test run and a bricked handset, is where on-device software actually gets built. And it’s a gap almost nobody writes about: the people who survive it are too busy shipping to blog, and the people who blog about “I built an AI voice thing” mostly stopped at the demo that only ever ran in the simulator. This is about the specific, physical reasons the simulator lies, and why shipping on real hardware is a different craft than passing tests. ...

Everyone building on AI now is asking the same question: which model? And it’s the wrong question, because the model is the one part of your stack you don’t own, can’t keep, and will be forced to swap the moment a cheaper one ships. What you can own is everything that wraps around it. The memory. The rules. The decision boundaries. The list of things you’ve already verified and never have to verify again. ...

The agent said the tests pass. The commit is pushed. The deploy finished. As far as the summary in your chat window is concerned, the feature is done. Then you actually click the link and the page is a blank white screen. This is the most expensive sentence a solo builder learns the hard way: “done” is a claim, not a fact. And when your team is a handful of AI agents working through a chat interface, the gap between “claims done” and “is done” stops being an edge case and becomes the whole game. ...

There’s a new job title forming, and it doesn’t exist on any org chart. Fortune named it in March 2026: the supervisor class — developers whose primary value is no longer writing code but orchestrating the agents that write it for them. This isn’t a prediction. It’s already the daily reality for the fastest solo builders. And it changes something more fundamental than how fast you ship. It changes what you are. ...

There’s a moment every solo builder has had: you find a library that does exactly the thing you need, it’s free, it has thousands of stars, and npm install is one keystroke away. It feels like the fastest possible decision you’ll make all week. That moment is the most expensive place to be fast. A dependency isn’t a purchase — it’s a relationship. You don’t pay for it up front; you inherit it. You inherit its bugs, its security posture, its maintenance schedule, and — the part nobody thinks about until it’s too late — its custody problem. When the single maintainer who wrote it walks away, or gets their GitHub account taken over, it doesn’t stop being your code. It becomes your code that you can no longer maintain. ...

The first time an agent blows it, the instinct is to reach for a bigger model. The second time, to “prompt harder.” Both miss the point. An agent that goes wrong is usually not a dumb model. It’s a model you handed the wrong shape to work in. The patterns you choose — how the model routes, what tools it can touch, whether it checks its own work — are what separate an agent that seems smart from one that keeps failing in the same predictable way. ...

The pitch is seductive: describe what you want in plain English, watch the code appear, ship it the same afternoon. For a solo builder, it feels like the thing that finally removes the last barrier between an idea and a shipped product. Here’s the part nobody puts on the landing page: the speed is real, but so is the bill — and it arrives on a different schedule. AI moves fast on day one. Maintenance compounds on day ninety. For a one-person team, there is no “someone else” to hand that bill to. ...

Model Context Protocol won. It’s now “the boring infrastructure layer” — 78% of enterprise AI teams run MCP-backed agents in production, and it just got its biggest update ever, a fully stateless rewrite meant for “really big players” with tens of thousands of agents. So the question a solo builder faces is pointed: if the protocol is the standard, why would I ever write a raw API call myself? The instinct to just grab the API is right more often than the hype suggests. Here’s the rule. ...

Most SEO advice is written for companies with a content team and a year to burn. The indie hacker has neither — you have a Stripe account, a weekend cadence, and a product that needs signups now. So here’s the honest version: the SEO that matters to you is a subset of the SEO that matters to everyone else. You skip the parts that need scale, and you go hard on the parts that need precision. ...