blog
Where is the low hanging fruit with AI? - Start with the boring work. Not the clever work. The work that is done the same way every time, because that is where you can tell whether it was done right.
vibe2value
blog
An AI agent charges you per answer and never says whether the answer was any good - Telemetry records the cost, the template, the model and the latency. It does not record whether the answer was any good, and that half has to be built by hand.
blog
The cheapest way to build an AI agent is the most expensive way to run one - The option that feels like progress in week one is the one still charging you in week fifty. An agent has to keep its policy somewhere. There are three obvious places to put it.
blog
Your next vibeCode starts where the last one finished - The first vibeCode is rough. It is also the worst it will ever be. What the next one is worth depends entirely on what you rebase it onto.
blog
A Wednesday check-in to make your vibe have more value - A ten minute check before you vibeCode something or hand it to an AI: is this the best return on the effort and does it already exist?
launch
3.3.3 - Are You Comfortable Putting Your Name on This Build? - Set the ownership threshold: say what is still imperfect, what would happen if it failed and why shipping is still acceptable under those conditions.
launch
3.3.2 - Name the Risks Yourself Before Users Find Them in Production - Name the launch risk: say what might break, what would trigger it and what response reduces the damage.
launch
3.3.1 - What "Ready" Actually Means Once Real Users Are Looking - Define the readiness rule: say what has to be true, how it will be checked and who owns any remaining risk.
launch
3.2.3 - Iteration Should Increase Value, Not Just Add Surface Area - Check the iteration value test: say what changed, what user outcome it is meant to improve and what signal will show that it did.
launch
3.2.2 - Explain Your Decisions Before Asking for Review - Explain the review context: say what was decided, what trade-off it created and what question you want reviewers to answer.
launch
3.2.1 - The Difference Between Learning and Being Stuck - Name the learning signal: say what question is being answered, what signal will answer it and what decision comes next.
launch
3.1.3 - Decide in Advance What Would Change Your Mind - Set the decision threshold: say what evidence will trigger change, where it will come from and what action follows.