The Reasoning Show

The Reasoning Show AI moves fast. Thinking clearly matters more.

The Reasoning Show cuts through the hype to explore how the smartest people in enterprise AI actually make decisions — the strategy, the tradeoffs, and the hard lessons no press release mentions.

Every week, hosts Aaron Delp and Brian Gracely sit down with the founders building the tools, investors funding the shift, and operators running AI in the real world. Not hype. Not panic. Just clear-headed conversations with people who have to make actual decisions.

Because the AI revolution isn't just happening. It's being reasoned through.

New shows every Wednesday and Sunday.

Topics: Enterprise AI strategy · LLMs in production · AI leadership · Agentic AI · Digital Sovereignty · Machine Learning · AI startups · Cloud Computing

All Episodes

The Reasoning Show

Everything is a Little Bit Broken

September 04, 2019 • Aaron Delp & Brian Gracely

0:00 | 35:07

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 Innovators
PricingWire - Pricing Metric Decision Guide

Digital Ocean Homepage
Get Started Now and Get a free $50 Credit on Digital Ocean
[FREE] Try an IT Pro Challenge
Get 20% off VelocityConf passes using discount code CLOUD

CLOUD NEWS OF THE WEEK:

Donate to the Red Cross for victims of Hurricane Dorian

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?