Products launching from solo indie hackers who don’t know how to code isn’t rare anymore. It’s the new normal. With this generation of new builders, it means creativity and expertise are no longer bottlenecked by technical skill. That’s a huge win for everyone. But it also means a lot of people are shipping without an operating manual. They’re learning to work with agents on the fly, and it’s not always clear how to do that without stumbling along the way. Growing pains are inevitable, but they don’t have to be as bad as they could be. This post is a field guide for the builders who weren’t builders a year ago. You’re shipping anyway. Here’s a primer on how to get started.
What the agent actually is
An agent isn’t a mind. It’s a very well-read improviser. It has read a mountain of code and conversation, and it’s making its best guess about what you want based on what you wrote and what’s in the room.
That means two things matter more than anything else. What you tell it. And what’s already in the project when you start.
Everything in this post is a variation on that theme.
New to AI terminology? If words like “agent,” “model,” or “context window” feel fuzzy, start with AI Vocabulary 101 to build your foundation.
What the agent actually is
An agent isn't a mind. It's a very well-read improviser. It has read a mountain of code and conversation, and it's making its best guess about what you want based on what you wrote and what's in the room.
That means two things matter more than anything else. What you tell it. And what's already in the project when you start.
Everything in this post is a variation on that theme.
What makes a brief strong?
Click through three versions of the same request and watch the gaps disappear.
The pattern isn't hard. Tell the agent what you're doing, where the work lives, what already exists that it should respect, and how you'll know it worked. That's the whole job.
To be honest, this is also the part that gets skipped most. The excitement of watching something appear on screen is strong. The discipline of briefing well is quieter.
How much to trust it
Trust is where most new builders go wrong, in both directions. Some people don't trust the agent at all and refuse to let it touch anything meaningful. Others trust it completely and wake up to a production incident.
The right answer depends on what's at stake. Move the slider.
Where's your trust dial right now?
Trust is situational. I trust an agent to scaffold a boring form. I don't trust it to handle payment logic without me reading every character. Neither of those positions is wrong. They're responses to different levels of risk.
The skill you're building is knowing which situation you're in.
Five ways it goes sideways
Every new builder I've coached has hit at least three of these. Click one. See if you recognize yourself.
The loop you're actually in
The mental model most new builders start with is one-shot. I ask, it delivers, we move on. The reality is iterative. Here's what good iteration actually looks like.
The blue path is where most of the real work happens. Most new builders try to collapse it, hoping the first output is the last one. It almost never is.
Plan for two or three trips around the loop. Budget for it. Accept it as part of the job instead of as a failure mode.
The pre-ship checklist
Before you push a change an agent made, run through this. Check each one as you go.
Is this ready?
The pattern that works
The builders I see succeed with agents aren’t the ones who prompt cleverly. They’re the ones who treat the agent as a collaborator with specific strengths and specific blind spots, and adjust their own behavior accordingly.
They brief well, stay close to the work, read what gets produced, notice when they’re looping and stop. They ship small, frequent changes instead of big, I-don’t-know-what-I-broke ones.
None of that is technical skill. It’s builder skill. And you already have more of it than you think.
Going deeper
Ready to level up your AI work? Here’s where to go next:
-
AI 102: From Vocabulary to Systems — Understanding prompts, workflows, and tool chaining. The shift from “what should I prompt?” to “what are the steps this task requires?”
-
Momentum vs. Alignment Tax: Hidden Costs in Your LLM Sessions — What looks productive in an AI session often hides a whole layer of alignment work. Learn to spot where your workflow is getting expensive.
-
Your AI Agent Will Eventually Do Something Stupid: A Guide to AI Security 101 — Before you hand your agent the keys to everything, understand what those keys open. Essential reading for anyone building with AI agents.