--- title: "Foundations" canonical: "https://current.tinyfish.ai/issue/16/foundations" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/16/foundations" issue: 16 section: "foundations" description: "Conceptual clarity earned from building at scale" authors: ["Rina Takahashi"] published: 2026-02-16 updated: 2026-02-12 articles: 11 --- # 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 16 — Foundations Conceptual clarity earned from building at scale ### What Building Teaches Builders - [When Agents Can't Find What's Right in Front of Them]() — By [Rina Takahashi]() · Published 2026-02-11 · Format: Field Guide A web scraper pulls product prices from a retail site every morning. One day it returns empty results. The prices are still there, displayed correctly on the page—customers see them, competitors see them. But the agent can't find them. Teams spend days checking pipelines and validating formats. Something broke, something most debugging approaches miss entirely. ### Tools & Techniques - [Headless Browsers at Scale: Where Speed Determines Economics]() — By [Rina Takahashi]() · Published 2026-02-11 · Format: Tools in Context The infrastructure lead switches 10,000 daily hotel price checks from headful to headless browsers. Monthly bill: $4,500 to $1,500. Tasks complete 2-15x faster. Same server handles three times the concurrent sessions. For teams running automation at volume, headless execution determines how many servers you need and what they cost. Then anti-bot systems evolve to catch the missing rendering pipeline, the absent plugins, the suspicious timing patterns. Engineering around detection becomes its own cost, one that sometimes exceeds the infrastructure savings. - [When Headful Browsers Justify Their Resource Overhead]() — By [Rina Takahashi]() · Published 2026-02-11 · Format: Tools in Context The pricing monitoring system ran cleanly for three months—15,000 hotel properties checked daily, data flowing into automated pricing decisions. Then Booking.com updated their anti-bot system. Success rate dropped from 94% to 31% within 48 hours. Missing pricing data meant stale dashboards. Stale dashboards meant the system underpriced 400 properties based on weekend rates that were four days old. The revenue team calculated the loss. The cost of being wrong exceeded the cost of running more expensive infrastructure by a factor of eight. ### Pattern Recognition - [Platform Vendors Launch Before Production Proves Out]() — Published 2026-02-11 Three major vendors launched agent management platforms in February 2026. OpenAI released Frontier on February 5. Salesforce expanded Agentforce throughout January and February. AWS grew Bedrock AgentCore. Gartner called these platforms "the most valuable real estate in AI." ### Questions Worth Asking Most teams pick tools based on demos that showcase perfect scenarios. Then production arrives with its corrupted files, peak-hour spikes, and users who do things no one anticipated. We've seen this pattern repeatedly. The system that looked solid in the vendor presentation becomes the thing demanding constant attention once real load hits. The gap between demo and deployment is where expensive mistakes live. These questions surface what matters when systems scale. They distinguish tools that fade into infrastructure from those that become operational burdens. Ask them before you're locked in. - **Does It Handle Corrupted Files?** — [Source]() — Published 2026-02-11 Tag: Production Reality Demos use clean inputs. Production delivers corrupted PDFs, malformed JSON, and queries that make no sense. The tool that chokes on the first weird file isn't a tool. It's a liability waiting to page you at 2 AM. - **Can It Run 10,000 Tests Simultaneously?** — [Source]() — Published 2026-02-11 Tag: Parallel Execution Sequential testing is a luxury production can't afford. You need parallel execution across distributed resources, not a queue that takes hours. If the tool can't shard tests and run them concurrently, you're building a bottleneck into your pipeline. - **Does QA Actually Match Production?** — [Source]() — Published 2026-02-11 Tag: Environmental Parity Code that works in staging and fails in production is expensive. Not just frustrating. Your QA environment needs the same hardware, network topology, and configuration drift that production has. Otherwise you're testing a fantasy version of your system. - **Are Integrations Native or Duct-Taped?** — [Source]() — Published 2026-02-11 Tag: Integration Depth Bolted-on integrations break. Native ones fade into infrastructure. Check whether the tool connects to your actual systems—GitHub, Datadog, PagerDuty—without custom glue code. If you're writing adapters, you're maintaining two systems instead of one. - **How Fast Can You Undo This?** — [Source]() — Published 2026-02-11 Tag: Rollback Capability Rollback sounds simple until you try it with database migrations and dependent services. The tool should make reverting trivial, not a multi-step procedure requiring three teams. If rollback takes longer than the deploy, something's wrong with your architecture. - **Will This Company Survive Your Contract?** — [Source]() — Published 2026-02-11 Tag: Vendor Viability Tool selection is a three-year bet minimum. Check how long they've existed, whether they're actively shipping updates, and if their business model makes sense. Migrating off a dead vendor is worse than choosing wrong in the first place. ### In Dialogue With Complexity - [An Interview with the Acceleration Curve That Judges Your Humanity]() — Published 2026-02-11 We're sitting in what I can only describe as a visualization lab. Walls covered in projected trajectories, each one a ghost of cursor movement past. Some flow like water. Others snap corner to corner like they're being drawn with a ruler. ## Other sections in Issue 16 - [Daily Brief]() - [Market Pulse]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()