On vibecoding products
April 24th, 2026It’s 2026 and AI can write code if only you can tell it what to write. It’s no silver bullet for software development but it is a way to develop programs in a higher level language: English. I’ve been practicing for over a year with the goal of having AI write useful software and I think I’m getting close.
My first few projects were unspectacular. After a while the codebase got too large to fit in a context window and 200-line functions confused the model. My workflow improved, the model improved and the hurdle is gone.
I’m very excited to have figured out how to have AI develop a beautiful and usable UI before implementing database schemas and jumping right in. Before, I relied on a tweak-based workflow:
- tell the AI to do something
- look at what it made (which doesn’t match the product vision)
- propose updates, AI iterates on the already-written code
Now, I’ve inverted the sequence:
- write the idea in Linear
- tell the AI to design the interface
- review the design and propose updates (define the product requirements)
- implementation (matches the product requirements)
This works because defining the product requirements is one the two main human tasks in my workflow1.
I’m building an app (Chatatouille, an app+agent for home cooks; check it out) and found Storybook to be pretty good for allowing me to build interface before logic. This helps accelerate my specification process so the AI builds the right thing, on the first try, every time.
Combining Storybook with the ability to use Linear issues as a human-visible, human-editable memory system lets me ensure tasks are well defined before they’re implemented. Claude must be sick of hearing me ask “is this task well specified enough for us to proceed to implementation?”
Over a decade ago I became a programmer to make software. Apparently, software is built to satisfy product requirements so I switched my career to product management. Man, am I glad I did because it’s now given me the language, mindset and workflows to use AI to build an app I’m already using in my day-to-day life.
I invested two months of development and a year of vibecoding practice to get to this point and it’s exhilarating.
-
The other is QA, which I may write about eventually. My Pareto improvement here has been to explicitly ask the AI to give me a QA test plan. ↩