GOTO - The Brightest Minds in Tech

Hosted by GOTO

Technology News Science

Website RSS feed LinkedIn YouTube

Episodes

332

Latest episode

Aug 2026

Language

EN-US

About the show

The GOTO podcast seeks out the brightest and boldest ideas from language creators and the world's leading experts in software development in the form of interviews and conference talks. Tune in to get the inspiration you need to bring in new technologies or gain extra evidence to support your software development plan.

Listen to episodes

60 recent

August 14, 2026Episode 5832 min

The Platform Engineer’s Handbook • Ajay Chankramath & Kaspar von Grünberg

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/451Ajay Chankramath - Founder & CEO at Platformetrics & Co-Author of "The Platform Engineer’s Handbook"Kaspar von Grünberg - Founder & CEO at Stealth & Author of "Thinking in Platforms"RESOURCESAjayhttps://www.linkedin.com/in/chankramathhttps://github.com/achankrahttps://x.com/ajchantwhttps://chankramath.comhttps://platformetrics.comKasparhttps://www.linkedin.com/in/kvgruenberghttps://github.com/Kasparvongruenberghttps://kasparvongruenberg.comLinkshttps://peh-packt.platformetrics.comDESCRIPTIONAjay Chankramath — author of The Platform Engineer’s Handbook — joins Kaspar von Grünberg to unpack why he wrote a 14-chapter, code-first practitioner's guide instead of another theory-heavy platform book. The conversation's core thesis: the reason developers don't adopt platforms isn't a technology gap, it's a product discipline gap — a failure to treat developer experience as a first-class outcome with a real feedback loop. Ajay walks through the book's arc, from Kubernetes and service-mesh foundations through self-service portals to enterprise-grade concerns like policy-as-code and FinOps, and makes a pointed case for building on 100% open-source, vendor-agnostic tooling as a hedge against geopolitical and licensing whiplash.The most relevant thread for engineers building with AI today: citing a McKinsey finding that only 6% of AI initiatives show real productivity gains, Ajay argues that agentic AI doesn't reduce the need for platform engineering — it raises the stakes. As coding agents become genuine actors in the SDLC rather than tools, IDPs need a new layer for agent context, memory, tool registries, and guardrails, and that layer "must be built, owned, and operated by you," not bought off the shelf.His conclusion: the differentiator in the AI era isn't which frontier model you use — it's whether your platform foundations are solid enough to make agents safe and productive at all.RECOMMENDED BOOKSAjay Chankramath • The Platform Engineer's Handbook • https://amzn.to/4eCSibMAjay Chankramath & Eamonn Ryan • Domain-Driven Platform Engineering • https://amzn.to/3TdiC3JChankramath, Cheneweth, Oliver & Alvarez • Effective Platform Engineering • https://amzn.to/3OnxN8iKaspar von Grünberg & Luca Galante • Thinking in Platforms • https://weaveintelligence.io/thinking-in-platforms-bookGregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdbBlueskyInstagramLinkedInFacebookCHANNEL 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!

August 7, 2026Episode 5747 min

State of the Art of Platform Engineering • Abby Bangser & Charles Humble

This interview was recorded for GOTO State of the Art in April 2026.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/450Abby Bangser - Principal Engineer at Syntasso & Team Topologies AdvocateCharles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESAbbyhttps://bsky.app/profile/abangser.bsky.socialhttps://twitter.com/a_bangserhttps://github.com/abangserhttps://www.linkedin.com/in/abbybangserhttps://www.syntasso.io/members-area/abby/profileCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://blog.container-solutions.com/paula-kennedy-on-platform-team-responsibilities-patterns-and-anti-patternshttp://sites.libsyn.com/406853/syntasso-coo-paula-kennedy-on-platform-team-responsibilities-patterns-and-anti-patternshttps://www.oreilly.com/library/view/platform-as-a/0642572243777https://github.com/Cloud-Native-Platform-Engineering/cnpe-community/issues/79https://www.kratix.iohttps://leaddev.com/ai/nobody-knows-what-programming-will-look-like-in-two-yearshttps://leaddev.com/ai/shipping-faster-thinking-less-the-ai-code-verification-traphttps://www.cncf.io/blog/2023/11/20/announcing-the-platform-engineering-maturity-modelhttps://platformengineering.com/features/portals-and-pipelines-arent-enough-avoiding-the-platform-facadeDESCRIPTIONAbby Bangser opens with a clear-eyed status report on platform engineering: the concept of centralizing shared capabilities with self-service delivery is well understood, but the execution keeps going wrong in the same way. Organizations move from DevOps to platform engineering, but their platform teams end up becoming the new bottleneck — a centralized group drowning under the weight of the entire organization's requests, which is exactly what DevOps was supposed to fix. Abby traces this to an architectural problem: too many platforms are still built as centralized Terraform machines rather than as a marketplace of composable offerings. Her "platform as a product" test is blunt and useful: has the team ever said "no" to a feature request, or deprecated something?If not, they don't have a product — they have a request queue.The AI dimension is where the conversation gets most urgent. Abby's position is direct: AI agents are the new forcing function for platform maturity. The biggest misconception she wants to dismantle is the persistent equation of platform engineering with infrastructure-as-code: renaming your Terraform team doesn't count. Platform engineering is about building an experience — for human developers and increasingly for AI agents — that is self-service, compliant, and coherent at organizational scale. The Team Topologies model of interaction modes (from high-collaboration to fully automated on-demand APIs) gives a useful health check for where a platform actually sits on that maturity curve.RECOMMENDED BOOKSChankramath, Cheneweth, Oliver & Alvarez • Effective Platform Engineering • https://amzn.to/3OnxN8iGregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdbBlueskyInstagramLinkedInFacebookCHANNEL 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!

July 31, 2026Episode 5628 min

The C4 Model: Visualizing Software Architecture • Simon Brown & Susanne Kaiser

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/449Simon Brown - Author & Creator of "The C4 Model"Susanne Kaiser - Independent Tech Consultant & Author of "Architecture for Flow"RESOURCESSimonhttps://simonbrown.jehttps://bsky.app/profile/simonbrown.jehttps://twitter.com/simonbrownhttps://linkedin.com/in/simonbrownjerseyhttps://c4model.comSusannehttps://bsky.app/profile/suksr.bsky.socialhttps://mastodon.social/@suksrhttps://www.linkedin.com/in/susannekaiser1https://susannekaiser.netLinkshttps://structurizr.comDESCRIPTIONSimon Brown explains that the C4 Model started not as a grand design theory, but as a practical answer to an embarrassing problem: running a workshop on architecture diagramming, he realized he couldn't understand any of the diagrams being produced. The model formalized his own consulting practice of hierarchical handover documentation — context diagram at the top, containers below, components and code at the bottom — giving it a name and making it teachable. His core advice is to start with just the top two levels: context and container diagrams. These change infrequently, are quick to draw, and deliver immediate value. Levels three and four — components and code — are included for completeness but age rapidly with every commit, and in most cases aren't worth the maintenance overhead.Two especially practical insights emerge from the conversation. First, how to handle microservices: if your team owns all the services inside a system boundary, each service is a collection of C4 containers; if you depend on another team's service that you can't see inside, model it as an opaque software system. This maps naturally to how domain boundaries and team ownership actually work in practice. Second, the surprisingly important distinction between modeling and diagramming: C4's real value is the shared vocabulary — systems, containers, components, code — not the visual notation itself. Teams using entirely different tooling can communicate clearly because they've agreed on what the words mean. Simon is firm that there will be no C4 v2; the model is intentionally lightweight, and adding more would risk turning it into the next UML — comprehensive, heavy, and largely abandoned.RECOMMENDED BOOKSSimon Brown • The C4 Model • https://amzn.to/4xB9V33Susanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcNick Rozanski &, Eóin Woods • Software Systems Architecture • https://amzn.to/4cOLtTvvan Kelle, Verschatse &Baas-Schwegler • Collaborative Software Design • https://amzn.to/4iv0N8IBlueskyInstagramLinkedInFacebookCHANNEL 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!

July 24, 2026Episode 5544 min

Cloud, Containers, Security & AI - What’s Now, What’s Next? • Adrian Mouat, Kief Morris & Sam Newman

This interview was recorded at GOTO Copenhagen 2025.https://gotocph.comAdrian Mouat - Developer Relations at Chainguard & Author of "Using Docker"Kief Morris - Author of "Infrastructure as Code" & Distinguished Engineer at ThoughtworksSam Newman - Author of "Building Microservices" & "Monolith to Microservices"RESOURCESAdrianhttps://bsky.app/profile/adrianmouat.comhttps://twitter.com/adrianmouathttps://github.com/amouathttps://linkedin.com/in/adrianmouathttp://www.adrianmouat.comKiefhttps://bsky.app/profile/kief.comhttps://twitter.com/kiefhttps://github.com/kiefhttps://www.linkedin.com/in/kiefmorrishttps://infrastructure-as-code.comhttps://kief.comSamhttps://twitter.com/samnewmanhttps://www.linkedin.com/in/samnewmanhttp://samnewman.iohttp://samnewman.io/bloghttps://github.com/snewmanABSTRACTIn this session, Sam Newman will interview Kief Morris and Adrian Mouat, both experts in their field. We will explore the current reality of security in the container world, how infrastructure automation is impacted by AI, and whether platform teams are actually working. We’ll also be taking lots of questions from the audience! [...]Read the full abstract here:https://gotocph.com/2025/sessions/3938RECOMMENDED BOOKSAdrian Mouat • Using Docker • https://amzn.to/3PEYIJLLiz Rice • Container Security • https://amzn.to/3oU4iJeKief Morris • Infrastructure as Code • https://amzn.to/4e6EBQcSam Newman • Building Resilient Distributed Systems • https://www.oreilly.com/library/view/building-resilient-distributed/9781098163532Sam Newman • Monolith to Microservices • https://amzn.to/2Nml96EBlueskyInstagramLinkedInFacebookCHANNEL 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!

July 17, 2026Episode 541 hr 3 min

Signals & Levers • Elisabeth Hendrickson, Joel Tosi & Charles Humble

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubElisabeth Hendrickson - Advisor, Coach, Speaker & Co-Author of "Signals & Levers"Joel Tosi - Co-Founder & CTO at Dojo & Co & Co-Author of "Signals & Levers"Charles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantCheck out more here:https://gotopia.tech/episodes/448RESOURCESElisabethhttps://ruby.social/@testobsessedhttps://github.com/testobsessedhttps://www.linkedin.com/in/testobsessedhttps://curiousduck.ioJoelhttps://mastodon.social/@joeltosihttps://www.linkedin.com/in/joel-tosi-531a3bCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://ruthmalan.comhttp://www.ask-force.org/web/Discourse/Rittel-Dilemmas-General-Theory-Planning-1973.pdfDESCRIPTIONElisabeth Hendrickson and Joel Tosi open by explaining why systems thinking is having a moment right now: organizations that went all-in on Agile and DevOps are finding those returns plateauing, and the rise of AI is forcing engineering teams to reexamine where their real bottlenecks are. The book, Signals & Levers, gives software engineers a practical vocabulary and toolkit for that examination. A core insight is that most organizational dysfunction isn't caused by bad people or bad intentions, but by systems that produce bad outcomes predictably and structurally. The named archetypes in the book — over 20 of them, covering patterns like escalating technical debt, the "fixes that fail" loop, and the boiling frog — give teams a shared language to recognize and reason about those patterns without having to discover them from scratch.The most practically actionable section of the conversation covers signals versus levers: understanding the difference between information (a signal) and an intervention point (a lever) is the foundation for making changes that actually work rather than changes that feel productive and achieve nothing. On AI, both authors are cautious in the right ways: Elisabeth uses it daily as a thinking partner but keeps herself firmly at the steering wheel. Joel's warning is starker — AI amplifies whatever is already true about your organization, including dysfunction, and if it lets you ship faster than you can learn, the consequences may be severe. The book closes with an exercise for the reader: if AI doubles your delivery speed, what happens when you can ship faster than you can adapt?RECOMMENDED BOOKSElisabeth Hendrickson & Joel Tosi • Signals & Levers • https://amzn.to/4g6Fb3CDiana Montalion • Learning Systems Thinking • https://amzn.to/3ZpycdJDon Norman • The Design of Everyday Things • https://amzn.to/4fV6QVlGene Kim • The Unicorn Project • https://amzn.to/3woXQDzGene Kim, Kevin Behr & George Spafford • The Phoenix Project • https://amzn.to/3X9cYxaPeter Degrace & Leslie Hulet Stahl • Wicked Problems, Righteous Solutions • https://amzn.to/3ScP0D9Frederick Brooks Jr. • The Mythical Man-Month • https://amzn.to/4gd10OVGerald Weinberg • An Introduction to General Systems Thinking • https://amzn.to/4dZCsaODonella H. Meadows • Thinking in Systems • https://amzn.to/3XtqYCVBlueskyInstagramLinkedInFacebookCHANNEL 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!

July 10, 2026Episode 5334 min

The Architect's Guide to the AI Era • Luca Mezzalira & Teena Idnani

This interview was recorded for GOTO Unscripted.https://gotopia.techLuca Mezzalira - Solutions Architect, Consultant, International Speaker & Author of "Building Micro-Frontends"Teena Idnani - Senior Solutions Architect at Microsoft & Woman in Tech LeaderCheck out more here:https://gotopia.tech/articles/447RESOURCESLucahttps://www.buildingmicrofrontends.comhttps://twitter.com/lucamezzalirahttps://www.linkedin.com/in/lucamezzalirahttps://linktr.ee/lucamezzalirahttps://lucamezzalira.comTeenahttps://www.linkedin.com/in/teenaidnaniDESCRIPTIONLuca Mezzalira and Teena Idnani open with a clear framing: AI is accelerating certain tasks architects do, but the fundamentals — understanding context, connecting technical decisions to business capability, designing for evolutionary systems — are unchanged and arguably more important than ever. Luca identifies what he calls the shift from a T-shaped to an "M-shaped" architect: broader and deeper simultaneously, using AI as a research accelerator that collapses days of trade-off analysis into hours. Both agree that the biggest current risk isn't that AI will replace architects, but that AI-generated code can look convincingly correct and pass initial testing while concealing edge-case failures that only surface under load, regulatory audit, or upstream change — particularly dangerous in regulated industries like finance.The conversation sharpens around what architects must double down on to stay relevant. Luca advocates for merging deterministic and probabilistic systems through harness engineering — combining linters, static analysis, and deterministic guardrails with AI code assistants to produce more predictable outcomes. More broadly, both conclude that empathy is now a core technical skill: the architect's real job is riding the "elevator" between the engine room and the C-suite, translating freely in both directions. Luca's rule of thumb has shifted from 70% people and context, 30% technical — to nearly 90/10 in the AI era. The competitive edge for architects, they agree, is not in generating code, but in knowing which problems are worth solving and why.RECOMMENDED BOOKSLuca Mezzalira • Building Micro-Frontends • https://amzn.to/4ekqV5YLuca Mezzalira • Front-End Reactive Architectures • https://amzn.to/43a8VVJGregor Hohpe • The Software Architect Elevator • https://amzn.to/3F6d2axGregor Hohpe • Enterprise Integration Patterns, Vol 2 • https://amzn.to/3TNedQ3BlueskyInstagramLinkedInFacebookCHANNEL 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!

July 3, 2026Episode 5222 min

Model-Based Systems Eng. & Requirements Definition • Dennis Hansen & Jorge Orellana

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubDennis Hansen - Air Force Veteran, Chief Systems Engineer & Author of "Model-Based Systems Engineering and Requirements Definition"Jorge Orellana - Model Based Systems Engineer at IERUS Technologies & CEO & Founder at SCATTERBRAINSCheck out more here:https://gotopia.tech/episodes/445RESOURCESJorgehttps://www.linkedin.com/in/jorge-orellana-0b729129DESCRIPTIONDennis Hansen brings over six decades of systems engineering experience to this GOTO Book Club conversation — from Air Force airborne navigation technician to Chief Systems Engineer at L3Harris on programs including the complete rebuild of the GOES-R ground system for NOAA and NASA. His book argues that the fundamental failure mode in complex system development is the same every time: requirements are defined too loosely, too late, or across multiple model layers simultaneously. He structures the approach using an onion model — a layering framework he was taught by a Motorola engineer in 1961 — where each layer (mission, capabilities, activities, technical requirements, specifications) must be completed before the next is begun. Skipping layers or trying to do two at once invariably produces excess or faulty requirements that surface as expensive failures during system testing, or worse, after deployment.The second half of the conversation focuses on why modeling tools are databases, not drawing programs — a distinction Dennis considers critical. Every element in the model carries its associated requirements and the reasoning behind design decisions, which means that when you return to work after a weekend, you don't lose hours reconstructing your thinking. More importantly, when change requests arrive — and they always do — a maintained model lets you trace the impact backwards through the system and understand exactly what has to be modified, rather than slapping on a fix that creates five new problems. Dennis's closing advice is the thread that runs through the entire book: collaborate at every stage, every discipline working together rather than in silos, and define things properly upfront. Everything else follows from that.RECOMMENDED BOOKSDennis Hansen • Model-Based Systems Engineering and Requirements Definition • https://amzn.to/4e6IiqJKossiakoff, Seymour, Flanigan & Biemer • Systems Engineering Principles and Practice • https://amzn.to/4a7Elj9Dr. Bruce Powel Douglass • Agile Model-Based Systems Engineering Cookbook • https://amzn.to/4wYnj12BlueskyInstagramLinkedInFacebookCHANNEL 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!

June 26, 2026Episode 5132 min

Sovereign Cloud: Who Really Owns Your Infrastructure? • Jake Warner & Charles Humble

This interview was recorded for GOTO Unscripted in May 2026.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/445Jake Warner - Co-Founder & CEO at Cycle @JakeWarner Charles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESJakehttps://bsky.app/profile/jakewarner.comhttps://x.com/jakewarnerhttps://github.com/JakeWarnerhttps://www.linkedin.com/in/jakewarnerhttps://jakewarner.comCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comDESCRIPTIONJake Warner, co-founder and CEO of Cycle.io, traces a pattern he's watched repeat itself since his OpenStack days: a new orchestration technology arrives, developers adopt it enthusiastically, it grows in complexity, and organizations eventually ask whether managing it is really a core competency. He made a decade-long bet that Kubernetes would follow the same arc — and built Cycle as the answer: a distributed control plane that lets companies own their own infrastructure and compute while still getting a clean, platform-like experience on top of it. The key design principle is a high ceiling without sacrificing simplicity — companies shouldn't have to re-platform every time they grow, and they shouldn't have to give up infrastructure ownership to get ease of use.The conversation then pivots to Sovereign Cloud, which Jake frames not as a niche regulatory concern but as a fundamental trust and ownership question. He draws attention to a risk many organizations underestimate: the control plane itself. Unlike many platforms where the control plane is a single point of failure and a blackbox, Cycle's architecture ensures that even if the control plane goes down, customer infrastructure keeps running — servers maintain their own manifests and restart containers independently. Looking ahead, Jake expects more regions and countries to build their own cloud equivalents, driven by privacy concerns, data residency laws, and geopolitical pressures that are accelerating faster than the technology is.His conclusion: the organizations that handed AWS all the keys are beginning to realize the cost — and the industry is correcting.RECOMMENDED BOOKSAlan Hamilton • Sovereign Cloud Operations • https://amzn.to/4dqYAe4Leonard J. Horta • The Cloud Exit Strategy • https://amzn.to/4dXqeiNCharles Curry & Tanessa Curry • Cooling the Cloud • https://amzn.to/4a0d4iALiz Rice • Container Security • https://amzn.to/3oU4iJeLiz Rice • Kubernetes Security • https://www.oreilly.com/library/view/kubernetes-security/9781492039075BlueskyInstagramLinkedInFacebookCHANNEL 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!

June 23, 2026Episode 5042 min

Dungeons, Dragons & Developers • Matt Brunt

This presentation was recorded at YOW! 2025.https://yowcon.comMatt Brunt - Dungeon Master & Team TinkererRESOURCEShttps://bsky.app/profile/brunty.mehttps://mastodon.social/@bruntyhttps://github.com/Bruntyhttps://www.linkedin.com/in/mattbrunthttps://brunty.meABSTRACTYou enter the dungeon, as the echoes of your footsteps sound around you, something catches your eye - is that… oh, oh no.You grab your trusty sword and with your fellow adventurers, you seek to overcome the mighty challenge that lays ahead of you: building software.This talk is a look at some of the parallels between Dungeons and Dragons, and software development.We’ll see how lessons learned through delving into dungeons and fighting monsters with a party of adventurers can help teams of developers when building software in the real world.Are you ready to join me in a mighty quest for better software? [...]Download slides and read the full abstract here:https://yowcon.com/brisbane-2025/sessions/3641RECOMMENDED BOOKSHeidi Helfand • Dynamic Reteaming • https://amzn.to/3Fvu5BAHeidi Helfand • How to Change Your Teams • https://leanpub.com/DRTGuideCarl Larson & Frank M J LaFasto • Teamwork • https://amzn.to/4cFWseQGene Kim & Steve Spear • Wiring the Winning Organization • https://amzn.to/3QJcfBpBlueskyInstagramLinkedInFacebookCHANNEL 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!

June 19, 2026Episode 4945 min

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!

Is this your show?

Claim this listing to keep it up to date, reach guests who want to pitch you, and manage bookings with Guestify.

Claim this listing

More Technology podcasts

Earth Notes

Earth Notes / Damon Hart-Davis

Technology

The Civil Engineering Podcast

Anthony Fasano, PE, AEC PM, F. ASCE and James Taylor, JR., P.E.

BusinessTechnologyInterviews guests