InfoQ Homepage InfoQ Content on InfoQ
-
The Latest in OpenJDK and JCP Expert Group: Insights with Simon Ritter
In this episode, Simon Ritter, deputy CTO at Azul, sat down with podcast host Michael Redlich, lead editor of the Java topic at InfoQ, and discussed the latest features in OpenJDK and Ritter’s experiences serving on the JCP Expert Group since JDK 9. OpenJDK topics included: the six-month release cycle, Generational Shenandoah, JDK Flight Recorder, Project Leyden and Compact Object Headers.
-
Building a More Appealing CLI for Agentic LLMs Based on Learnings from the Textual Framework
Will McGugan, the maker of Textual and Rich frameworks, speaks about the reasoning of developing the two two libraries and the lesson learned. Also, he shares light on Toad, his current project, which he envisions being a more visually appealing way of interacting with agentic LLMs through command line.
-
Platform Engineering for AI: Scaling Agents and MCP at LinkedIn
QCon AI New York Chair Wes Reisz talks with LinkedIn’s Karthik Ramgopal and Prince Valluri about enabling AI agents at enterprise scale. They discuss how platform teams orchestrate secure, multi-agentic systems, the role of MCP, the use of foreground and background agents, improving developer experience, and reducing toil.
-
Bridging the Open Source Gap: from Funding Paradoxes to Digital Sovereignty
Gabriele Columbro, managing director of the Linux Foundation Europe, discusses the differences in the open-source landscape between Europe, China and the US. Stressing that the open-source landscape is the last favorable ground for global innovation in the current geo-political landscape.
-
GenAI Security: Defending Against Deepfakes and Automated Social Engineering
In this episode, QCon AI New York 2025 Chair Wes Reisz speaks with Reken CEO and Google Trust & Safety founder Shuman Ghosemajumder about the erosion of digital trust. They explore how deepfakes and automated social engineering are scaling cybercrime and argues defenders must move beyond default trust, utilizing behavioral telemetry and game theory to counter attacks that simulate human behavior.
-
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.
-
The Evolution of Code Review: From Bug-Finding to Team Building
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Greg Foster about the evolution and purpose of code reviews, building teams with kindness, expertise, and urgency, and how AI tools are changing software development.
-
Building a Resilient and Inclusive Engineering Culture with Matthew Card
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Matthew Card about his resilience framework (CAPSS - Confidence, Adaptability, Purpose, Social Support) which has helped him overcome career challenges and now guides him in building inclusive engineering cultures by empowering teams and breaking echo chambers.
-
Finding Your Engineering Bottleneck: The Hierarchy of Engineering Needs
In this podcast, Shane Hastie, Lead Editor for Culture & Methods, spoke to Myles Henaghan about the open-sourced "Hierarchy of Engineering Needs" - a systematic framework inspired by Maslow's hierarchy that helps engineering leaders identify and prioritize the most impactful constraints limiting their software delivery systems among competing improvement initiatives.