Software Engineering Daily

Software testing is widely understood as essential to building reliable systems, and it’s one of the hardest things to get right. A fundamental issue is that tests are good at confirming the behavior a team expects, but the most damaging failures tend to hide in the edge cases no one thought to check during development. Those blind spots are only growing as AI produces more code that no human has closely reviewed. Antithesis is a software verification company built around an approach called deterministic simulation testing. The platform runs a customer’s software in a fully controlled environment, exploring thousands of different paths through it at runtime. Crucially, the paths aren’t pre-specified and they’re not merely the expected cases. In this way, it can surface rare, damaging bugs that normal testing would never catch. Carl Sverre is on the Red Team at Antithesis and he also leads much of the company’s AI strategy. In this episode, Carl joins Sean Falconer to discuss the Antithesis approach to software verification, why reliability tooling has been chronically underinvested, what makes stateful and distributed systems so hard to test, how deterministic simulation testing works under the hood, and much more.Full Disclosure: This episode is sponsored by AntithesisSponsorship inquiries:[email protected] The post Software Verification in the Age of Coding Agents appeared first on Software Engineering Daily.

The popular story of Steve Jobs is that he co-founded Apple, was pushed out, wandered through a failed venture called NeXT, then returned to save the company and usher in the iPod and iPhone. That version is memorable, widely repeated, and, in an important sense, wrong. His years at NeXT are usually treated as a footnote, when they were among the most consequential of his life and career. Geoffrey Cain is the author of Steve Jobs in Exile, which draws on previously unpublished material and new interviews to illuminate the NeXT years. The book argues that NeXT was not a failure but the hidden turning point. Its operating system, NeXTSTEP, became the foundation of Mac OS X and, later, the iPhone, and its fingerprints are still visible in Apple’s code today. Dan’l Lewin was an early Apple employee who led the initial launch of the Macintosh into higher education. In 1985, he left the company alongside Steve Jobs to co-found NeXT, where he served as VP of Marketing and Sales. Over more than 30 years in Silicon Valley, he went on to hold senior roles at Sony and Microsoft, and later served as President and CEO of the Computer History Museum. In this episode, Geoffrey and Dan’l join Matt Merrill to discuss the story behind NeXT, the 1980s computing landscape that shaped it, the technical bets like Objective-C and dynamic binding that gave Apple a long head start, why the university market mattered so much, and how the company ended up shaping the devices in our pockets.Sponsorship inquiries:[email protected] The post Steve Jobs in Exile appeared first on Software Engineering Daily.

Automated browser testing is a foundational technology that many web developers rely on. Modern tooling lets a single test drive Chrome, Firefox, and Safari the same way, a triumph of software engineering built on years of standardization work. That standardization emerged from the interplay between open source projects, browser vendors, and standards bodies like the W3C. David Burns is a longtime Selenium and WebDriver contributor, a veteran of Mozilla, and is currently the Head of Developer Advocacy and Open Source at BrowserStack. In this episode, David joins Josh Goldberg to discuss how open source projects, browser vendors, and standards bodies fit together, a practical philosophy of testing built around one solid test per critical path, and the risks that AI and vibe coding introduce to web development.Sponsorship inquiries:[email protected] The post The State of Browser Testing appeared first on Software Engineering Daily.

Data retrieval is a fundamental challenge in AI systems, and the approaches for solving it are still evolving. Vector search was an early answer to the retrieval problem, but the rise of agentic systems has raised the stakes considerably. Agents issue queries at machine speed, decompose complex questions into parallel searches, and require retrieval infrastructure that can keep pace without becoming prohibitively expensive. Chroma is a company building open source infrastructure for AI applications, best known for its widely used database of the same name. The company also published the influential Context Rot paper, which documented how model performance degrades as context window utilization increases, and recently released Context One, a 20 billion parameter retrieval sub-agent trained to do agentic search at frontier model quality but at an order of magnitude lower cost and higher speed. Hammad Bashir is the CTO of Chroma, with a background spanning machine learning, computer vision, and data systems. In this episode, Hammad joins Gregor Vand to discuss the origins of ChromaDB, our current understanding of context rot, why a purpose-built small model can match frontier models on search tasks, the philosophy behind Chroma’s open source approach, and where the company sees AI data infrastructure heading.Sponsorship inquiries:[email protected] The post Chroma and Agentic Retrieval appeared first on Software Engineering Daily.

Most AI agent setups today are built around a single session, where one user interacts with one agent at a time. However, that model breaks down when an agent has to serve a business, where thousands of requests can arrive at once and each session needs to be isolated, durable, and recoverable. Getting agents to run reliably at that scale has meant a lot of hand-rolled infrastructure beneath the agent itself. eve is an open source, cloud-native agent framework from Vercel that removes much of the agent scaling burden. In the eve framework, an agent is defined declaratively through configuration files and these files compile into infrastructure as code so the platform provisions only what the agent actually uses. Andrew Barba is a Member of Technical Staff at Vercel, and Shar Dara is the Product Lead for eve at Vercel. In this episode, they join Kevin Ball to discuss what it means for an agent framework to be cloud-native, why they chose to express agents in plain English, and their view that company building is becoming agent building.Sponsorship inquiries:[email protected] The post Scaling Agent Workloads at Vercel appeared first on Software Engineering Daily.

The terminal has been a constant in software development for decades. It has remained largely unchanged while everything around it transformed. However, as AI agents have become central to the developer workflow, the terminal is emerging as a natural home for agentic development, and a new category of tooling is forming around it. Warp is a popular Rust-based terminal and agentic development environment. The company recently open-sourced its codebase and launched Oz, its cloud agent infrastructure product aimed at helping enterprises automate software development at scale. Zach Lloyd is the co-founder and CEO of Warp, and a former principal engineer at Google where he led engineering on the Google Docs suite. In this episode, Zach joins Gregor Vand to discuss how Warp has evolved over the years, why the terminal is better suited than the IDE for agentic development, how Oz approaches the governance and auditability challenges enterprises face with AI agents, and more.Sponsorship inquiries:[email protected] The post The Terminal as an Agentic Interface appeared first on Software Engineering Daily.

The most useful coding agents can mutate their environments by downloading packages, writing files, and connecting to services across the network. However, that freedom also presents dangers, and promises to usher in a new wave of security threats. Docker recently announced Docker Sandboxes, which give each agent its own isolated micro VM while preserving the familiar ergonomics of a container. A standard container shares the host’s kernel, but a micro VM emulates hardware and runs its own kernel, giving a stronger security boundary around code that cannot be trusted. Mark Cavage is the President and COO of Docker, and he previously worked at companies including Stripe, AWS and Oracle. In this episode, Mark joins Gregor Vand for a wide-ranging conversation that includes why agents break the immutability assumptions containers were built on, how micro VMs differ from both containers and traditional VMs, and the still-unsolved challenge of giving agents scoped, trustworthy access to sensitive services and data.Sponsorship inquiries: [email protected] The post Docker and Sandboxing AI Agents appeared first on Software Engineering Daily.