SHOW: 413
DESCRIPTION: Brian talks with Heidi Waterhouse, (@wiredferret, Developer Advocate @LaunchDarkly) about the challenges of balancing stability and agility, from a technology perspective and a cultural perspective.
SHOW SPONSOR LINKS:
CLOUD NEWS OF THE WEEK:
SHOW INTERVIEW LINKS:
SHOW NOTES:
Topic 1 - Welcome to the show. We’re going to talk about broken systems today, but before we get into that, let’s talk about your background, and what types of things you work on at LaunchDarkly.
Topic 2 - As we start seeing companies adopt a lot of these new technologies and methods (Agile, DevOps, Microservices, Distributed Systems, Cloud-Native Apps, Continuous Integration, etc.) we’re seeing them go through this interesting transformation of having to think differently about how things should work and how they might break. This is an area that you talk about quite a bit.
Topic 3 - There is a 5 9s mentality and there is a release daily intro production mentality that sort of seem at odds with each other. How do we start figuring out how to manage that big space in between those two world views? Or can they be the same?
Topic 4 - By adding in error budgets, layered access, and other accommodations for failure and for designing our systems for function over form or purity - we learn how to add resiliency to their system by learning to trust but mitigate their reliance on the perfect performance of their underlying tools.
Topic 5 - You get to talk to a lot of developers and architects. What are some of the best ways that you’ve seen them not only grasp these concepts but communicate them up to their management chains so they educate them about the terminology and concepts?
FEEDBACK?
FEEDBACK?