All advice

Make agent code pass rules, not your mood

Vlad
Vlad

Backend engineer turned indie hacker

Vlad's guardrails slide put five gates between an agent and the main branch: lint, static analysis, import rules, tests, and a verifier on the pull request. He called them rules that do not have opinions. Reviewing agent output by reading it and deciding how you feel does not scale past a few changes a day. Deterministic checks do. Write down what a good change must satisfy, make the machine check it, keep the verifier out of the agent's reach, and spend your own attention on the changes that fail.

Related advice

Product·Vlad Vlad

Sell the children's clip to the parent

The room treated the children's clip as a product with a buyer, a moment, and a rule. The buyer is the parent. The moment is bedtime or mealtime. The rule is what the model may draw. Vlad's buyers are one-off and quiet, so a form with a reason to answer is how he learns why they came. A picture book can survive a rough line. A frame that is wrong for a child has to be blocked before it renders. Pick those three, then teach the pipeline to follow a timeline.

Product·Vlad Vlad

Define a role as context, tools, and verification

Vlad defines an agent's role with three things: the context it needs to know, the tools it can touch, and the verification that proves it did the job right. His own team works this way. One agent coordinates, one writes and ships code, one clicks through production like a user. Most people set up the first two and skip the third, which is how an agent ends up confidently wrong. Before you add a bot, write one line for each of the three. If you cannot say how you would check its work, it is not a role yet.

Mindset·Vlad Vlad

Stop polishing code, start finding customers

As an engineer, your instinct is to keep improving the product. Resist it. A mediocre product with great distribution will outperform a great product with no distribution every single time. Vlad spent months polishing sisif.ai before realizing that nobody knew it existed. The hardest shift for technical founders is accepting that code quality doesn't drive revenue.

Mindset·Vlad Vlad

Twitter and ProductHunt are slow for unknown founders

Building in public, Twitter threads, and ProductHunt launches all share the same assumption: someone is already listening. If you have 12 followers, tweeting into the void won't generate customers. Vlad tried the standard playbook for months and got nothing. These channels compound over time, but if you need traction now, you need to go where attention already exists.