Share Episode

We welcome David Burns, Head of Open Source at BrowserStack and previously Mozilla, this week to help explain how can browser and mobile app testing be so bad still in 2026. "Even if we had to do it all over again, we probably still wouldn't have gotten it right", might just be the biggest learning. We review some of the core challenges that cause even the most experienced web engineers pain and how some companies are attempting to avoid them.

We also review shares lessons from Mozilla’s 'War on Orange,' demonstrating why chasing a 100% green CI suite at scale is a fool's errand, and why engineering teams must instead manage delta tolerances and adhere to a strict testing pyramid. Additionally, we investigate the physical hardware nightmares of running 30,000 real phones in data centers; from battery swelling and custom Faraday cages to complying with Apple EULA requirements using racks of Mac Minis. And finally, we discuss WebMCP, Project Fugu, and why LLM browser agents still struggle against edge-case browser behaviors like the Back-Forward Cache (BF Cache).

• ✨ Episode: Sam Goto — Security challenges in the Browser World
• ✨ Episode: Actually think about how are your users use your tools
• Mozilla CI - Tree Herder
• The Worst UX site with a perfect 100
• Project Fugu Browser initiative
• WebMCP Project Specification

• Warren - Paper — The Corporate Bullshit Receptivity Scale
• David - Anbernic Retro Handheld Game Console

Share Episode

From your feedback, we know that on-call issues, especially those that arise at the database layer are always the most challenging to solve. This episode builds on our Grafana Observability episode as we go deeper into the challenge of data ownership in data lakes. Apache Druid creator, previous Yahoo Distinguished Engineer, Fellow at Splunk, and currently the Chief Architect as Imply, Eric Tschetter joins us to confirm that there are unsolved problems in data platforms, and it doesn't get better when we throw agents into the mix.

In the true DevOps mindset aligment, Eric reminds us that whoever is operating the system, knows what is going on, they know their service boundaries, and so it's their choice to make. And the sad reality is that at large enough companies, you will always have independent teams making independent decisions, it's never possible to fully align them, and realistically we get down to why it is even a mistake to try.

• ✨ Episode: Grafana — Observability
• ✨ Episode: AST can run anything
• Book: Lean Manufacturing — The Toyota Way
• Monkeys typing the Complete Works of Shakespeare
• Paper: Ironies of Automation (& AI)
• Jeff Bezos API Rant — 2011
• Book: The Formula, Science Success
• Show: Burn Notice

• Warren - The Agency
• Eric - 継続は力なり — keizoku wa chikara nari

Share Episode

Sauce Labs CTO Anoop Tripathi addresses the root causes of broken test suites and why teams frequently become numb to intermittent test failures. Anoop shares concrete lessons from his career, detailing how bad practices like embedding fixed sleep routines instead of signal-based waiting ruin test reliability. We discuss the necessity of designing products for testability from day one—such as using pair programming where one developer writes the implementation while the other writes the test suite, or building dedicated test interfaces directly into the application architecture. We also analyze the hidden business costs of poor quality, where engineering debt forces sales teams to spend their time managing upset clients instead of acquiring new revenue.

We explore organizational anti-patterns—such as teams claiming to be 'Agile' with one-year sprint cycles, or shipping debug builds to production because release builds continuously crash, highlighting a pair-programming model where one developer writes the code while another writes the corresponding tests

Finally, we tackle the dangers of chasing vanity metrics, from engineers writing automated assert pass statements to claim fake coverage, to organizations bragging about more code. Anoop distinguishes between output gain and outcome gain, warning that LLMs are creating a massive testing and review crisis by generating 20-page documentation files for minor features.

• Quality Iron Triange of Software
• Book: Sapiens
• ✨ Episode: DORA Report
• ✨ Episode: Grafana — Managing Open Source

• Warren - Proof of Quantum Consciousness - Paper
• Annop - Book: Genesis: Artificial Intelligence, Hope, and the Human Spirit