InfoQ Homepage InfoQ Content on InfoQ
-
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.
-
Microfrontends: Heuristics, Patterns and Antipatterns by Luca Mezzalira
Luca Mezzalira, a pioneer and enthusiast of microfrontends, discusses the microfrontends' evolution over the past years, underlying a set of heuristics that will allow you to gradually implement them in your product. He also touches on approaches to obtain quick feedback, both in your inner and outer development loops.
-
Understanding Event-Driven Architecture in a Multicloud Environment
Teena Idnani, senior solutions architect at Microsoft, shares her experience on how and when to use event-driven architectures to improve the experience of your customers. She touches on when to use and not use this approach, as well as how to design your system, implement observability, and when to consider using more than one cloud vendor.
-
Techniques for Improving Communication and Connection in Technical and Social Settings
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Geoffrey Huck about how software engineers can improve their communication skills, particularly with non-technical colleagues, by actively seeking feedback, using analogies and stories to explain technical concepts and varying their speaking style to keep audiences engaged.
-
Intentional Culture and Continuous Compensation: An Interview with Austin Vance
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Austin Vance, about the importance of intentional onboarding and culture-building, as well as his company's unique approach to compensation and the role of managers in retaining top talent.
-
Building Safe and Usable Medical Device Software: A Conversation with Neeraj Mainkar
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Neeraj Mainkar about the challenges of developing safe and usable medical device software in areas where software bugs can have life-and-death consequences, and how to approach these challenges through rigorous processes, user-centered design, and leveraging emerging technologies.
-
Leveraging AI Platforms to Improve Developer Experience – From Personal Hackathon to AI at Scale
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Olalekan Elesin about how generative AI tools can elevate developer experience by enabling engineers to be more creative and productive. He stresses the need to manage expectations, develop prompt engineering skills, and maintain a focus on security and customer privacy when leveraging these tools in an enterprise setting.
-
Building Effective Engineering Teams and Avoiding Cargo Cult Practices
In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to David Guttman about building effective engineering teams, avoiding common pitfalls, critiques of cargo cult practices, building great engineering culture and the importance of individual accountability.