Speaker
Abstract
AI is making it dramatically easier to create and change software, but writing code is only one part of the software lifecycle. Every change still needs to be deployed, observed, operated, diagnosed, and kept reliable in production. As the volume of software changes grows, the bottleneck increasingly shifts from writing code to operating it safely.
Drawing on lessons from operating large-scale distributed systems at LinkedIn, this talk follows a software change through the production lifecycle: Deploy → Observe → Operate → Incident → Diagnose → Mitigate → Learn → Improve. We will look at practical patterns for catching problems before production, reducing deployment risk, detecting and diagnosing failures, and deciding where production responsibilities should live as more people and AI agents create software.
Finally, we will look at how incidents can become inputs to the next software change by turning operational learnings into automated tests, deployment policies, detection rules, rollback conditions, and platform guardrails.
The goal isn't to slow down software development. It's to make sure we can move faster without sacrificing reliability, with platforms that make production safety the default.
Key Takeaways:
- Learn how to evolve the SDLC beyond AI-assisted coding, with practical patterns for safely deploying, observing, diagnosing, and mitigating a growing volume of software changes.
- Understand which production responsibilities belong in the platform versus the application, and how abstractions and guardrails around deployment, observability, traffic, reliability, and rollback can make safe operation the default.
- Learn how to build a feedback loop from production back into development, turning incidents and operational learnings into automated tests, detection rules, deployment policies, and guardrails that prevent the same class of failure from recurring.
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.
Part of the track
Code Beyond Engineers & Engineering Teams Hosted by Suhail Patel Member of Technical Staff @OpenAI, Previously @monzoFrom the same track
Wednesday 18 November
10:35 Seacliff ABC Session Builder-Driven Development: Rebuilding the Organization Around the Builder Jyothi Nookula Product Leader Director with 13+ Years Driving AI Product & Platform Innovation, Previously @Meta, @Amazon, and @Etsy Most teams still run agent development the way they run traditional software projects. Requirements are written up front, builders execute against them, and a demo closes out the cycle. That model works poorly for agents, because the most useful information rarely comes from a planning document. 11:45 Seacliff ABC Session Staff Plus Engineering Legacy as Leverage: How Brownfield Work Builds Technical Judgment Shine Garg Founder of Uncharted Path Breakthroughs, Former Staff Software Engineer, 15+ Years Building and Scaling Backend, Data, Machine Learning, and Platform Systems Legacy systems are often treated as a necessary evil: work to be endured rather than an opportunity to develop technical judgment. 13:35 Ballroom BC Session AI/ML Product Engineering: When code costs nothing, what's next? Laurie Voss Head of Developer Relations @Arize AI, Co-Founder of npm, Inc., Developer for 30+ Years Coding agents produce 741% more code, and only 30% more software ships as a result. The gap is human review: people top out around 400 lines an hour and agents are not slowing down. This talk is for engineering leaders trying to decide what to do about that. 14:45 Ballroom BC Session AI You Can't Read the Code Anymore - Verifying Software in the Age of AI Omer van Kloeten Principal Engineer @Forter, 25+ Years in Software Engineering, Now Building an AI-Agent Framework to Tame Legacy Systems and Reduce KTLO AI writes most of the code now, so the hard part of engineering has moved from authoring to the part we’re worse at - verifying. With the incentives all pushing toward shipping faster and faster - the rational move is to skim the diff, click through a little manual QA, and ship on vibes. 15:55 Ballroom BC Session When Everyone Can Code, Who Owns Production? Sanjay Singh Staff Software Engineer @LinkedIn Specializing in Large-Scale Distributed Systems, Traffic Infrastructure, Reliability, and Zero Trust Security AI is making it dramatically easier to create and change software, but writing code is only one part of the software lifecycle. Every change still needs to be deployed, observed, operated, diagnosed, and kept reliable in production.