Your Second Agent Is the Hard One
Going from one agent to many does not multiply what you can do. It moves every failure into the space between them.
Technology executive and hands-on architect with 11+ years building and scaling engineering organizations. Three-time company builder with a successful acquisition under the belt.
Technology executive and hands-on architect with 11+ years building and scaling engineering organizations and shipping products to hundreds of thousands of users.
Three-time company builder: grew a 30-person engineering org at AWS, co-founded and sold a blockchain studio via acquisition by Dapper Labs, and took a healthtech startup from napkin sketch to 50K+ users as founding CTO.
Currently Chief Architect at Tarobase (poof.new), building AI-powered tools for vibe-coded dApps. Proven ability to set technical strategy, recruit world-class teams, and raise venture capital.
Going from one agent to many does not multiply what you can do. It moves every failure into the space between them.
You bounded what your agent can touch, gave it an undo button, and taught it when to ask. But when it does something surprising, can you reconstruct exactly why? That is the observability gap.
Full autonomy is the wrong goal. The best agents know exactly when to stop and hand the decision back to you.
You can bound what an agent touches and measure when it fails. Neither one saves you if the mistake it makes cannot be taken back.
A passing test and a working workflow are not the same thing. The gap between them is where production breaks.
Always open to interesting conversations and building things that matter. Based in Washington, DC.