InfoQ Homepage Podcasts
-
Why Rust Will Help You Deliver Better Low-latency Systems and Happier Developers
Andrew Lamb, a veteran of database engine development, shares his thoughts on why Rust is the right tool for developing low-latency systems, not only from the perspective of the code’s performance, but also looking at productivity and developer joy. He discusses the overall experience of adopting Rust after a decade of programming in C/C++.
-
Is WebAssembly the Secure, Efficient Alternative Everybody was Waiting for?
Laurent Doguin and Geoffroy Couprie discuss their pioneering work with Wasm on the infrastructure side. They walk us through the benefits and challenges of building a platform over WebAssembly and why it’s the safer alternative to containers.
-
Continuous Deployment and Pair Programming for Lean Software Delivery Even without Jira
Asgaut Mjølne Söderbom and Ola Hast, two developers with Sparebank1, speak about their journey towards continuous deployment and pair programming. During the conversation, they share how they use the "waste clock" to identify areas of improvement or how TDD helps them deliver high-quality code.
-
Sovereign Clouds, Hyperscalers and European Alternatives: InfoQ Dev Summit Munich 2025 Preview
In this podcast episode, speakers from the upcoming InfoQ Dev Summit Munich 2025 tackle the practical challenges facing European developers caught between regulatory pressures and technological realities. The panel discusses trade-offs between using US cloud providers versus emerging European alternatives, exploring cloud-agnostic architecture strategies and the implications of data sovereignty.
-
The Financial Architecture of Software with Ian Miell
In this episode, Thomas Betts speaks with Ian Miell about how the financial aspects of a business affect how software is designed and built. If Conway’s Law says organizational structures determine the software design, then following the money helps us understand why those organization structures exist, and ultimately whether software will be successful in achieving its goals.
-
From Code to Strategy: Drive Organizational Impact Through Strategic Conversations and User Focus
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Mark Allen about how engineers can expand their influence through strategic conversations, user-focused development practices, and excellence in incident management. Mark emphasizes the importance of building cross-organizational relationships and working on meaningful problems with positive impact.
-
Productivity Through Play: Why Messing Around Makes Better Software Engineers
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Holly Cummins about productivity in creative knowledge work like software engineering. She talks about how "messing around and having fun" actually enhances problem-solving, while exploring the shift from coding to code management with AI tools and the importance of managing cognitive load in modern development practices.
-
Technology Radar and the Reality of AI in Software Development
Shane Hastie, Lead Editor for Culture & Methods spoke to Rachel Laycock, Global CTO of Thoughtworks, about how the company's Technology Radar process captures technology trends around the globe. She is sceptical of the current AI efficiency hype, emphasizing that real value of generative AI tools lies in solving complex problems like legacy code comprehension rather than just writing code faster.
-
Using AI Code Generation to Migrate 20000 Tests
In this podcast, Shane Hastie, Lead Editor for Culture & Methods spoke to Sergii Gorbachov, a staff engineer at Slack, about how they successfully used AI combined with traditional coding approaches to migrate 20,000 tests in 10 months, discovering that AI alone was insufficient and required human oversight and conventional tools to work effectively.
-
Emerson Murphy-Hill on Engineering Productivity, Team Dynamics and Equity
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.