Podcasts

Architecture Should Model the World as it Really is: a Conversation with Randy Shoup

In this podcast, Michael Stiefel spoke with Randy Shoup about how to evolve your software after a software failure, and how to improve the resilience of your software by modeling transient states using events and workflows. Software failure is inevitable, but learning from failure, including making the necessary changes to organizational culture, can make your software more resilient.

Effective Error Handling: a Uniform Strategy for Heterogeneous Distributed Systems

Jenish Shah, a back-end engineer focused on distributed systems at Netflix, provides more insights into how to handle failures in a distributed systems setup. He shares details on how he built a library that handles exceptions uniformly, regardless of the underlying communication protocol.

Mental Models in Architecture and Societal Views of Technology: a Conversation with Nimisha Asthagiri

In this podcast, Michael Stiefel spoke with Nimisha Asthagiri about the importance of system thinking, multi-agent systems, the consequences of society applying a technology into an area for which it was not designed, and whether we can ever have a healthy relationship with artificial intelligence.

Scaling Systems, Companies, and Careers with Suhail Patel

In this episode, Suhail Patel joins Thomas Betts for a discussion about growing yourself as your company grows. When he started at Monzo, Patel was one of four engineers on the then new platform team–there are now over 100 people. The conversation covers how to thrive when the company and the systems you’re building are going through major growth.

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.