Parallel Agents Need Ownership Too
Parallel agents only become throughput when each lane has a named owner, a blast radius, and a kill switch. Tabs do not dilute accountability.
Hands-on architect focused on building the platforms where AI agents ship to production. 3x startup builder with an exit; ex-AWS identity and security.
Hands-on architect and engineering leader focused on the platforms and guardrails that let AI agents ship to production.
3x startup builder with an exit: co-founded a development studio acquired by Dapper Labs, rebuilt eddii's HIPAA platform as its first CTO and grew it to 50K+ users, and joined Tarobase's founding team. Before that, AWS identity and security, including the SSO/MFA service Amazon's 1.5M+ employees sign in through.
Currently Chief Architect at Tarobase (OpenApps | Bounded | poof.new), leading the team behind the runtime where AI coding agents build, verify, and deploy production apps.
You debug the agent that produced the bad output. The bug was in the message it got handed.
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.
The most-cited number about AI and jobs is real, and almost everyone repeats it wrong. Here is what the Stanford paper actually found, what its authors refuse to claim, and the one fact in it worth building a hiring plan on.
Always open to interesting conversations and building things that matter. Based in Washington, DC.