I Ran a Manager-Worker Agent Team on Real Work. A Single Session Beats It.
I ran a manager-worker agent team on 67 real tasks. A single session would have done the work better. The failure modes are structural.
Your team uses AI tools. I'll show them how to ship with them.
I'm a senior systems engineer who builds and ships production code with AI tools daily.
Public work that demonstrates the practice. Click through to verify directly.
Backend engineer with 10+ years shipping production systems across fintech, security, blockchain, and developer tooling.
Currently building AI execution infrastructure: LLM orchestration, MCP, multi-agent systems, and evaluation tooling.
Known for owning ambiguous systems end-to-end, from architecture through operations.
9+ years developing production systems in Go and Python, with specialized expertise in Solidity for blockchain applications.
4+ years architecting blockchain systems from smart contracts to full-stack dApps, with deep expertise in multiple networks and protocols.
Specialized in production AI systems, from LLM orchestration to multi-agent frameworks, with focus on practical business applications.
I ran a manager-worker agent team on 67 real tasks. A single session would have done the work better. The failure modes are structural.
Agent memory should be files in git, next to the work they describe, not rows in a vendor database.
A gate an agent waves itself through is not a gate. Quality gates for agent work have to be decisions against artifacts.
Most scaling problems have a 2-week solution and a 6-month solution. Let's find yours.
No sales calls. Just an engineer who gets it.