--- title: "Practitioner's Corner" canonical: "https://current.tinyfish.ai/issue/26/practitioners-corner" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/26/practitioners-corner" issue: 26 section: "practitioners-corner" description: "Lessons from the field—what we see building at scale" authors: ["Rina Takahashi"] published: 2026-04-27 updated: 2026-04-23 articles: 10 --- # 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 26 — Practitioner's Corner Lessons from the field—what we see building at scale ### The Formalization Problem - [The Legibility Bottleneck]() — By [Rina Takahashi]() · Published 2026-04-23 · Format: The Formalization Problem Meta recently pointed AI agents at a major internal codebase. Of 4,100 files across four repositories, roughly 5% had documentation the agents could actually use. The other 95% worked fine. Engineers maintained it, understood it, kept production running. Nothing was broken. It just wasn't written down in a way machines could read. ### Builder Profile - [What Meta Found When It Sent Agents Into Its Own Codebase]() — By [Rina Takahashi]() · Published 2026-04-23 · Format: Builder Profile Inside one of Meta's data pipelines, two configuration fields refer to the same operation. Use the wrong one and the code compiles clean, passes review, looks correct. It isn't. A human engineer learned this the hard way years ago and told the next person who needed to know. Nobody wrote it down. ### The Unwritten Layer - [The Memory Leak Who Couldn't Be Garbage Collected]() — Published 2026-04-23 *Every large enterprise has one. The person whose phone rings when the documentation runs out. Not the architect, not the manager who signed off on the deployment. The person who remembers why the system actually works the way it does, including the parts nobody wrote down.* ### When Knowledge Leaves - [Meta's AI Infrastructure VP Departs Two Days Before the Company Publishes Its Agent Expertise-Encoding Playbook]() — Published 2026-04-23 Aparna Ramani, Meta's VP of Engineering for AI Infrastructure, announced her departure April 14 after nearly a decade. Two days later, Meta published its Capacity Efficiency agent platform post, describing how senior engineers' expertise gets encoded into composable AI skills for optimization at hyperscale. ### Further Reading - **How Meta Sent 50+ AI Agents to Document What Only Senior Engineers Knew** — [Source]() — Published 2026-04-23 Agents without tribal context produced code that compiled but was subtly wrong. A quiet failure case study worth studying closely. - **Meta's Capacity Agents Have Recovered Hundreds of Megawatts of Power** — [Source]() — Published 2026-04-23 The offense/defense agent architecture here treats reliability engineering as the core function, not an afterthought. Worth reading for the design pattern alone. - **KernelEvolve: Meta Treats Kernel Optimization as a Search Problem Across Hardware** — [Source]() — Published 2026-04-23 Weeks of expert optimization compressed to hours, with 100% correctness across 480 operator-platform configurations. Accepted at ISCA 2026. - **Beyond pass@1: Why Frontier Models Melt Down Most** — [Source]() — Published 2026-04-23 Introduces the first quantitative meltdown detection metric and surfaces a genuine paradox: the models with the highest meltdown rates also show the highest partial completion. The implications for how we measure agent reliability are uncomfortable. - **Why Browser Automation Breaks at Scale: The Concurrency Multiplier** — [Source]() — Published 2026-04-23 A 0.1% timing failure becomes ten guaranteed failures per run at 10,000 sessions. Practitioner breakdown of how edge cases become operational constants. - **Meta's AI Infrastructure VP Departs Mid-Buildout With No Successor Named** — [Source]() — Published 2026-04-23 Aparna Ramani's exit leaves fixed cloud delivery timelines running while institutional knowledge walks out the door. A live example of the tribal knowledge problem at the leadership layer. ## Other sections in Issue 26 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()