Discover
Adventures in DevOps
Adventures in DevOps
Author: Will Button, Warren Parad
Subscribed: 257Played: 8,052Subscribe
Share
© Rhosys AG
Description
Join us in listening to the experienced experts discuss cutting edge challenges in the world of DevOps. From applying the mindset at your company, to career growth and leadership challenges within engineering teams, and avoiding the common antipatterns. Every episode you'll meet a new industry veteran guest with their own unique story.
291 Episodes
Reverse
Share Episode Most companies out there believe that the best Turing test we have is the Captcha, and honestly it isn't working.Suchintan Singh from Skyvern joins us to talk through the challenges of automating processes on the web. Somehow we end up in the philosophical debate regarding one second after the discovery of human-proof-of-work, the CAPTCHAs. And if we can't solve these, you have to question, what is even a human? We dive into why relying purely on APIs is a failing strategy for web automation: out of 1.1 billion websites, only a fraction have functional APIs, let alone usable. Most cost-center organizations such as government portals or local telecom billing sites, have zero incentive to build or maintain developer endpoints. This reality plunges us into the ethical ambiguity of bot deployment. We review why actively bans users attempting to build Reddit bot farms or mass-create Anthropic accounts is still problematic and blur lines when standard business automation triggers an organization's anti-bot defenses. We get into the escalating absurdity of modern CAPTCHAs, noting how users are now forced to complete ridiculous mini-games—like solving dynamic platformer levels just to prove they aren't machines. 💡 Notable Links: ✨ Episode: Web MCP✨ Episode: Actually think about how are your users use your tools✨ Episode: Browsers, things that go wrong all the timeEverquest Pizza ordering — Pizza Hut (and not Domino's)Just East completely fails with AI generated food item imagesGoogle Research — Semantic Locators🎯 Picks: Warren - Mardingtop 75L BackpackSuchintan - Video game — RuneScape
Share Episode We sit down with veteran Principal Engineer Justin Abrahms to discuss why having a clear engineering scoreboard is critical to winning the software delivery game. Drawing on his experience scaling deployment pipelines for payment engineers, platform engineering teams, and globocorps, Justin explains the simple truth: when you deliberately do the right things—embracing continuous delivery, small batch sizes, and tight feedback loops—you get the right outcomes. Yet despite these battle-tested practices existing for decades, our industry suffers from an "Eternal September" fueled by terrible onramps. We dissect the performative theater of modern engineering, taking aim at the severe lack of intentionality in code reviews. Too many peer reviews devolve into superficial nitpicking rather than educational, inquisitive assessments of long-term maintainability. Justin shares lessons learned from working alongside Trevor Foucher (author of The Art of Readable Code) at Google, demonstrating how high-signal code reviews should actively educate developers and de-risk downstream systems before code ever hits production. Finally, we confront the reality that raw development speed is profoundly addictive. Teams chase the immediate dopamine hit of generating code faster with LLMs, ignoring what happens when they look just one week or one month out and realize unmaintainable prototypes instantly collapse under the weight of real customer changes 💡 Notable Links: Book: The Psychology of Software TeamsShort: Rory Sutherland — Slow is safer and better🎯 Picks: Warren - Malicious domain names researchJustin - Deadworld Isekai
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). 💡 Notable Links: ✨ Episode: Sam Goto — Security challenges in the Browser World✨ Episode: Actually think about how are your users use your toolsMozilla CI - Tree HerderThe Worst UX site with a perfect 100Project Fugu Browser initiativeWebMCP Project Specification🎯 Picks: Warren - Paper — The Corporate Bullshit Receptivity ScaleDavid - 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. 💡 Notable Links: ✨ Episode: Grafana — Observability✨ Episode: AST can run anythingBook: Lean Manufacturing — The Toyota WayMonkeys typing the Complete Works of ShakespearePaper: Ironies of Automation (& AI)Jeff Bezos API Rant — 2011Book: The Formula, Science SuccessShow: Burn Notice🎯 Picks: Warren - The AgencyEric - 継続は力なり — 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. 💡 Notable Links: Quality Iron Triange of SoftwareBook: Sapiens✨ Episode: DORA Report✨ Episode: Grafana — Managing Open Source🎯 Picks: Warren - Proof of Quantum Consciousness - PaperAnnop - Book: Genesis: Artificial Intelligence, Hope, and the Human Spirit









