InfoQ Homepage Podcasts
-
Cloud Security Challenges in the AI Era - How Running Containers and Inference Weaken Your System
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.
-
Architecture Should Model the World as it Really is: a Conversation with Randy Shoup
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.
-
If You Can’t Test It, Don’t Deploy It: The New Rule of AI Development?
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.
-
Effective Error Handling: a Uniform Strategy for Heterogeneous Distributed Systems
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.
-
Cloud and DevOps InfoQ Trends Report 2025
In this episode of the podcast, members of the InfoQ editorial staff and friends of InfoQ will discuss current trends in the cloud and DevOps domains as part of our annual trends report creation process. These reports provide InfoQ readers with a high-level overview of key topics to watch and also help the editorial team focus on innovative technologies.
-
Using Brain Science to Communicate and Lead Technical Teams Effectively
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Charlotte de Jong Schouwenburg about how understanding brain science and emotional intelligence can help engineers and technical leaders improve communication, manage conflict, and build stronger teams.
-
Building Engineering Culture Through Autonomy and Ownership
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Marcos Arribas about building and scaling engineering culture as an organisation grows, emphasizing autonomous teams, ownership mentality, progressive feature rollouts with flags, small pull requests, strategic AI adoption, and the importance of hiring junior engineers for long-term organizational growth.
-
How Blameless Culture Transforms Engineering Teams
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Tameem Hourani about building a blameless engineering culture through radical transparency, focusing on system resilience over individual blame, and creating high-performing teams that can embrace change and learn from failures.
-
The Myth of 100% Utilization: The Neuroscience of Productive Teams
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Shannon Mason about optimizing team productivity by understanding the neuroscience behind cognitive load, distinguishing between beneficial "slack time" and detrimental "idle time", and how the pursuit of maximum utilization that leads to burnout and poor decision-making.
-
Why Software Development Sucks And 7 Mental Models To Help Fix It
Shane Hastie, Lead Editor for Culture & Methods, spoke to Thanos Diacakis about how teams often struggle with software delivery. He proposes a shift in mental models and a four-step framework to systematically improve software development by focusing on bottlenecks, balancing different types of work beyond just feature delivery, and investing 20-30% of effort in improving how the team works.