Every week someone asks the same question in quiet forums and DMs: “I have a job I don’t hate. I want to build my own thing. When do I quit?” There’s a whole genre of content that answers this with a pep talk. Quit the golden handcuffs. Bet on yourself. The money will follow. It’s not wrong. It’s just incomplete — because it only ever shows you the people it worked for. ...
Build the thing, and a certain silence follows. You ship it. You tell a few people. And then — nothing. No users, no feedback, no sign that anyone heard. Most solo builders assume this means the product failed. Usually it means something simpler: you built it, but you never actually distributed it. This is the part nobody writes about, because the people who write about building are good at building, not at the awkward part that comes after. Distribution is not another build skill. It’s a social skill — which is exactly why introverts assume they’re bad at it. They’re not. They’ve just been handed the wrong playbook. ...
The solo-builder conversation is almost entirely about software — code, agents, apps. And every time, the same assumption slips in: that “one person can now ship” only applies to things that compile. That assumption is quietly wrong. The same cost collapse that flattened software shipping is happening on the hardware bench, a few years behind and mostly unnoticed. A single maker with a fifteen-dollar microcontroller, AI-assisted design tools, and on-demand fabrication can now assemble, in a weekend, what once required a team of engineers and a factory. ...
No code vs vibe coding vs real code: the real difference The 2026 building scene offers three overlapping paths, and the internet has opinions about all of them. No-code is “the future” or “a toy.” Vibe coding is “magic” or “a disaster waiting to happen.” Writing real code is “the only serious option” or “a waste of time now.” They’re all being argued about the wrong way, because they’re not rungs on a ladder — they’re three different tools for three different jobs. The real question isn’t “which is best.” It’s “which failure mode can you afford?” Here’s the honest read. ...
A year ago this site was an empty scaffold and a promise. A year of building later, there’s a body of work: things shipped, things broken, things learned. This is the honest ledger of that year — what actually compounded, what quietly didn’t, and the one insight I’d reread on day one if I could. What actually compounded The streak, not the sprint. The single biggest lesson, and the least glamorous. Consistent small sessions beat heroic weekends every time, because the streak keeps the context warm and the weekends keep relearning it. I’d heard this for years. I didn’t believe it until I felt the difference. ...
Until very recently, “solo founder” was a phrase investors said with a wince. It read as couldn’t find a co-founder — a red flag on a term sheet, a polite rejection from an accelerator. Going it alone was the backup plan, not the point. That stigma is now dead, and it didn’t die by argument. It died the way stigmas actually die: the numbers stopped supporting it, and the people closest to the numbers changed their minds. This is the receipts post — the outcomes that are now public, and what they actually prove. ...
Everyone wants the breakthrough — the big launch, the viral hit, the overnight success. And everyone quietly knows that’s not how it works. What actually works is so boring it gets ignored: ship one tiny thing, every single week, without fail. The system doesn’t sound impressive. That’s the point. It’s the unglamorous, compounding engine that separates people who have a body of work from people who want one. Here’s the whole thing. ...
There’s a question every solo builder gets asked constantly, and it’s the wrong one: “which AI coding tool do you use?” The question implies the tool is the bottleneck — that if you just found the right assistant, the work would get easier. It won’t. The tools are roughly equal now, and the gap between them is smaller than the gap between using one well and using ten badly. This post is about the stack I actually settled on, and the part of the story that usually gets skipped: the biggest win wasn’t the tool, it was stopping the search. ...
Ask someone what it costs to build a product solo and they’ll name the visible line items: a coding-tool subscription, an API bill, a domain, maybe a designer. Those are the cheap parts, and they total to less than you think. The expensive parts never show up on an invoice. They’re time, attention, and the quiet load of being the only decision-maker. This is the honest accounting no one gives you before you start — and it matters, because the thing that actually sinks solo projects isn’t running out of money. It’s misreading what the real cost is. ...
The promise of AI building tools keeps inflating: “describe anything, it builds anything.” Every few months someone ships a demo that looks like the software writes itself. Here’s the honest counterweight, from actually shipping with these tools: agents are superhuman at volume and untrustworthy at judgment. They can generate more code, faster, than any team you’ve seen. They cannot decide what’s worth building, what’s actually correct, or what’s good. That last stretch — call it the last 10% — is where the product is won or lost, and it’s still entirely yours. ...