The Support System I Wish I'd Had (And What I Did Instead)
No incubator. No accelerator. No slack channel of peers. Here's what I cobbled together instead — and honestly, it was enough.
Field Notes
Short, honest field notes for anyone building with AI without a tech background. Read one on your lunch break. Come back for the next one when the roller coaster demands it.
No incubator. No accelerator. No slack channel of peers. Here's what I cobbled together instead — and honestly, it was enough.
Every night around midnight the same thought shows up: this is dumb, nobody cares, quit. It's not information. It's just tired.
You have an incredible AI research analyst on call. Use it before you spend three months building the wrong thing.
AI-assisted building is cheap compared to hiring a team. It is not free. Budget like an adult.
AI is the most patient teacher you'll ever meet. But it doesn't read minds. Learn to ask, and doors open.
Most of the people around me don't understand what I'm doing, and probably never will. I had to stop needing them to.
Fifty years old, no coding background, typing into a chat box like it owes me a business. Yeah, it feels ridiculous. Do it anyway.
The AI will occasionally look you in the eye and lie with total conviction. Not to hurt you — it just doesn't know it's wrong. Here's how to catch it.
You can't out-code a 22-year-old engineer. But you can absolutely out-taste them. Here's why the years you've spent noticing things are worth more than you think.
If you're not occasionally wondering what on earth you're doing, you're probably not building anything real yet.
The quiet part of starting something new: there is no team, no cofounder in the next chair, no boss to escalate to. Just you and a blinking cursor.
The project you launch will not be the project you started. Adapt or die is not a threat — it's the entire game.
There is a version of the tech internet that will convince you that what you are doing is not real. Do not visit that internet. Protect your beginner's mind.
You don't need to be an expert. You just need to not do the obviously dumb things. Here's the shortlist of security stuff I now do without thinking.
Wins, fails, and a whole lot of learning. Trust the product; trust the process. Launch day is day one, not day done.
AI is astonishingly smart and confidently wrong at exactly the same time. Verify facts. Test features. Always.
You don't need to be an expert to build. You need to know one problem well enough to smell when a solution is fake.
The term sounds ridiculous. The idea behind it is quietly the biggest shift in who gets to build software since the internet.
I started with no idea what I was doing, one honest conversation with ChatGPT, and one big prompt to Lovable. Turns out that was enough.
The most terrifying and useful thing you can do is show your half-built thing to a real human, out loud, before it's ready. Here's how to survive it.
Social media shows you people shipping. Nobody posts the six-hour bug. Fall in love with the process anyway.
For every feature that ships, there's a graveyard of the ones that didn't. You are allowed — encouraged — to throw things away.
The highs are higher than you think and the lows are lower. Bring snacks.
Some bugs are bugs. Some bugs are the building telling you the foundation is wrong. Here's how I've learned to tell the difference — usually one fix too late.
In vibe coding, the prompt is the product. A vague prompt gets you a vague app. Here's how I stopped writing wishes and started writing instructions.
You are in control — but only of the map. The moment you try to grab the wheel, everything gets weird.
Waiting for a big block of free time to build is a great way to never build. Use the gaps.
The urge to talk about your project is not the same as building it. Save the announcement for something worth announcing.