Advertise on podcast: GOTO - The Brightest Minds in Tech

This presentation was recorded at GOTO Copenhagen 2025. https://gotocph.com Kent Beck - Software Engineer & Creator of Extreme Programming RESOURCES https://bsky.app/profile/kentbeck.bsky.social https://www.kentbeck.com https://github.com/KentBeck https://twitter.com/KentBeck https://www.linkedin.com/in/kentbeck https://tidyfirst.substack.com/about ABSTRACT So close and yet so far. We see similar behaviors in The Forest & The Desert, but with opposite meanings. Similar words but opposite meanings. Superficially similar goals but working out at completely different scales. What is The Forest? What is The Desert? Why are they so different, despite the similarities? And how can we get from crumbs to cake and stay there? [...] Download slides and read the full abstract here: https://gotocph.com/2025/sessions/3659 RECOMMENDED BOOKS Kent Beck • Tidy First? • https://amzn.to/4gscjjK Kent Beck & Cynthia Andres • Extreme Programming Explained • https://amzn.to/3sBASDG Kent Beck • Test Driven Development • https://amzn.to/3U4AXLs Kent Beck, Fowler, John, William, Don & Gamma • Refactoring • https://amzn.to/3SFBYbN Kent Beck • Implementation Patterns • https://amzn.to/3sBlCGL Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This Q&A session was recorded at GOTO Copenhagen 2025. https://gotocph.com Joanna Bryson - Professor of Ethics and Technology, Responsible Data Science for Human Development RESOURCES https://bsky.app/profile/j2bryson.bsky.social https://mastodon.social/@j2bryson https://twitter.com/j2bryson https://www.linkedin.com/in/bryson https://joanna-bryson.blogspot.com Links https://digital-markets-act.ec.europa.eu/index_en DESCRIPTION Joanna Bryson challenges many popular assumptions about AI and AGI. She argues that current generative AI systems are not autonomous intelligences but powerful tools that compress and reproduce human cultural knowledge at scale. While these systems can appear intelligent, they remain dependent on human-created data, corporate incentives, and carefully engineered guardrails. Bryson cautions against anthropomorphizing AI and emphasizes that many concerns about AI stem from misunderstandings about how these systems actually work. The discussion ultimately centers on responsibility and governance. Bryson argues that transparency, accountability, and democratic oversight matter far more than debates about machine consciousness. Whether discussing AI companions, recommendation algorithms, open-source models, regulation, or AI-assisted software development, her conclusion remains consistent: technology is not destiny. Engineers, companies, policymakers, and citizens all have agency in shaping how AI is deployed, regulated, and integrated into society. [...] Read the full abstract here: https://gotocph.com/2025/sessions/3783 RECOMMENDED BOOKS Chris Miller • Chip War • https://amzn.to/4aBCUKT Henry Farrell & Abraham Newman • Underground Empire • https://amzn.to/3YdXdGX Phil Winder • Reinforcement Learning • https://amzn.to/3t1S1VZ Alex Castrounis • AI for People and Business • https://amzn.to/3NYKKTo Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Check out more here: https://gotopia.tech/episodes/451 Ajay 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" RESOURCES Ajay https://www.linkedin.com/in/chankramath https://github.com/achankra https://x.com/ajchantw https://chankramath.com https://platformetrics.com Kaspar https://www.linkedin.com/in/kvgruenberg https://github.com/Kasparvongruenberg https://kasparvongruenberg.com Links https://peh-packt.platformetrics.com DESCRIPTION Ajay 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 BOOKS Ajay Chankramath • The Platform Engineer's Handbook • https://amzn.to/4eCSibM Ajay Chankramath & Eamonn Ryan • Domain-Driven Platform Engineering • https://amzn.to/3TdiC3J Chankramath, Cheneweth, Oliver & Alvarez • Effective Platform Engineering • https://amzn.to/3OnxN8i Kaspar von Grünberg & Luca Galante • Thinking in Plat­forms • https://weaveintelligence.io/thinking-in-platforms-book Gregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdb Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO State of the Art in April 2026. https://gotopia.tech Read the full transcription of this interview here: https://gotopia.tech/articles/450 Abby Bangser - Principal Engineer at Syntasso & Team Topologies Advocate Charles Humble - Freelance Techie, Podcaster, Editor, Author & Consultant RESOURCES Abby https://bsky.app/profile/abangser.bsky.social https://twitter.com/a_bangser https://github.com/abangser https://www.linkedin.com/in/abbybangser https://www.syntasso.io/members-area/abby/profile Charles https://bsky.app/profile/charleshumble.bsky.social https://linkedin.com/in/charleshumble https://mastodon.social/@charleshumble https://conissaunce.com Links https://blog.container-solutions.com/paula-kennedy-on-platform-team-responsibilities-patterns-and-anti-patterns http://sites.libsyn.com/406853/syntasso-coo-paula-kennedy-on-platform-team-responsibilities-patterns-and-anti-patterns https://www.oreilly.com/library/view/platform-as-a/0642572243777 https://github.com/Cloud-Native-Platform-Engineering/cnpe-community/issues/79 https://www.kratix.io https://leaddev.com/ai/nobody-knows-what-programming-will-look-like-in-two-years https://leaddev.com/ai/shipping-faster-thinking-less-the-ai-code-verification-trap https://www.cncf.io/blog/2023/11/20/announcing-the-platform-engineering-maturity-model https://platformengineering.com/features/portals-and-pipelines-arent-enough-avoiding-the-platform-facade DESCRIPTION Abby 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 BOOKS Chankramath, Cheneweth, Oliver & Alvarez • Effective Platform Engineering • https://amzn.to/3OnxN8i Gregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdb Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Check out more here: https://gotopia.tech/episodes/449 Simon Brown - Author & Creator of "The C4 Model" Susanne Kaiser - Independent Tech Consultant & Author of "Architecture for Flow" RESOURCES Simon https://simonbrown.je https://bsky.app/profile/simonbrown.je https://twitter.com/simonbrown https://linkedin.com/in/simonbrownjersey https://c4model.com Susanne https://bsky.app/profile/suksr.bsky.social https://mastodon.social/@suksr https://www.linkedin.com/in/susannekaiser1 https://susannekaiser.net Links https://structurizr.com DESCRIPTION Simon 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 BOOKS Simon Brown • The C4 Model • https://amzn.to/4xB9V33 Susanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCc Nick Rozanski &, Eóin Woods • Software Systems Architecture • https://amzn.to/4cOLtTv van Kelle, Verschatse &Baas-Schwegler • Collaborative Software Design • https://amzn.to/4iv0N8I Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded at GOTO Copenhagen 2025. https://gotocph.com Adrian Mouat - Developer Relations at Chainguard & Author of "Using Docker" Kief Morris - Author of "Infrastructure as Code" & Distinguished Engineer at Thoughtworks Sam Newman - Author of "Building Microservices" & "Monolith to Microservices" RESOURCES Adrian https://bsky.app/profile/adrianmouat.com https://twitter.com/adrianmouat https://github.com/amouat https://linkedin.com/in/adrianmouat http://www.adrianmouat.com Kief https://bsky.app/profile/kief.com https://twitter.com/kief https://github.com/kief https://www.linkedin.com/in/kiefmorris https://infrastructure-as-code.com https://kief.com Sam https://twitter.com/samnewman https://www.linkedin.com/in/samnewman http://samnewman.io http://samnewman.io/blog https://github.com/snewman ABSTRACT In 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/3938 RECOMMENDED BOOKS Adrian Mouat • Using Docker • https://amzn.to/3PEYIJL Liz Rice • Container Security • https://amzn.to/3oU4iJe Kief Morris • Infrastructure as Code • https://amzn.to/4e6EBQc Sam Newman • Building Resilient Distributed Systems • https://www.oreilly.com/library/view/building-resilient-distributed/9781098163532 Sam Newman • Monolith to Microservices • https://amzn.to/2Nml96E Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Elisabeth 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 & Consultant Check out more here: https://gotopia.tech/episodes/448 RESOURCES Elisabeth https://ruby.social/@testobsessed https://github.com/testobsessed https://www.linkedin.com/in/testobsessed https://curiousduck.io Joel https://mastodon.social/@joeltosi https://www.linkedin.com/in/joel-tosi-531a3b Charles https://bsky.app/profile/charleshumble.bsky.social https://linkedin.com/in/charleshumble https://mastodon.social/@charleshumble https://conissaunce.com Links https://ruthmalan.com http://www.ask-force.org/web/Discourse/Rittel-Dilemmas-General-Theory-Planning-1973.pdf DESCRIPTION Elisabeth 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 BOOKS Elisabeth Hendrickson & Joel Tosi • Signals & Levers • https://amzn.to/4g6Fb3C Diana Montalion • Learning Systems Thinking • https://amzn.to/3ZpycdJ Don Norman • The Design of Everyday Things • https://amzn.to/4fV6QVl Gene Kim • The Unicorn Project • https://amzn.to/3woXQDz Gene Kim, Kevin Behr & George Spafford • The Phoenix Project • https://amzn.to/3X9cYxa Peter Degrace & Leslie Hulet Stahl • Wicked Problems, Righteous Solutions • https://amzn.to/3ScP0D9 Frederick Brooks Jr. • The Mythical Man-Month • https://amzn.to/4gd10OV Gerald Weinberg • An Introduction to General Systems Thinking • https://amzn.to/4dZCsaO Donella H. Meadows • Thinking in Systems • https://amzn.to/3XtqYCV Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted. https://gotopia.tech Luca Mezzalira - Solutions Architect, Consultant, International Speaker & Author of "Building Micro-Frontends" Teena Idnani - Senior Solutions Architect at Microsoft & Woman in Tech Leader Check out more here: https://gotopia.tech/articles/447 RESOURCES Luca https://www.buildingmicrofrontends.com https://twitter.com/lucamezzalira https://www.linkedin.com/in/lucamezzalira https://linktr.ee/lucamezzalira https://lucamezzalira.com Teena https://www.linkedin.com/in/teenaidnani DESCRIPTION Luca 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 BOOKS Luca Mezzalira • Building Micro-Frontends • https://amzn.to/4ekqV5Y Luca Mezzalira • Front-End Reactive Architectures • https://amzn.to/43a8VVJ Gregor Hohpe • The Software Architect Elevator • https://amzn.to/3F6d2ax Gregor Hohpe • Enterprise Integration Patterns, Vol 2 • https://amzn.to/3TNedQ3 Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Dennis 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 SCATTERBRAINS Check out more here: https://gotopia.tech/episodes/445 RESOURCES Jorge https://www.linkedin.com/in/jorge-orellana-0b729129 DESCRIPTION Dennis 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 BOOKS Dennis Hansen • Model-Based Systems Engineering and Requirements Definition • https://amzn.to/4e6IiqJ Kossiakoff, Seymour, Flanigan & Biemer • Systems Engineering Principles and Practice • https://amzn.to/4a7Elj9 Dr. Bruce Powel Douglass • Agile Model-Based Systems Engineering Cookbook • https://amzn.to/4wYnj12 Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for GOTO Unscripted in May 2026. https://gotopia.tech Read the full transcription of this interview here: https://gotopia.tech/articles/445 Jake Warner - Co-Founder & CEO at Cycle  @JakeWarner  Charles Humble - Freelance Techie, Podcaster, Editor, Author & Consultant RESOURCES Jake https://bsky.app/profile/jakewarner.com https://x.com/jakewarner https://github.com/JakeWarner https://www.linkedin.com/in/jakewarner https://jakewarner.com Charles https://bsky.app/profile/charleshumble.bsky.social https://linkedin.com/in/charleshumble https://mastodon.social/@charleshumble https://conissaunce.com DESCRIPTION Jake 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 BOOKS Alan Hamilton • Sovereign Cloud Operations • https://amzn.to/4dqYAe4 Leonard J. Horta • The Cloud Exit Strategy • https://amzn.to/4dXqeiN Charles Curry & Tanessa Curry • Cooling the Cloud • https://amzn.to/4a0d4iA Liz Rice • Container Security • https://amzn.to/3oU4iJe Liz Rice • Kubernetes Security • https://www.oreilly.com/library/view/kubernetes-security/9781492039075 Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This presentation was recorded at YOW! 2025. https://yowcon.com Matt Brunt - Dungeon Master & Team Tinkerer RESOURCES https://bsky.app/profile/brunty.me https://mastodon.social/@brunty https://github.com/Brunty https://www.linkedin.com/in/mattbrunt https://brunty.me ABSTRACT You 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/3641 RECOMMENDED BOOKS Heidi Helfand • Dynamic Reteaming • https://amzn.to/3Fvu5BA Heidi Helfand • How to Change Your Teams • https://leanpub.com/DRTGuide Carl Larson & Frank M J LaFasto • Teamwork • https://amzn.to/4cFWseQ Gene Kim & Steve Spear • Wiring the Winning Organization • https://amzn.to/3QJcfBp Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This presentation was recorded at GOTO Copenhagen 2025. https://gotocph.com Abby Bangser - Principal Engineer at Syntasso & Team Topologies Advocate Dave Farley - Bestselling Author, Founder & Director of Continuous Delivery Ltd. RESOURCES Abby https://bsky.app/profile/abangser.bsky.social https://twitter.com/a_bangser https://github.com/abangser https://www.linkedin.com/in/abbybangser https://www.syntasso.io/members-area/abby/profile Dave https://bsky.app/profile/davefarley77.bsky.social https://www.continuous-delivery.co.uk https://linkedin.com/in/dave-farley-a67927 https://twitter.com/davefarley77 http://www.davefarley.net DESCRIPTION Dave 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/3779 RECOMMENDED BOOKS Kief Morris • Infrastructure as Code • https://amzn.to/4e6EBQc Matthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQ Dave Thomas • simplicity • https://amzn.to/43FghBJ Dave Farley & Jez Humble • Continuous Delivery • https://amzn.to/3ocIHwd David Farley • Modern Software Engineering • https://amzn.to/3GI468M Dave Farley • Continuous Delivery Pipelines • https://amzn.to/3rjetdi Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub Barry Feigenbaum - Retired Sr. Principal Software Engineer & Author of "Go for Java Programmers" Shon Saliga - IBM Storage Evangelist Check out more here: https://gotopia.tech/episodes/444 RESOURCES Barry https://www.linkedin.com/in/barryfeigenbaum Shon https://www.linkedin.com/in/shon-saliga-32336b2 DESCRIPTION Dr. Barry Feigenbaum — an IBM, Amazon and Dell veteran with a PhD in Computer Engineering and decades of Java experience — spent time working with Go on microservices and liked it enough to write the book he wished had existed when he made the switch. In this GOTO Book Club episode with longtime colleague Shon Saliga, he walks through the core contrasts: Go is a compiled language that targets a narrower domain than Java — primarily command-line tools and web servers — but excels there with smaller binaries, faster startup, and dramatically lower container overhead. Concurrency is the headline difference: Go's goroutines are far lighter than Java threads, and its channel-based communication model sidesteps many of the problems that make concurrent Java code hard to reason about. The error handling conversation is particularly illuminating. Java's exception mechanism, while powerful, encourages developers to overuse it for ordinary error reporting — Go simply doesn't allow that by design. Errors in Go are return values, not throws; panics are reserved for truly catastrophic situations. Similarly, Go's implicit interfaces (if you implement the methods, you implement the interface — no declaration required) give the language a flexibility that feels alien to Java developers at first but becomes a strength quickly. Barry's conclusion is clear: for greenfield servers and containerized microservices, Go is worth serious consideration — and for Java developers willing to reset a few mental models, the transition is more tractable than it looks. RECOMMENDED BOOKS Barry Feigenbaum • Go for Java Programmers • https://amzn.to/4uRL3li Ken Christopher, Barry Feigenbaum, Shon Salig • DOS 5: The Basic • https://amzn.to/4tKDVGs A N M Bazlur Rahman • Modern Concurrency in Java • https://amzn.to/42w8cOk Ben Evans & Jim Gough • Optimizing Cloud Native Java • https://amzn.to/41nivD9 Ian F. Darwin • Java Cookbook 5th ed. • https://amzn.to/3QH0NZy Victor Grazi & Jeanne Boyarsky • Real-World Java • https://amzn.to/4oCEeBR Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This conversation was recorded at GOTO Copenhagen 2025. https://gotocph.com Sarah Wells - Independent Consultant & Author of "Enabling Microservice Success" Patrick Kua - Founder of the Tech Lead Academy Daniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & Associates RESOURCES Sarah https://bsky.app/profile/sarahjwells.bsky.social https://linkedin.com/in/sarahjwells1 https://www.sarahwells.dev Patrick https://hachyderm.io/@patkua https://twitter.com/patkua https://www.linkedin.com/in/patkua https://github.com/thekua https://patkua.com Daniel https://bsky.app/profile/tastapod.com https://www.linkedin.com/in/tastapod https://github.com/tastapod https://mastodon.social/@tastapod http://dannorth.net/blog DESCRIPTION Engineering leadership becomes significantly more complex in times of uncertainty. This conversation highlights how leaders must shift from rigid plans to adaptable thinking—balancing delivery, team well-being, and long-term direction while navigating constant change. A key takeaway is that great leadership isn’t about having all the answers, but about creating clarity, trust, and resilience within teams. The speakers emphasize communication, context-awareness, and empowering engineers as the foundation for thriving—even when everything feels unstable. RECOMMENDED BOOKS Sarah Wells • Enabling Microservice Success • https://amzn.to/4aa8xrv Patrick Kua • Talking with Tech Leads • https://amzn.to/3ECO3xB Patrick Kua • The Retrospective Handbook • https://amzn.to/4jpxxQN Neal Ford, Rebecca Parsons & Patrick Kua • Building Evolutionary Architectures • https://amzn.to/42qXJV2 Mary Lynn Manns & Linda Rising • Fearless Change • https://amzn.to/49uuune Mary Lynn Manns & Linda Rising • More Fearless Change • https://amzn.to/4tX6GAR Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

This interview was recorded for the GOTO Book Club. http://gotopia.tech/bookclub A N M Bazlur Rahman - Java Champion & Author of "Modern Concurrency in Java" Michael Redlich - Java Champion & Lead Java Queue News Editor at InfoQ Check out more here: https://gotopia.tech/episodes/443 RESOURCES Bazlur https://bsky.app/profile/bazlur.ca https://x.com/bazlur_rahman https://github.com/rokon12 https://www.linkedin.com/in/bazlur https://bio.site/bazlur https://bazlur.ca Michael https://twitter.com/mpredli https://github.com/mpredli01 https://www.linkedin.com/in/michael-redlich-13a966 https://about.me/mpredli DESCRIPTION In this GOTO Book Club episode, Java Champion A N M Bazlur Rahman joins host and fellow Java Champion Michael Redlich to discuss Modern Concurrency in Java — the first comprehensive update to Java concurrency literature in 20 years. Bazlur traces his motivation to the arrival of virtual threads in JDK 21, which he describes as a fundamental shift in Java's concurrency cost model: platform threads were expensive and scarce, demanding careful pooling; virtual threads are cheap, plentiful, and behave like ordinary threads from the developer's perspective, without requiring a new programming model. The book covers this evolution end-to-end, from the history of threads through to structured concurrency, scope values, and the modern frameworks that have already adopted virtual threads — most with a single config change. The conversation also takes a nuanced look at reactive programming's future. Bazlur's conclusion is that reactive remains compelling in specific contexts — event-driven streaming systems, architectures needing end-to-end back-pressure — but it's no longer the default answer to scalability. For most microservices doing blocking I/O, virtual threads are now the stronger default, and reactive becomes a deliberate architectural choice rather than an automatic one. The book's goal is to give developers both the conceptual grounding and the practical guidance to make that choice confidently — understanding the tool one level deep, so they can design better systems, not just configure their way through a framework. RECOMMENDED BOOKS A N M Bazlur Rahman • Modern Concurrency in Java • https://amzn.to/42w8cOk Ben Evans & Jim Gough • Optimizing Cloud Native Java • https://amzn.to/41nivD9 Ben Evans, Jason Clark & David Flanagan • Java in a Nutshell • https://amzn.to/43FDoMA Ian F. Darwin • Java Cookbook 5th ed. • https://amzn.to/3QH0NZy Victor Grazi & Jeanne Boyarsky • Real-World Java • https://amzn.to/4oCEeBR Bluesky Instagram LinkedIn Facebook CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket: gotopia.tech SUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!