Continuous Delivery in a World of Constant Change • Abby Bangser & Dave Farley

This presentation was recorded at GOTO Copenhagen 2025.https://gotocph.comAbby Bangser - Principal Engineer at Syntasso & Team Topologies AdvocateDave Farley - Bestselling Author, Founder & Director of Continuous Delivery Ltd.RESOURCESAbbyhttps://bsky.app/profile/abangser.bsky.socialhttps://twitter.com/a_bangserhttps://github.com/abangserhttps://www.linkedin.com/in/abbybangserhttps://www.syntasso.io/members-area/abby/profileDavehttps://bsky.app/profile/davefarley77.bsky.socialhttps://www.continuous-delivery.co.ukhttps://linkedin.com/in/dave-farley-a67927https://twitter.com/davefarley77http://www.davefarley.netDESCRIPTIONDave Farley and Abby Bangser open with a clear statement: Continuous Delivery isn't a relic of the pre-AI era — it's the foundation that makes the AI era survivable. Dave's definition is simple but consequential: software should always be in a releasable state, verified after every small change. That's not just a workflow preference; it's the same incremental, hypothesis-driven approach that underpins science and engineering. In an AI-assisted world where code can be generated far faster than humans can reason about it, the discipline of small, safe, verifiable steps becomes more critical, not less. The danger isn't AI writing bad code — it's AI writing a lot of code very fast that nobody is properly checking.The conversation turns to a genuinely alarming DORA report statistic: 70% of developers using AI tools don't distrust the output. Abby draws a parallel to the long-running debate over whether developers can be trusted to test their own code — they usually can't, without a deliberate change in perspective. The same challenge applies to AI-generated code: you need to consciously shift from "prompter" mode to "verifier" mode, and most developers aren't making that switch. Dave closes with a surprising note of optimism: AI may be the industry's best-ever opportunity to finally get XP practices — small increments, automated tests, continuous feedback — embedded into how teams actually work. Not because anyone chose to adopt them ideologically, but because working without them while using AI is visibly, measurably risky.Read the full abstract here:https://gotocph.com/2025/sessions/3779RECOMMENDED BOOKSKief Morris • Infrastructure as Code • https://amzn.to/4e6EBQcMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQDave Thomas • simplicity • https://amzn.to/43FghBJDave Farley & Jez Humble • Continuous Delivery • https://amzn.to/3ocIHwdDavid Farley • Modern Software Engineering • https://amzn.to/3GI468MDave Farley • Continuous Delivery Pipelines • https://amzn.to/3rjetdiBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!