--- title: "Practitioner's Corner" canonical: "https://current.tinyfish.ai/issue/33/practitioners-corner" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/33/practitioners-corner" issue: 33 section: "practitioners-corner" description: "Lessons from the field—what we see building at scale" authors: ["Rina Takahashi","Nora Kaplan"] published: 2026-06-15 updated: 2026-06-12 articles: 13 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 33 — Practitioner's Corner Lessons from the field—what we see building at scale ### Builder Profile - [APIs for Websites That Don't Have APIs]() — By [Rina Takahashi]() · Published 2026-06-11 · Format: Builder Profile Suchintan Singh describes Skyvern as building "APIs for websites that don't have APIs." It sounds like a pitch deck line. But the phrase does real work if you've spent years watching ML platforms get measured by marketplace revenue, not model accuracy, and Selenium scripts break every time a frontend developer renames a CSS class. His team built a harder benchmark, scored below 50% on it, and published the results anyway. The architecture and the measurement both point the same direction: web agents are an infrastructure problem that the AI framing keeps obscuring. ### Enforcement Gap - [The Wall That Used to Be There]() — By [Rina Takahashi]() · Published 2026-06-11 · Format: Enforcement Gap An agent running on an 8K-context model that entered a loop used to crash. The window filled, the API errored, the run died. That was an accidental safety mechanism, and it worked. Context windows now stretch past a million tokens, and the accidental wall is gone. A recent multi-agent loop ran for eleven days and $47,000 before a human noticed the billing dashboard. The team had monitoring. They could see it happening. They couldn't stop it programmatically. Watching and stopping, it turns out, require entirely different infrastructure. ### Enforcement Design - [The Crash That Stopped Coming and the Engineer Who Had to Replace It]() — Published 2026-06-11 *Dag Halvorsen is a platform engineer at a mid-size logistics company who, until recently, was sleeping through the night. He spent six years on Kubernetes autoscaling before moving into agent orchestration, a transition he describes as "going from herding cattle to herding cats that occasionally hallucinate." We spoke over video call. A Post-it note stuck to his monitor read "RAN ≠ SUCCEEDED" in red marker. It had clearly been there a while.* ### Compound Failure Math - [The Compound Failure Rate: Why 85% Per-Step Accuracy Means 80% Workflow Failure]() — Published 2026-06-11 P(success) = a^m. Per-step accuracy raised to the number of sequential steps. At 85% accuracy across 10 steps, you land at 19.7% end-to-end success. Bump to 95% per step and a 10-step workflow still only clears 60%. ### Further Reading - **Checkpoints Are Not Durable Execution: Why LangGraph, CrewAI, Google ADK Fall Short** — [Source]() — Published 2026-06-11 Why agent framework save points can't be incrementally improved into durable execution - **AI Agent Token Budget Enforcement** — [Source]() — Published 2026-06-11 A $47,000 runaway loop shows why budget alerts without runtime enforcement are a category error - **AI Agents Burn 50x More Tokens Than Chats** — [Source]() — Published 2026-06-11 Audit of 30 engineering teams revealing a 20x cost spread between developers on the same tools - **State of Agent Engineering (2026 Survey)** — [Source]() — Published 2026-06-11 Primary-source data from 1,300+ practitioners on the observability-without-evals gap in production - **AI Agent Retries and Idempotency: Tool Failure Patterns** — [Source]() — Published 2026-06-11 How standard HTTP retry logic creates duplicate writes in agent tool calls and what fixes it ### Past Articles - [Shuchang Zheng and the Architecture That Notices]() — By [Rina Takahashi]() · Published 2026-06-03 · Format: Builder Profile Skyvern's architecture compiles AI-learned browser workflows into deterministic scripts, then calls the model back only when a script breaks. The rationale is cost and reliability — compiled paths cut token consumption by 57× at scale. But each time the model gets called back, it timestamps something else: an environment event. The website changed enough to break a path that previously worked. Co-founder Shuchang Zheng spent years at Lyft building infrastructure that told engineers when something changed and whether it mattered. His browser automation architecture produces the same kind of signal as a byproduct, pointed at the web rather than the agent. - [Governing the Hypothetical]() — By [Nora Kaplan]() · Published 2026-06-03 · Format: Governance Before Catastrophe Airworthiness rules carry the fingerprints of specific crashes. Banking regulations followed specific crises. The Five Eyes agentic AI guidance and NSA's MCP security advisory, both published in May 2025, have no crashes to study. They govern systems that barely exist in production, and both documents say so plainly — evaluation methods aren't mature enough to certify what's being built. Critical safety decisions, like whether an operation that runs twice produces the same result, are left to implementers. When regulators publish hypotheses instead of prohibitions, the compliance machinery that receives them may not notice the difference. - [Between Complete and Correct]() — By [Rina Takahashi]() · Published 2026-05-28 · Format: Builder Profile An agent asked to add a specific sneaker to a cart navigated Amazon, found a shoe, added it, and reported success. It was the wrong shoe. Every step completed. The task failed. Browser Use co-founders Gregor Zunic and Magnus Müller have made two moves that trace this gap between "complete" and "correct": a migration to raw Chrome DevTools Protocol for real-time browser visibility, and an unsolved problem listed quietly on their hiring page in five words. One reaches for more observation. The other, reproducibility. Neither closes the gap. - [Retries Were Built for a Deterministic World]() — By [Rina Takahashi]() · Published 2026-05-27 · Format: Reliability vs. Correctness A request times out. You send it again. Retry logic is so fundamental to distributed systems that most frameworks ship it by default. It works because the retried operation is identical to the original. Replace the executor with an LLM, and that assumption dissolves. The agent may reason differently on the second attempt, choose different tools, take a different path. Deterministic side effects, produced by a nondeterministic executor. Reliability infrastructure, doing exactly what it was designed to do, starts producing incorrect outcomes. ## Other sections in Issue 33 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()