![Cloud Computing artwork](https://is2-ssl.mzstatic.com/image/thumb/Podcasts123/v4/b7/53/cf/b753cf9a-a74d-df30-e6f7-4bec5abdb6e3/mza_11081673843999015901.jpg/100x100bb.jpg)
Everything is a Little Bit Broken
Cloud Computing
September 04, 2019 05:00 - 35 minutes - 24.1 MB - ★★★★ - 79 ratingsTechnology News Tech News Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
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:
PricingWire: Monetization & Pricing Strategy for Software & Technology InnovatorsPricingWire - Pricing Metric Decision GuideCLOUD NEWS OF THE WEEK:
Donate to the Red Cross for victims of Hurricane DorianSHOW INTERVIEW LINKS:
Heidi Waterhouse (homepage)Heidi’s upcoming keynote at Velocity (Berlin)LaunchDarkly HomepageSHOW 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?