Podcasts

Safely Changing Software to Avoid Incidents: a Conversation with Justin Sheehy

In this podcast, Michael Stiefel spoke with Justin Sheehy about how to safely put software into production without creating production incidents. Among the topics discussed were the futility of root cause analysis, and the importance of having a shared language for discussing incidents. This discussion included the need for software to be malleable as well as observable.

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.

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.