InfoQ Homepage Agile 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.
-
The Java Ecosystem Remains Ever-Green by Continuously Adapting to Developers' Needs
Kevin Dubois and Thomas Vitale, two cloud-native enthusiasts in the Java ecosystem, discuss the evolution of frameworks and tooling that has led to increased development and developer joy. They cover everything from Testcontainers to incorporating LLMs in existing applications, as well as how to ensure the code quality remains high, even with the proliferation of code generation tooling.
-
Achieving Seamless Integration through User Co-Design
Savannah Kunovsky and Jenna Fizel, co-managing directors of IDEO’s Emerging Technology division, talk about the future of technology in general and how we can work with our users to build the most impactful product. They explore prototyping and co-design techniques, as well as how generative AI can help with rapid prototyping.
-
Building the Middle Tier and Doing Software Migrations: a Conversation with Rashmi Venugopal
In this podcast, Michael Stiefel spoke with Rashmi Venugopal about two topics. The first is how the middle-tier creates the application from the raw materials in the back-end, and how the front-end uses the middle-tier to present a meaningful workflow to the user. The second is how to manage the usually inevitable software migration that results from a successful software product.
-
Designing for Knowledge Flow with Diana Montalion
In this episode, Thomas Betts speaks with Diana Montalion about how architecture is designing for knowledge flow. The conversation covers the differences between knowledge stock and knowledge flow and the importance of a growth mindset. If you’re trying to find new ways to solve problems, you have to start by thinking in new ways.
-
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.
-
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.