World's Fair 2026
You Didn't Ship a Bug. You Just Wrote It for a Human. - Ravi Madabhushi, Scalekit
Overview
This talk addresses a critical oversight in agent development: designing infrastructure for human interaction rather than agentic behavior. The core thesis is that many production LLM errors, particularly those related to rate limits, stem from this fundamental mismatch. Infrastructure built for human speed and interaction patterns fails when agents make thousands of calls per second, leading to performance issues and unexpected costs.
Who should watch
- AI Engineers building agentic systems
- Product Managers overseeing LLM-powered features
- Developers encountering rate limit issues or performance bottlenecks with agents
- Anyone designing infrastructure for AI agents
Key takeaways
- A significant portion of production LLM errors, around 60%, are due to rate limits, not model failures or poor prompting.
- Existing infrastructure, including APIs and databases, is often designed with the assumption of human-speed interaction, leading to strain when agents operate at machine speed.
- A simple "last seen" timestamp update on every tool call, intended for human logging, caused database strain when an agent called it sixty times per second.
- Rate limits often fail to distinguish between legitimate high-volume agent needs and agents stuck in loops.
- Treating agents as first-class principals, distinct from fast humans, requires rethinking infrastructure design from the ground up.
- Designing for agentic behavior from the start is crucial to avoid costly production issues.
Notable quotes
*A rate limit can't tell the difference between an agent that legitimately needs 100 calls and an agent that is just looping.*
*We had built infrastructure to show customers how to connect agents to their tools. We hadn't noticed we'd built it for humans.*
Unofficial community note. Prefer the recording for nuance.