Guides on software and AI.
Written by the people doing the work: when vibe coding is enough, how to brief an AI coding tool, why an MVP gets harder to change, and how a launch actually runs.
· 7 min read
Vibe coding or hire a developer: which does your idea actually need?
AI coding tools are genuinely good enough for some products and genuinely dangerous for others. An honest framework for telling which one you have, before you spend the money.
· 6 min read
Why your MVP got harder to change in week four
Three weeks of astonishing progress, then everything takes a day. The cause is almost always the same, it is visible from the outside, and it is fixable before it compounds.
· 6 min read
How to brief an AI coding tool so the code survives real users
Prompts get you what you asked for, which is rarely what you needed. Four things to state up front that cost nothing now and are expensive to add later.
· 8 min read
From vibe-coded prototype to production: what actually has to change
AI coding tools will get you a working prototype in a weekend. Here is the honest list of what stands between that and something you can sell, and what each item costs.
· 7 min read
One brief, six disciplines: how a launch actually runs
What changes when the people building the prototype, the product and the pipeline sit in one team. A walk through a launch, week by week.
· 6 min read
Assistants that earn their keep
Most AI pilots die in the demo. The ones that survive start from a task that costs hours, not from a model. Here is how we choose that task.
· 5 min read
Monitoring a client can read
The dashboard we hand over after launch, what is on it, and why error counts and uptime charts are not on the first screen.