Skip to content

About this Episode

Everyone wants a software factory: tickets go in, reviewed and tested code comes out. So how do you actually build one, and where should the human stay? Brendan and Baird walk through the setup they already use on a side project. A recorded planning call becomes a spec, the spec becomes Linear tickets, and Claude Code picks the tickets up. Then they look at what's still missing: automatic pickup, real checks and balances, and a way to run it all without a $145 API bill for a routine task. They agree the code itself can go to the AI. The human still decides what gets built and signs off on how it works. Baird argues for small chunks over one-shot builds, because AI over-engineers and you lose track of what you have. He also makes the case for feeding Granola meeting transcripts straight back into the tickets. The back half covers why you should dogfood what you build ("seven apps, two users"), the idea that you can give up context but not understanding, and how vibe-coded prototypes run into trouble when they go to production because the AI follows your bad patterns without pushing back. Also: context windows that quietly make agents dumber, where the SDLC fits, and the two questions to ask your agent before any PR: "Did we do everything we set out to do? Did we do anything extra?"

Want help building your own factory, or moving a vibe-coded app to production? We're taking consulting work. Drop a comment or DM us.

Sponsor
Powerful podcast hosting & analytics
By podcasters, for podcasters. Since 2016
Brought to you by https://fireside.fm

claudecode #claudeai #aicoding #aiagents

Signup for our newsletter:
https://vibing-with-ai-code.beehiiv.com

Check out our Website
https://vibingwithaicode.com