Andy Brinkmeyer shares how engineering leaders and architects can use Rust to build failure-proof systems. Moving beyond memory safety, he explains how ownership, enums, and the typestate pattern embed complex runtime protocols into compile-time checks. Learn to eliminate entire classes of bugs, manage real-world resources safely, and maximize codebase robustness effortlessly.
In this eMag, we try to establish agentic AI architecture as a new type of software architecture that will likely dominate the industry for years to come. The articles, written by industry experts, cover various elements and aspects of agentic AI architecture. We aim to present the latest trends and developments shaping the new type of architecture as it enters the mainstream.
Itamar Friedman discusses how architects and engineering leaders can break through the AI productivity ceiling using adaptive multi-agent systems. He shares insights on moving past simple autocomplete to resilient workflows by integrating autonomous testing, intelligent code review, and robust arbitration. Learn how to govern agent communication and build a context-driven SDLC that scales.
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Gabriela Moreira about making formal methods accessible through the Quint specification language, how AI is dramatically lowering the barrier to entry for formal specification and model-based testing, and why defining correct system behaviour remains essential human work in an AI-driven world.
In this episode, Alex Zenla (CTO/Co-founder, Edera) challenges the "laissez-faire" attitude toward modern infrastructure. She promotes "spite-driven development", building software to solve genuine technical pain points rather than passively accepting flawed abstractions, as a philosophy of improving the world of software.
InfoQ's podcasts are interviews with the software architects, senior engineers, and team leaders who build and
operate production systems. Episodes work through the tradeoffs behind real decisions in
software architecture,
AI and ML engineering, and
engineering culture. Guests are practitioners
and QCon speakers describing what worked and what broke in systems they built.
The InfoQ Podcast
About this Podcast
Interviews with the software architects and senior engineers who build and run production systems. Each episode works through the tradeoffs behind a real decision in architecture, AI engineering, and development.
Vivek Yadav, an engineering manager from Stripe, shares his experience in building a testing system based on multi-year worth of data. He shares insights into why Apache Spark was the choice for creating such a system and how it fits in the "traditional" engineering practices.
Marina Moore, a security researcher and the co-chair of the security and compliance TAG of CNCF, shares her concerns about the security vulnerabilities of containers. She explains where the issues originate, providing solutions and discussing alternative routes to using micro-VMs rather than containers. Additionally, she highlights the risks associated with AI inference.
In this podcast, Michael Stiefel spoke with Randy Shoup about how to evolve your software after a software failure, and how to improve the resilience of your software by modeling transient states using events and workflows. Software failure is inevitable, but learning from failure, including making the necessary changes to organizational culture, can make your software more resilient.
Magdalena Picariello reframes how we think about AI, moving the conversation from algorithms and metrics to business impact and outcomes. She champions evaluation systems that don't just measure accuracy but also demonstrate real-world business value, and advocates for iterative development with continuous feedback to build optimal applications.
Jenish Shah, a back-end engineer focused on distributed systems at Netflix, provides more insights into how to handle failures in a distributed systems setup. He shares details on how he built a library that handles exceptions uniformly, regardless of the underlying communication protocol.
Conversations on building intentional engineering culture: team dynamics, leadership, and software management. For engineering leaders, managers, and the developers they support.
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Emerson Murphy-Hill about how measuring developer productivity is tricky, why team dynamics and psychological safety matter more than things like meeting load, the impact of systemic bias and how new AI tools are shaping equity in engineering - sometimes helping, but sometimes risking new kinds of unfairness.
In this podcast, Shane Hastie, Lead Editor for Culture & Methods spoke to Bhavani Vangala about creating powerful yet simple technology solutions, taking a balanced approach to AI tools, fostering inclusive team environments, and empowering women in tech leadership through focusing on strengths rather than societal constraints.
This is the InfoQ Culture & Methods Trends Report for 2025. Featuring the InfoQ editorial team and special guest Charity Majors, they discuss how AI is transforming software development with dramatic productivity gains alongside quality concerns, emphasize the continued importance of team collaboration, observability, engineering metrics, and creating high-performing software teams.
Shane Hastie spoke to John Gesimondo about how to leverage generative AI tools to support sustainable mental peace and productivity in the complex, interruption-prone world of software engineering by developing a practical framework that addresses emotional recovery, overcoming being stuck, structured planning and communication, maximizing flow, and fostering divergent thinking.
In this podcast, Shane Hastie, Lead Editor for Culture & Methods spoke to Erin Doyle about her journey as a generalist engineer, her passion for web accessibility, the importance of empathy and psychological safety in engineering teams, and her commitment to building better developer experiences by fostering collaboration, continuous learning, and vulnerability among technical professionals.