Abstract
Register
$2,995, Conference (3 days). Current pricing ends November 10th. All pass options.
76%
senior dev or higher
1:11
speaker ratio
60+
practitioners
QCon San Francisco 2026 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Slides & video
Slides Not available
Video Not available
From the same track
Monday 16 November
10:35 Seacliff ABC Session Resiliency The Freeze Paradox: Why Stopping Deployments Doesn't Stop Failures Prachi Jain, Sandhya Narayan When systems fail at Netflix and in an environment this complex, they sometimes will, the instinctive response is to freeze deployments. 11:45 Seacliff ABC Session Resilience Adapt or Drift: Resilience Engineering When AI Moves the Operating Point Andrew Hatch Engineering Leader and SRE Manager @Cisco ThousandEyes, With 25+ Years Building Software, Operations, SRE, and Platform Teams Across Australia, India, and the United States Resilient systems do not stay resilient by standing still. They survive by adapting. But adaptation comes with risk: under sustained pressure, organizations and systems can slowly drift toward failure while still appearing to operate normally. 13:35 Seacliff D Unconference Unconference: Resilience Engineering 14:45 Seacliff ABC Session Reliability Saturation: How Your Software Will Fail at Scale Lorin Hochstein Staff Software Engineer @Airbnb, Writes @surfingcomplexity.blog, Previously @Netflix and Member of the Resilience in Software Foundation Even in the ethereal world of software, everything has a limit. And, once that limit is reached, very bad things can happen. In this talk, we will explore the problem of saturation: when a software system runs into one of these limits. 15:55 Seacliff ABC Session Incidents What Is Incident Severity, but a Lie Agreed Upon? Em Ruppe Technical Incident Commander @Chime, Previously @SendGrid and @Twilio, and Product and Training @Jeli.io Is your incident severity a complex word problem? Do you arbitrate which severity an incident should be during the incident itself? Do you know what the difference between your severities are? Do you even have incident severity in your org? 17:05 Seacliff ABC Session It's Never the Thing That Broke: Learning From Incidents at (AI) Speed Vanessa Huerta Granda Resilience Engineering Manager @Enova, Co-Author of the Howie Guide on Post Incident Analysis, Board Member for the Resilience in Software Foundation When something breaks, our first instinct is to focus on the thing that failed. But in complex systems, the failure is usually the result of many things going right, changing, and interacting in ways we didn't anticipate.