Podcasts

Simplify Your System by Challenging the Status-Quo and Learning from Other Ecosystems

In this podcast, Max Rydahl Andersen, distinguished engineer at RedHat and the creator of JBang, discusses how continuously learning from other ecosystems and adopting new tools allows you to simplify your thinking and systems. This will increase the developer joy of the coders and further obtain safer and more robust systems.

Building LinkedIn’s Resilient Data Storage: a Deep Dive into Derived Data Storage with Felix GV

In this podcast, Felix GV, Principal Staff Engineer at LinkedIn, discusses how to create and operate planet-scale data storage solutions for derived data. When it’s time to build a new system, how do you decide on the pieces that must be fitted to ensure a resilient operating system?

Understanding What Really Matters for Developer Productivity: a Conversation with Lizzie Matusov

In this podcast Michael Stiefel spoke with Lizzie Matusov about the dependency of effective, productive, and satisfied teams on good software architecture. Understanding this relationship requires understanding exactly what software productivity really is, how modern software engineering research has become more rigorous and practical, and how to apply that research to software development.

Facilitating Software Architecture with Andrew Harmel-Law

In this episode, Thomas Betts speaks with Andrew Harmel-Law about his new book, Facilitating Software Architecture: Empowering Teams to Make Architectural Decisions. The conversation includes a discussion of what constitutes an architecturally significant decision, how the practice of architecture is evolving, and how architects have a role to facilitate software architecture.

Your Software Will Fail; It is How You Recover That Matters: a Conversation with Randy Shoup

In this podcast Michael Stiefel spoke with Randy Shoup about how to build resilient systems. We discuss why it is a serious mistake to fail to acknowledge that software’s interaction with itself. We also discuss where to use workflows, orchestration or choreography, the role of architecture in building good teams, and the wisdom of letting each team use their own set of tools.