--- title: "Practitioner's Corner" canonical: "https://current.tinyfish.ai/issue/2/practitioners-corner" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/2/practitioners-corner" issue: 2 section: "practitioners-corner" description: "Lessons from the field—what we see building at scale" authors: ["Rina Takahashi"] published: 2025-11-05 updated: 2025-11-07 articles: 12 --- # 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 2 — Practitioner's Corner Lessons from the field—what we see building at scale ### Dispatches from Production Scale - [One Price Every 36 Seconds]() — By [Rina Takahashi]() · Published 2025-11-04 · Format: Operations Field Notes There's still someone at most companies checking competitor prices manually—open tab, copy number, paste into spreadsheet, repeat. One price every 36 seconds if they're fast and the sites cooperate. Building web automation makes you realize why this person hasn't been replaced yet: the web fights systematic monitoring at every turn. CAPTCHAs, authentication labyrinths, sites that redesign overnight. What looks simple—"just check the website"—turns into infrastructure problems most teams don't see coming. - [The Work That Never Started]() — By [Rina Takahashi]() · Published 2025-11-07 A pricing team wanted to understand their competitive position. Simple question. The answer required checking 50,000 product pages daily. At 30 seconds per page, that's 417 hours of work. Every single day. They never tried. The work remained undone because it couldn't be scoped. Not expensive—impossible to resource. The information existed. The questions mattered. But certain work hits a threshold where the economics break completely, and companies stop attempting tasks they know would matter. - [The Numbers That Don't Exist]() — By [Rina Takahashi]() · Published 2025-11-07 A pricing team wanted to understand their competitive position across their catalog. Reasonable question. The answer required checking 50,000 product pages daily. At 30 seconds per page—if you could somehow maintain that pace without breaks—that's 417 hours of work. Every single day. They never tried. The work remained undone because it couldn't be scoped. ### Mapping the Invisible Web - [When the Website Isn't in the HTML]() — By [Rina Takahashi]() · Published 2025-11-04 · Format: Field Dispatch Been watching this pattern repeat: someone needs to extract pricing data from a site, opens view source expecting to see the prices, finds nothing but script tags and empty divs. Then they look at what's actually rendering in the browser—full tables, interactive elements, everything—and realize the website isn't in the HTML anymore. It's assembled on-the-fly by JavaScript pulling from APIs. The weather's turning on this: we're drifting from "web as documents" to "web as runtime environment." ### Theory Meets Production Reality - [When the Tenth Session Breaks Everything]() — By [Rina Takahashi]() · Published 2025-11-04 · Format: Parallax View Keep seeing the same pattern: pilot runs at ten sessions, someone asks about scaling to a hundred, system just stops. Not gradually—it stops. Same code, same logic. The infrastructure gaps were always there, but pilot conditions never exposed them. Cascades that couldn't happen at low volume. Rate limits you never hit. Session management that worked fine until it didn't. This piece walks through what breaks and why those failures were inevitable. Second piece covers the other side—the manual work keeping pilots alive that nobody tracks. - [The Three Hours Nobody Saw]() — By [Rina Takahashi]() · Published 2025-11-04 · Format: Parallax View Saw a pilot where someone cleaned data three hours every morning before automation ran. Demo never showed those hours. Pilot succeeded partly because that person existed. Edge cases that show up once in test data appear a hundred times daily at production scale. Manual oversight that's feasible for ten sessions becomes impossible for thousands. This examines what pilots hide—not infrastructure that breaks under load, but human dependencies that can't scale. Pairs with the technical failures piece because both reveal why pilot success masks what production actually demands. ### The Number That Matters - [13 Trillion Bot Requests Blocked in One Year]() — Published 2025-11-04 Imperva's network blocked 13 trillion malicious bot requests in 2024. Trillion with a T. Do the arithmetic: 35.6 billion requests per day, 413 million per hour, 6.9 million requests every single minute, all year long. ### Field Notes from the Ecosystem October delivered three Azure outages in thirty days. Same platform, different failure modes, millions affected each time. Cloudflare processed 100 million bot challenges without a breach. Scrapers still get caught reading 300 pages per minute. Shared token buckets look elegant in architecture diagrams. In production, they become single points of failure. Stealth mode plugins promise invisibility but leave HTTP/2 fingerprints. These patterns only surface when systems hit scale. - **100 Million Challenges, Zero Breaches** — [Source]() — Published 2025-11-04 Tag: Bot Detection Troy Hunt deployed Cloudflare Turnstile five months back. 100 million challenges processed. Not a single abnormal traffic spike to his unified search endpoint. Turnstile runs non-interactive JavaScript challenges: proof-of-work, proof-of-space, browser quirk detection. Difficulty adjusts per request. No visual puzzles required. - **One Health Check Kills Everything** — [Source]() — Published 2025-11-04 Tag: Rate Limiting AWS API Gateway default: 10,000 requests per second, shared across all APIs in your region. One user floods a single health check endpoint, exhausts your entire quota. No per-method isolation. One careless endpoint configuration becomes an account-wide vulnerability. - **Azure's Three-Outage October** — [Source]() — Published 2025-11-04 Tag: Infrastructure Reliability Microsoft's October 29 Front Door outage ran 12+ hours, affected millions. Third Azure incident that month. October 9: Front Door issues across four continents. Same day: Azure Portal hit 45% of customers. Pattern recognition matters when evaluating cloud provider stability claims. - **300 Pages in 60 Seconds** — [Source]() — Published 2025-11-04 Tag: Scraper Detection No human reads 300 product pages per minute. Scrapers do. Modern detection keys on this arithmetic impossibility: request velocity that defies human physiology. Most sites cap at 10-20 requests per minute. Exceed it: throttled, challenged, or banned outright. - **HTTP/2 Fingerprints Bypass Stealth Mode** — [Source]() — Published 2025-11-04 Tag: Browser Fingerprinting Cloudflare maintains a whitelist of HTTP/2 fingerprint and User Agent pairs. Each client request generates a static fingerprint. Playwright's stealth mode masks navigator.webdriver flags but leaves protocol-level signatures exposed. Fingerprint-agent mismatch triggers blocks even when surface indicators look clean. ## Other sections in Issue 2 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()