Podcast appearances and mentions of jez humble

Sam Newman is the author of "Building Microservices" and "Monolith to Microservices", two of the most influential books on distributed systems design. He is an independent consultant and former ThoughtWorks technologist, he has spent decades helping organizations worldwide decompose monoliths, adopt cloud and CI/CD practices, and reason clearly about service boundaries. He is one of the most recognized voices on microservices and software architecture in the industry. So is AI really replacing software architects? Find out what Dave Farley and Sam Newman think about that in this episode of " The Engineering Room".-------------------------------------------------------------------------------Only Patreon supporters get to see the full length video episodes of "The Engineering Room” Sign up here: https://www.patreon.com/c/continuousdeliverySam Newman on "X" (formerly "Twitter"): https://x.com/samnewman?lang=en

Hosted by Dave Farley - co-author of Continuous Delivery (Jolt Award winner), author of Modern Software Engineering, and inventor of the Deployment Pipeline.David Yanacek is a Senior Principal Engineer at AWS and a lead advisor on the Agentic AI team, having played a foundational role in the development of DynamoDB and CloudWatch. He is currently a primary driver behind the Kiro IDE and Amazon's operational agents, specializing in building and operating resilient, high-scale distributed systems.David and Dave talk about the transition from simple AI code completion to autonomous agentic development and the fundamental engineering principles are more critical than ever in an era of AI-generated code.------------------------Only Patreon supporters get to see the full length video episodes of "The Engineering Room” Sign up here: https://www.patreon.com/c/continuousdeliveryLinkedIn David Yanacek - https://www.linkedin.com/in/david-yanacek/?isSelfProfile=falseEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0

Join Dave Farley — co-author of Continuous Delivery (Jolt Award winner), author of Modern Software Engineering, and inventor of the CD Deployment Pipeline - and guest Steve Freeman in this fascinating episode. Steve is a pioneer of the software craftsmanship movement and a foundational figure in the global Agile community. He is the co-author of the seminal book Growing Object-Oriented Software, Guided by Tests, a winner of the Gordon Pask Award, and the co-creator of JMock. With a PhD from Cambridge, Steve has spent decades refining the "London School" of TDD, shifting testing from a verification step to a profound tool for architectural design.----------------------------------------Only Patreon supporters get to see the full length video episodes of "The Engineering Room” Sign up here: https://www.patreon.com/c/continuousdeliveryLinkedIn Steve Freeman: https://www.linkedin.com/in/stevefreeman/Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0

This episode with Joachim Hill-Grannec asks: How do platforms bloat, and how do you keep them simple and fast with trunk-based dev and small batches? Which metrics prove it works—cycle time, uptime, or developer experience? Can security act as a partner that speeds delivery instead of a gate?   We are always happy to answer any questions, hear suggestions for new episodes, or hear from you, our listeners. DevSecOps Talks podcast LinkedIn page DevSecOps Talks podcast website DevSecOps Talks podcast YouTube channel Summary In this episode of DevSecOps Talks, Mattias speaks with Joachim Hill-Grannec, co-founder of Peltek, a boutique consulting firm specializing in high-availability, cloud-native infrastructure. Following up on a previous episode where Steve discussed cleaning up bloated platforms, Mattias and Joachim dig into why platforms get bloated in the first place and how platform teams should think when building from scratch. Their conversation spans cloud provider preferences, the primacy of cycle time, the danger of adding process in response to failure, and a strong argument for treating security and quality as enablers rather than gatekeepers. Key Topics Platform Teams Should Serve Delivery Teams Joachim frames the core question of platform engineering around who the platform is actually for. His answer is clear: the delivery teams are the client. Platform engineers should focus on making it easier for developers to ship products, not on making their own work more convenient. He connects this directly to platform bloat. In his experience, many platforms grow uncontrollably because platform engineers keep adding tools that help the platform team itself: "Look, I spent this week to make my job this much faster." But Joachim pushes back on this instinct — the platform team is an amplifier for the organization, and every addition should be evaluated by whether it helps a product get to production faster and gives developers better visibility into what they are working on. Choosing a Cloud Provider: Preferences vs. Reality The conversation briefly explores cloud provider choices. Joachim says GCP is his personal favorite from a developer perspective because of cleaner APIs and faster response times, though he acknowledges Google's tendency to discontinue services unexpectedly. He describes AWS as the market workhorse — mature, solid, and widely adopted, comparing it to "the Java of the land." Azure gets the coldest reception; both acknowledge it has improved over time, but Joachim says he still struggles whenever he is forced to use it. They observe that cloud choices are frequently made outside engineering. Finance teams, investors, and existing enterprise agreements often drive the decision more than technical fit. Joachim notes a common pairing: organizations using Google Workspace for productivity but AWS for cloud infrastructure, partly because the Entra ID (formerly Azure AD) integration with AWS Identity Center works more smoothly via SCIM than the equivalent Google Workspace setup, which requires a Lambda function to sync groups. Measuring Platform Success: Cycle Time Above All When Mattias asks how a team can tell whether a platform is actually successful, Joachim separates subjective and objective measures. On the subjective side, he points to developer happiness and developer experience (DX). Feedback from delivery teams matters, even if surveys are imperfect. On the objective side, his favorite metric is cycle time — specifically, the time from when code is ready to when it reaches production. He also mentions uptime and availability, but keeps returning to cycle time as the clearest indicator that a platform is helping teams deliver faster. This aligns with DORA research, which has consistently shown that deployment frequency and lead time for changes are strong predictors of overall software delivery performance. Start With a Highway to Production A major theme of the episode is that platforms should begin with the shortest possible route to production. Mattias calls this a "highway to production," and Joachim strongly agrees. For greenfield projects, Joachim favors extremely fast delivery at first — commit goes to production, commit goes to production — even with minimal process. As usage and risk increase, teams can gradually add automation, testing, and safeguards. The critical thing is to keep the flow and then ask "how do we make those steps faster?" as you add them, rather than letting each new step slow down the pipeline unchallenged. He also makes a strong case for tags and promotions over branch-based deployment, noting his instinctive reaction when someone asks "which branch are we deploying from?" is: "No branches — tags and promotions." The Trap of Slowing Down After Failure Joachim warns about a common and dangerous pattern: when a bug reaches production, the natural organizational reaction is not to fix the pipeline, but to add gates. A QA team does a full pass, a security audit is inserted, a manual review step appears. Each gate slows delivery, which leads to larger batches, which increases risk, which triggers even more controls. He sees this as a vicious cycle. Organizations that respond to incidents by slowing delivery actually get worse security, worse quality, and worse throughput over time. He references a study — likely the research behind the book Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim — showing that faster delivery correlates with better security and quality outcomes. The organizations adding Engineering Review Boards (ERBs) and Architecture Review Boards (ARBs) in the name of safety often do not measure the actual impact, so they never see that the controls are making things worse. Mattias connects this to AI-assisted development, where developers can now produce changes faster than ever. If the pipeline cannot keep up, the pile of unreleased changes grows, making each release riskier. Getting Buy-In: Start With Small Experiments Joachim does not recommend that a slow, process-heavy organization throw everything out overnight. Instead, he suggests starting with small experiments. Code promotions are a good entry point: teams can start producing artifacts more rapidly without changing how those artifacts are deployed. Once that works, the conversation shifts to delivering those artifacts faster. He finds starting on the artifact pipeline side produces quicker wins and more organizational buy-in than starting with the platform deployment side, which tends to be more intertwined and higher-risk to change. Guiding Principles Over a Rigid Golden Path Mattias questions the idea of a single "golden path," saying the term implies one rigid way of working. Joachim leans toward guiding principles instead. His strongest principle is simplicity — specifically, simplicity to understand, not necessarily simplicity to create. He references Rich Hickey's influential talk Simple Made Easy (from Strange Loop 2011), which distinguishes between things that are simple (not intertwined) and things that are easy (familiar or close at hand). Creating simple systems is hard work, but the payoff is systems that are easy to reason about, easy to change, and easy to secure. His second guiding principle is replaceability. When evaluating any tool in the platform, he asks: "How hard would it be to yank this out and replace it?" If swapping a component would be extremely difficult, that is a smell — it means the system has become too intertwined. Even with a tool as established as Argo CD, his team thinks about what it would look like to switch it out. Tooling Choices and Platform Foundations Joachim outlines the patterns his team typically uses when building platforms, organized into two paths: Delivery pipeline (artifact creation): - Trunk-based development over GitFlow - Release tags and promotions rather than branch-based deployment - Containerization early in the pipeline - Release Please for automated release management and changelogs - Renovate for dependency updates (used for production environment promotions from Helm charts and container images) Platform side (environment management): - Kubernetes-heavy, typically EKS on AWS - Karpenter for node scaling - AWS Load Balancer Controller only as a backing service for a separate ingress controller (not using ALB Ingress directly, due to its rough edges) - Argo CD for GitOps synchronization and deployment - Argo Image Updater for lower environments to pull latest images automatically - Helm for packaging, despite its learning curve He notes that NGINX Ingress Controller has been deprecated, so teams need to evaluate alternatives for their ingress layer. Developers Should Not Be Fully Shielded From Operations One of the more nuanced parts of the conversation is how much operational responsibility developers should have. Joachim rejects both extremes. He does not think every developer needs to know everything about infrastructure, but he has seen too many cases where developers completely isolated from runtime concerns make poor decisions — missing simple code changes that would make a system dramatically easier to deploy and operate. He advocates for transparency and collaboration. Platform repos should be open for anyone on the dev team to submit pull requests. When the platform team makes a change, they should pull in developers to work alongside them. This way, the delivery team gradually builds a deeper understanding of how the whole system works. Joachim loves the open-source maintainer model applied inside organizations: platform teams are maintainers of their areas, but anyone in the organization should be able to introduce change. He warns against building custom CLIs or heavy abstractions that create dependencies — if a developer wants to do something the CLI does not support, the platform team becomes a bottleneck. Mattias adds that opening up the platform to contributions also exposes assumptions. What feels easy to the person who built it may not be easy at all; it is just familiar. Outside contributors reveal where the system is actually hard to understand. Designers, Not Artists: Detaching Ego From Code Joachim shares an analogy he prefers over the common "developers as artists" framing. He sees developers more like designers than artists, because an artist's work is tied to their identity — they want it to endure. A designer, by contrast, creates something to serve a purpose and expects it to be replaced when something better comes along. He applies this to platforms and infrastructure: "I want my thing to get wiped out. If I build something, I want it to get removed eventually and have something better replace it." Organizations where ego is tied to specific systems or tools tend to resist change, which leads to the kind of dysfunction that keeps platforms bloated and brittle. Complexity Is the Enemy of Security Mattias raises the difficulty of maintaining complex security setups over time, especially when the original experts leave. Joachim responds firmly: complexity is anti-security. If people cannot comprehend a system, they cannot secure it well. He acknowledges that some problems are genuinely hard, but argues that much of the complexity engineers create is unnecessary — driven by ego rather than need. "The really smart people are the ones that create simple things," he says, wishing the industry would redirect its narrative from admiring complicated systems to admiring simple ones. Security and QA as Internal Consulting, Not Gatekeeping Joachim draws a parallel between security and QA. He dislikes calling a team "the quality team," preferring "verification" — they are one component of quality, not the entirety of it. Similarly, security is not one team's responsibility; it spans product design, development practices, tooling, and operations. His ideal model is for security and QA teams to operate as internal consultants whose goal is to reduce risk and improve the overall system — not to catch every possible issue at any cost. The framing matters: if a security team's mandate is simply "block all security issues," the logical conclusion is to stop shipping or delete the product entirely. That may be technically secure, but it is useless. He frames security as risk management: "Security is a risk management process, not just security for the sake of security. You're managing the risk to the business." The goal should be to deliver faster and more securely — an "and," not an "or." Mattias recalls a PCI DSS consultant joking over drinks that a system being down is perfectly compliant — no one can steal card numbers if the system is unavailable. The joke lands because it exposes exactly the broken incentive Joachim describes. Business Value as the Unifying Frame The episode closes by tying everything back to business outcomes. Joachim argues that speed and security are not opposites; both contribute to business value. Fast delivery creates value directly, while security reduces business risk — and risk management is itself a business operation. He explains why focusing on the highest-impact business bottleneck first builds trust. When you hit the big items first, you earn credibility, and subsequent changes become easier to justify. For example, one of his clients has a security group that is the slowest part of their organization. Speeding up that security process would have a massive impact on business delivery — more than optimizing the artifact pipeline. Mattias reflects that he used to see platform work as separate from business concerns — "I don't care about the business, I'm here to build a platform for developers." Looking back, he would reframe that: using business impact as the measure of platform success does not mean abandoning the focus on developers, it means having a clearer way to prioritize and demonstrate value. Highlights Joachim on platform bloat: "Your job is not to make your job faster and easier — you're an amplifier to the organization." Joachim on his favorite metric: "Cycle time is my favorite metric. I love cycle time metrics." Joachim on deployment strategy: "No branches, no branches — tags and promotions." Mattias on platform design: He calls the ideal early setup a "highway to production." Joachim on simplicity vs. ease: He references Rich Hickey's Simple Made Easy talk — "It's very hard to create simple systems that are easy to reason about. And it's very easy to create systems that are very hard to reason about." Joachim on replaceability: "If swapping a tool out would be extremely hard, that's a pretty big smell." Joachim on complexity and security: "If it's complicated, you just can't keep all the context together. Simple systems are much easier to be secure." Joachim on engineering ego: "I don't particularly like the aspect of [developers as] artists... I want my thing to get wiped out. I want it to get removed eventually and have something better replace it." He prefers the analogy of designers over artists, because artists tie their identity to their creations. Joachim on security as a blocker: "If their goal is we are going to block every security issue, the best way to do that is delete your product." Spicy cloud takes: Joachim calls GCP his favorite cloud for developers, compares AWS to "the Java of the land," and says he still struggles every time he is forced to use Azure. PCI DSS dark humor: Mattias recalls a consultant joking that a downed system is perfectly compliant — you cannot steal card numbers from a system that is not running. Joachim on the slow-down trap: Organizations add ERBs, ARBs, and manual security gates after incidents, but "the faster you can deliver, you actually get better security, better quality, and better throughput — and the more you slow it down, you go the opposite." Resources Simple Made Easy by Rich Hickey (InfoQ) — The influential 2011 talk Joachim references on distinguishing simplicity from ease in system design. DORA Metrics: The Four Keys — The research framework behind cycle time, deployment frequency, and the finding that speed and stability are not tradeoffs. Trunk Based Development — A comprehensive guide to the branching strategy Joachim recommends over GitFlow. Argo CD — Declarative GitOps for Kubernetes — The GitOps tool Joachim's team uses for cluster synchronization and deployment. Release Please (GitHub) — Google's tool for automated release management based on conventional commits, used by Joachim's team for tag-based promotions. Karpenter — Kubernetes Node Autoscaler — The node autoscaler Joachim's team uses with EKS for fast, flexible scaling. Renovate — Automated Dependency Updates — The dependency management bot Joachim uses for both build dependencies and production environment promotions.

In this episode of The Engineering Room, Dave Farley welcomes Dan Abel, a veteran technical leader with over 30 years of experience, to explore the nuances of engineering leadership and the evolution of high-performing teams.This episode is a masterclass in dismantling silos, reducing cognitive load through platform engineering, and aligning technical excellence with core business values.---------------Dan Abel LinkedIn: https://www.linkedin.com/in/daniel-abel/Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Only Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdelivery

This interview was recorded for GOTO Unscripted.https://gotopia.techCheck out more here:https://gotopia.tech/articles/417Olaf Molenveld - Technology Advisor at CircleCIJulian Wood - Serverless Developer Advocate at AWSRESOURCESOlafhttps://x.com/olafmolenveldhttps://medium.com/@olafmolenveldhttps://www.linkedin.com/in/olafmolenveldJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttps://github.com/julianwoodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodDESCRIPTIONCircleCI's Technology Advisor Olaf Molenveld discusses the evolution of CI/CD practices with AWS's Julian Wood. They explore how modern software delivery has transformed from simple monolithic deployments to complex microservices ecosystems, drawing parallels between managing production code and managing the "factory" that produces it.The discussion covers optimization strategies, the balance between local and remote development, platform engineering trends, and how AI is reshaping DevOps practices. Olaf emphasizes that getting software into users' hands is as critical as writing it, and shares how teams can leverage observability, right-sizing, and intelligent automation to improve their delivery pipelines.RECOMMENDED BOOKSDavid Farley • Continuous Delivery Pipelines • https://leanpub.com/cd-pipelinesJez Humble & Dave Farley • Continuous Delivery • https://amzn.to/3ocIHwdNicole Forsgren, Jez Humble & Gene Kim • Accelerate • https://amzn.to/442Rep0Kim, Humble, Debois, Willis & Forsgren • The DevOps Handbook • https://amzn.to/47oAf3lLauren Maffeo • Designing Data Governance from the Ground Up • https://amzn.to/3QhIlnVRoy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNBBurns, Beda & Hightower • Kubernetes: Up & Running • https://amzn.to/3sueuuIGojko Adzic • Lizard Optimization • https://leanpub.com/lizardoptimizationGregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdbBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

Mathias is Head of Data for Marketing at N26, the Berlin-based neobank valued at over $9 billion. He joined as a Senior Data Analyst in May 2020 and has since scaled the team to 12 people.We cover :

This interview was recorded for GOTO State of the Art in October 2025.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/415Nathen Harvey - DORA Lead, Product Manager at Google Cloud & AuthorCharles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESNathenhttps://bsky.app/profile/nathenharvey.bsky.socialhttps://x.com/nathenharveyhttps://github.com/nathenharveyhttps://www.linkedin.com/in/nathenhttps://linktr.ee/nathenharveyhttp://nathenharvey.comCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://dora.devhttps://dora.dev/research/2025/dora-reporthttps://dora.dev/research/2024/dora-reporthttps://thenewstack.io/ebooks/kubernetes/kubernetes-at-the-edge-container-orchestration-at-scaleDESCRIPTIONCharles Humble speaks with Nathen Harvey, leader of Google's DORA research team, about the real impact of AI on software development.Drawing from surveys of nearly 5,000 practitioners, Nathen reveals a surprising finding: increased AI adoption initially correlates with decreased stability and throughput - the very metrics teams have optimized for decades. The conversation explores why this happens, what capabilities organizations need before scaling AI adoption, and how AI acts as an amplifier of existing systems rather than a silver bullet.Nathen introduces DORA's seven AI capabilities model and discusses critical issues around trust, documentation, skill devaluation, and the future of software delivery in an AI-native world.RECOMMENDED BOOKSEmily Freeman & Nathen Harvey • 97 Things Every Cloud Engineer Should Know • https://amzn.to/3UlWBLtCharles Humble • Professional Skills for Software Engineers • https://www.conissaunce.com/professional-skills-shortcutNicole Forsgren, Jez Humble & Gene Kim • Accelerate • https://amzn.to/442Rep0Kim, Humble, Debois, Willis & Forsgren • The DevOps Handbook • https://amzn.to/47oAf3lJez Humble & David Farley • Continuous Delivery • https://amzn.to/452ZRkyJez Humble, Joanne Molesky & Barry O'Reilly • Lean Enterprise • https://amzn.to/47pcOXDAdrienne Braganza Tacke • "Looks Good to Me": Constructive Code Reviews • https://amzn.to/3E75XrDYevgeniy Brikman • Fundamentals of DevOps and Software Delivery • https://amzn.to/3WMPMFUBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

In this episode of The Engineering Room, Dave Farley talks with with Gene Kim, the bestselling author of "The Phoenix Project," "The Unicorn Project," and "Accelerate: The Science of Lean Software and DevOps." They discuss the controversial topic of "Vibe Coding," a concept Gene explored in his recent collaboration with Steve Yegge. While Dave initially described Vibe Coding as "one of the worst ideas of 2025," this conversation unpacks whether AI actually represents a fundamental shift in how we build software.----------------------Gene Kim LinkedIn https://www.linkedin.com/in/realgenekim/Gene Kim ''X'' (formerly "'Twitter") https://x.com/@RealGeneKimEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Only Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdelivery

What does it truly take to build a high-performing software team? Is it about hiring the legendary "10x engineer," or is it about crafting the right environment?In this episode of The Engineering Room, Dave Farley is joined by Charity Majors, CTO and Co-founder of Honeycomb and co-author of Observability Engineering, for an unvarnished look at the reality of modern software development.-----------------------------------------------Charity Majors LinkedIn https://www.linkedin.com/in/charity-majors/Charity Majors Website https://charity.wtf/ Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Only Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdelivery

This interview was recorded at GOTO Copenhagen 2024.https://gotocph.comDaniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & AssociatesKevlin Henney - Consultant, Programmer, Keynote Speaker, Technologist, Trainer & WriterRESOURCESDanielhttps://bsky.app/profile/tastapod.comhttps://twitter.com/tastapodhttps://www.linkedin.com/in/tastapodhttps://github.com/tastapodhttps://mastodon.social/@tastapodhttp://dannorth.net/blogKevlinhttps://bsky.app/profile/kevlin.bsky.socialhttps://about.me/kevlinhttps://twitter.com/KevlinHenneyhttps://linkedin.com/in/kevlinhttps://instagram.com/kevlin.henneyhttps://kevlinhenney.medium.comLinkshttps://jaoo.dk/jaoo2004/index2.jsphttps://jaoo.dk/archivesRECOMMENDED BOOKSJez Humble & David Farley • Continuous Delivery • https://amzn.to/452ZRkyNicole Forsgren, Jez Humble & Gene Kim • Accelerate • https://amzn.to/442Rep0Kevlin Henney & Trisha Gee • 97 Things Every Java Programmer Should Know • https://amzn.to/3kiTwJJKevlin Henney • 97 Things Every Programmer Should Know • https://amzn.to/2Yahf9UHenney & Monson-Haefel • 97 Things Every Software Architect Should Know • https://amzn.to/3pZuHsQGojko Adzic • Specification by Example • https://amzn.to/44uqT6zInspiring Tech Leaders - The Technology PodcastInterviews with Tech Leaders and insights on the latest emerging technology trends.Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

In this episode of The Engineering Room, Dave Farley speaks with Sam Newman, renowned author of "Building Microservices" and "Monolith to Microservices," about distributed systems, architectural decisions, and the future of software development.-------------------------Sam Newman on "X" (formerly "Twitter"): https://x.com/samnewman?lang=en

Join Dave Farley in conversation with Daniel Terhorst-North, the creator of Behavior-Driven Development (BDD) and pioneering voice in agile software development. In this wide-ranging discussion,Dan shares insights from his time at ThoughtWorks, where he helped establish many practices now considered standard in modern software engineering.Whether you're interested in improving your development practices, leading organizational change, or understanding the historical evolution of agile methodologies, this conversation offers valuable perspectives from one of the field's most influential practitioners.-----------------------------------Dan Terhorst-North's LinkedIn: https://www.linkedin.com/in/tastapod/?originalSubdomain=ukDan Terhorst-North's Website: https://goalwards.co/Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Only Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdelivery

Farah est à l'image de sa passion, une véritable Formula 1 de la qualité. Ou plutôt de l'excellence, comme elle nous l'explique.Contrairement à nombre d'entre nous, qui, au même âge, pensions plus à la future sortie du week-end avec les copaines, c'est à 14 ans que démarre la vocation de Farah pour la tech et les sciences de l'informatique. Une fois son bac en poche, elle arrive en France pour poursuivre son parcours. Après une licence en informatique, elle suit un master en Machine Learning et traitement automatique de l'image, en parallèle d'un apprentissage chez Dassault Système. C'est à cette occasion qu'elle découvre le sujet de la qualité. Un sujet qui ne l'a plus jamais quitté. Ayant l'envie d'évoluer dans un environnement sur lequel elle verrait son impact, elle se dirige vers le milieu des Start-up Scale-Up : en tant qu'Head of Quality Enginering, elle a ainsi participé à l'évolution d'entreprises telles que Leetchi, Mangopay, Livestorm, ou encore Ankorstore. Aujourd'hui, c'est en tant que C.T.O de Worklife qu'elle poursuit sa trajectoire.   Mais son envie d'impacter les gens et le monde de la qualité ne s'arrête pas à son environnement professionnel. Elle a ainsi co-fondé la communauté Women of Influence, lancé la newsletter Build Quality, et intervient régulièrement en tant que conférencière.Durant cette passionnante conversation, nous avons évoqué :L'importance de prendre le temps de l'introspection pour booster ses ambitions,Pourquoi elle ne pense plus qualité mais excellence ?Comment adapter ses focus excellences en fonction du projet ? Le scale ne s'improvise pas : comment l'organiser méthodiquement ?Sa formation en gouvernance en cybersécurité,Ce qu'elle fait pour monter en compétence partout, tout le temps et par tous les moyens,Comment bien s'approprier les responsabilités et la culture de l'entreprise lorsqu'on arrive comme CTO,Comment diriger le focus des équipes sur les bons éléments ?Quels sont les avantages d'avoir été testeur quand on est CTO ?Ce qu'elle fait dans ses moments “Koala”,L'intérêt d'avoir des CTO au COMEX et au board,Comment et pourquoi elle est devenue conférencière,Son moteur principal : l'impact qu'elle va avoir sur les gens,Comment faire quand on n'a pas le temps de transmettre le why et le how aux équipes ?Est-ce qu'elle aurait fait certaines choses différemment aujourd'hui ?Farah nous recommande de lire : Start with Why de Simon Sinek How to Fail at Almost Everything and Still Win Big de Scott Adams Accelerate: The Science Behind Devops: Building and Scaling High Performing Technology Organizations de Nicole Forsgren PhD, Jez Humble, Gene KimEt de suivre : David Heinemeier HanssonThe Pragmatic EngineerThe Dora Metric CommunityLisa CrispinRetrouvez Farah sur LinkedIn : https://www.linkedin.com/in/farah-chabchoub/Ou en vous abonnant à sa newsletter Build Quality : https://farahchabchoub.substack.com/Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereManuel Pais - Co-Author of the Book "Team Topologies"Julian Wood - Serverless Developer Advocate at AWS  RESOURCESManuelhttps://x.com/manupaisablehttps://www.manuelpais.nethttps://www.linkedin.com/in/manuelpaishttps://github.com/manupaisableJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://teamtopologies.comhttps://academy.teamtopologies.comhttps://www.teamperature.comhttps://itrevolution.comhttps://matthewskelton.comDESCRIPTIONManuel Pais, co-author of Team Topologies, shares his journey in shaping modern organizational design for fast-flow efficiency with Julian Wood. Reflecting on the widespread impact of the book, Manuel explores how its principles have enabled organizations to redefine team structures, streamline value delivery, and balance cognitive load.The discussion covers communication challenges, the evolution of platform engineering, and strategies for iterative team reorganization. Manuel also addresses the growing influence of AI in software development, emphasizing the need for human oversight, strategic alignment with value streams, and enabling teams to harness AI effectively. With insights from real-world implementations and evolving trends, this episode provides a comprehensive guide to building adaptable, customer-focused, and innovative organizations.RECOMMENDED BOOKSMatthew Skelton & Manuel Pais • Team TopologiesSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team TopologiesHeidi Helfand • Dynamic ReteamingGene Kim, Kevin Behr & George Spafford • The Phoenix ProjectGene Kim, Nicole Forsgren & Jez Humble • AccelerateGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps HandbookJonathan Smart • Sooner Safer HappierBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

In this wide-ranging episode, Casey and Christine dive deep into leadership transitions, complex systems, and the art of managing large-scale projects. Christine discusses her new role as Head of Engineering at a Series D startup, managing 60+ people and Casey discusses the counterintuitive challenges of scaling teams. Christine shares her synthetic biology progress, building an orbital shaker from scratch and exploring the intersection of hardware and biotech. The conversation spans from ancient Roman infrastructure projects to modern space exploration, touching on hiring challenges, the value of going to primary sources, and why some historical civilizations came tantalizingly close to industrial revolution but never quite made the leap.Arabian Sands by Wilfred ThesigerNow It Can Be Told about the Manhattan ProjectWhat Got You Here Won't Get You There by Marshall GoldsmithAccelerate by Nicole Forsgren, Jez Humble, and Gene KimRadical Candor by Kim ScottPlayground - Contemporary science fiction novel about seasteading and AIClimbing Gold - Alex Honnold's podcast (featuring Vitaliy Musiyenko's Sierra traverse story)Conversations with Tyler - Tyler Cowen's interview showLex Fridman Podcast - Episodes with Jeff Wasserstrom (China scholar) and Tim Sweeney (Epic Games)The Complete History & Strategy of Standard Oil (Part I) (Acquired)Founders Podcast - Episodes on Jeff Bezos shareholder letters, Jim Simons, John D. Rockefeller, and Estée LauderHow Andreessen Horowitz Disrupted VC & What's Coming Next (Ben and Marc Discussions)The DER Task Force - Distributed energy resources podcast (Jesse Peltan episode)Main Engine Cut Off - Space industry podcast T+303: The Trump 2024 Transition (with Mark Albrecht)The Almost-Industrial Revolutions of Rome and China Cost of Glory - Ancient history podcast (Julius Caesar series)Circuit Playground Express - Adafruit electronics learning boardAda Fruit Orbital Shaker Tutorial - DIY lab equipment projectThinking by My Wits - Website featuring Scholar Alex Jones's literary works

In this conversation, Dave Farley explores the innovative Army Software Factory with Matt Flautt (CTO) and Jeff Day (Chief of Platform). They reveal how the U.S. Army is building an internal software development capability by training soldiers—many without prior coding experience—to become proficient developers through rigorous training and pair programming practices.This episode will be of interest to anyone with knowledge in building technical capability within large organisations, transforming non-technical talent into developers, or implementing DevOps practices in regulated environments. Their pragmatic approach to continuous improvement shows how even organisations with strict governance can adopt modern software practices.--------------------Army Software Factory Website: https://soldiersolutions.swf.army.mil/Matt Flautt (CTO) LinkedIn: https://www.linkedin.com/in/mattflauttJeff Day (Chief of Platform) LinkedIn: https://www.linkedin.com/in/jeffrey-robert-dayOnly Patreon Supporters get to see the FULL VIDEO Episodes of The Engineering Room, sign up here: https://www.patreon.com/c/continuousdeliveryPatreon: https://www.patreon.com/continuousdelivery

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereDaniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & AssociatesJulian Wood - Serverless Developer Advocate at AWSRESOURCESDanielhttps://bsky.app/profile/tastapod.comhttps://www.linkedin.com/in/tastapodhttps://github.com/tastapodhttps://mastodon.social/@tastapodhttp://dannorth.net/blogJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodhttps://s12d.com/gotoDESCRIPTIONDaniel Terhorst-North and Julian Wood share decades of experience to offer a nuanced view of programming, governance, and product delivery. By framing programming as a socio-technical activity, they emphasize the critical role of collaboration, feedback, and sustainable practices.The conversation challenges traditional governance models, advocating for hypothesis-driven product management and continuous feedback mechanisms. Through humorous anecdotes and hard-won wisdom, Terhorst-North inspires people to look beyond technical expertise to the broader ecosystem of teams, culture, and organizational alignment. [...]RECOMMENDED BOOKSJez Humble & David Farley • Continuous DeliveryNicole Forsgren, Jez Humble & Gene Kim • AccelerateKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookJez Humble, Joanne Molesky & Barry O'Reilly • Lean EnterpriseHeidi Helfand • Dynamic ReteamingHeidi Helfand • How to Change Your TeamsCarl Larson & Frank M J LaFasto • TeamworkGene Kim & Steve Spear • Wiring the Winning OrganizationMatthew Skelton & Manuel Pais • Team TopologiesBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

In this engaging conversation with Diana Montalion - former principal systems architect at The Economist and Wikimedia Foundation, and author of "Learning Systems Thinking" - we explore why traditional software development approaches are struggling to keep up with modern system complexity.Diana shares insights from her extensive experience building large-scale information systems, explaining how relationships between components often matter more than the components themselves. She discusses the critical shift from reductionist thinking to systems thinking, illustrated through practical examples from distributed systems and event-driven architectures.Diana and Dave explore what it really means to think systematically about complex software systems. They discuss why the future of software development requires us to move beyond simplistic solutions toward a more nuanced understanding of system dynamics.------------------------------Website Diana Montalion- https://montalion.com/LinkedIn Diana Montalion - https://www.linkedin.com/in/dianamontalion/Youtube Channel Diana Montalion - https://www.youtube.com/@dianamontalionBluesky Diana Montalion - https://bsky.app/profile/mentrix.bsky.socialPatreon: https://www.patreon.com/continuousdelivery

Join Dave Farley and Michael Nygard, former Chief Scientist at Sabre and current leader in Global Platforms at Nubank, for an illuminating discussion on modern software architecture and data systems. They explore how data mesh solutions enable incremental problem-solving at scale, and why traditional software engineering principles like modularity and separation of concerns remain crucial even as our systems evolve.Nygard shares insights from managing 300,000 datasets at Nubank, explaining how they're tackling the challenges of ETL (Extract, Transform, Load) generation, schema management, and the complex interplay between operational and analytical worlds. Drawing from decades of experience, they examine the industry's evolution, from the simplicity of early systems to today's intricate architectures, offering valuable perspectives on managing growing complexity while maintaining system quality.---------Thanks to Goto for hosting this chat at their conference in Copenhagen. You can check out Goto on YouTube HERE: https://www.youtube.com/@GOTOEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Find out more about their conferences HERE: https://gotopia.tech/events/upcoming?page=0"X (Formerly ''Twitter'') Michael Nygard : https://x.com/mtnygard?lang=en-GB LikedIn Michael Nygard: https://www.linkedin.com/in/mtnygard/

We discuss the four modes of coaching and navigate career growth in expanding / contracting companies with James Birchler. James shares highlights from the recent coaching / mentoring workshop he facilitated, and breaks down how each mode of coaching differs tactically. We also cover the dilemma of linear career/leadership growth vs. exponential company growth, different common communication challenges eng leaders face, why people / organizational challenges are harder than technical issues, and how to prepare for & execute uncomfortable conversations. James also shares his unique journey to technical leadership & how past management roles – even in non-tech spaces – have helped shape his thoughts on coaching & eng leadership today.ABOUT JAMES BIRCHLERJames Birchler is an engineering and product development leader, technical advisor, and an accredited Executive Coach from the UC Berkeley Haas School of Business Executive Coaching Institute.In his coaching practice, James focuses on self-awareness, integrity, accountability, and fostering a growth mindset that supports continuous learning and high performance.He focuses his technical advisory practice on common mechanisms and playbooks required at different phases and inflection points of startup growth and scaling: Hiring and interviewing, product development methodologies including Lean Startup and Agile, operational meeting cadence and communication flow, people management, technical leadership, vision/mission development, alignment, and execution.James implemented the Lean Startup methodologies with Eric Ries at IMVU (literally the first Lean Startup), where his team helped start the DevOps movement by building the infrastructure to ship code to production 50 times a day (which was a lot at the time!) and coining the term “continuous deployment.”He has more than 20 years of experience leading high-performance teams in growth environments, including startups and scaled organizations, including Amazon. He has delivered great consumer software products and implemented product development and innovation processes based on continuous learning and improvement.Presently James advises and coaches Series A+ startups in the US and Europe, and leads innovation practices in hyper-growth areas of last mile delivery technology for Amazon. Previously my roles included VP of Engineering & Operations, VP of Engineering, and Founder at several technology startups including IMVU, Caffeine.tv, SmugMug, iCracked, The Arts Coop, and Letters & Science.You can find James at jamesbirchler.com, LinkedIn, and Substack.SHOW NOTES:Highlights from James' recent coaching & mentoring workshop (2:41)Shared challenges around building trust in eng teams (5:25)The differences between coaching vs. mentoring (7:01)Building trust in order to best support your team members as a manager (9:38)Defining the advising mode of coaching (11:54)How supporting differs from advising (14:29)The story behind James' technical leadership journey (16:55)Transitioning from a PhD program & environmental planning career into tech (20:19)The dilemma of career growth: linear leadership growth vs. exponential company growth (23:53)Why organizational challenges are more complicated than technical puzzles (26:49)Navigating career growth during company contraction from the employee perspective (28:02)Preparing for uncomfortable conversations as a coach / manager (31:50)Strategies for actually having those tough conversations (35:36)Frameworks for helping others identify what they want (37:58)Rapid fire questions (42:44)LINKS AND RESOURCESStop 'Coaching' Your Tech Team (And What To Do Instead) - James' substack post on the four modes of development breaking down the core differences of coaching, advising, mentoring, and supporting roles and explaining how trust is the secret ingredient to all four.jamesbirchler.com - James' website where you can find info about his executive coaching and resources for engineering leaders and founders.How to lead with radical candor | Kim Scott - NYT bestselling author, Kim Scott, has cracked the code on giving valuable feedback in a way that builds genuine relationships, drives results, and creates positive workplaces.What Are People For? - In the twenty-two essays collected here, Wendell Berry conveys a deep concern for the American economic system and the gluttonous American consumer. Berry talks to the reader as one would talk to a next-door neighbor: never preachy, he comes across as someone offering sound advice. In the end, these essays offer rays of hope in an otherwise bleak forecast of America's future. Berry's program presents convincing steps for America's agricultural and cultural survival.New Happy: Getting Happiness Right in a World That's Got It Wrong - Happiness expert Stephanie Harrison draws upon hundreds of studies to offer a life-changing guide to finding the happiness you have been looking for, all based on a decade of research and brought to life with beautiful artwork.Accelerate: Building and Scaling High-Performing Technology Organizations - Through four years of groundbreaking research, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance—and what drives it—using rigorous statistical methods. This book presents both the findings and the science behind that research. Readers will discover how to measure the performance of their teams, and what capabilities they should invest in to drive higher performance.Conversations on Science, Culture, and Time: Michel Serres with Bruno Latour - Although elected to the prestigious French Academy in 1990, Michel Serres has long been considered a maverick--a provocative thinker whose prolific writings on culture, science and philosophy have often baffled more than they have enlightened. In these five lively interviews with sociologist Bruno Latour, this increasingly important cultural figure sheds light on the ideas that inspire his highly original, challenging, and transdisciplinary essays.This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/336Charity Majors - CTO at honeycomb.io & Co- Author of "Observability Engineering"James Lewis - Software Architect & Director at ThoughtworksRESOURCESCharityhttps://twitter.com/mipsytipsyhttps://github.com/charityhttps://linkedin.com/in/charity-majorshttps://charity.wtfJameshttps://twitter.com/boicyhttps://linkedin.com/in/james-lewis-microserviceshttps://github.com/boicyhttps://www.bovon.orgDESCRIPTIONWhat's next in the observability space? Join Charity Majors and James Lewis as they discuss canonical logs, Observability 2.0 and how to simplify complexity in software engineering!RECOMMENDED BOOKSCharity Majors, Liz Fong-Jones & George Miranda • Observability Engineering • https://amzn.to/38scbmaCharity Majors & Laine Campbell • Database Reliability Engineering • https://amzn.to/3ujybdSKelly Shortridge & Aaron Rinehart • Security Chaos Engineering • https://www.verica.io/sce-bookNora Jones & Casey Rosenthal • Chaos Engineering • https://amzn.to/3hUmuAHRuss Miles • Learning Chaos Engineering • https://amzn.to/3hCiUe8Nicole Forsgren, Jez Humble & Gene Kim • Accelerate • https://amzn.to/442Rep0BlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

In this episode of The Engineering Room, Dave Farley speaks with Holly Cummins, Senior Principal Software Engineer at Red Hat, about the evolving landscape of software development. They explore whether programming is getting harder, discussing how abstraction levels have changed while core problem-solving skills remain essential. Holly shares insights on AI's role in different programming contexts and the challenges of maintaining simplicity in modern software development.The conversation covers platform design principles, mechanical sympathy in programming, and the surprising benefits of garbage collection in Java. Holly explains how her journey from physics to software engineering was driven by a natural inclination to turn problems into programming challenges.They discuss the importance of fun and playfulness in software development teams as indicators of project health and creativity. The episode concludes with Holly explaining Quarkus, a Java framework that challenges traditional assumptions about runtime dynamics to deliver improved performance and developer experience.Sponsored by Equal Experts.-----------X (Formerly ''Twitter'') Holly Cummins: https://twitter.com/holly_cummins?lang=enLinkedIn Holly Cummins: linkedin.com/in/holly-k-cumminsWebsite Holly Cummins: https://hollycummins.com/Patreon: https://www.patreon.com/continuousdelivery

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/329Flavia Naezer - Product Thinker, Public Speaker, ArtistJulian Wood - Serverless Developer Advocate at AWSRESOURCESFlaviahttps://github.com/flavianaezerhttps://www.linkedin.com/in/flavia-naezer-449b285https://x.com/flaviasomethingJulianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://dl.acm.org/doi/pdf/10.1145/3595878https://www.designcouncil.org.uk/our-resources/the-double-diamondDESCRIPTIONExplore the evolving relationship between technology and product management with Julian Wood and Flavia Naezer. Discover how Flavia's tech and product expertise highlights the need for user-centric design thinking and thorough research in developing internal tools and platforms.Discover how Julian and Flavia explore the intersection of tech and product management, highlighting the importance of user-centric design and thorough research in developing internal tools and platforms.RECOMMENDED BOOKSMarty Cagan • Inspired • https://amzn.to/4e5l2r2Anthony W. Ulwick • Jobs to Be Done • https://amzn.to/4elaVhuGregor Hohpe • Enterprise Integration Patterns, Vol 2 • https://amzn.to/3TNedQ3Gregor Hohpe • Platform Strategy • https://amzn.to/4fPLW7pStephanie Stimac • Design for Developers • https://amzn.to/3EhuN4TGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps Handbook • https://amzn.to/3WBjzCMMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQGene Kim, Nicole Forsgren & Jez Humble • Accelerate • https://amzn.to/3WCG5uTMarty Cagan • Empowered • https://amzn.to/42kuKAjTwitterInstagramLinkedInFacebookLooking 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!

Новый, с пылу, с жару выпуск подкаста с членом ПК DevOpsConf 2025. На пару с Игорем Курочкиным обсуждали DevOps и развитие инжиниринговых практик. Говорили бодро, обсуждали NextOps, который не то, чем кажется! Вспомнили массу приятных книг и не только. DevOpsConf 2025, 7-8 апреля 2025, Москва CFP DevOpsConf 2025 Встреча докладчиков и Программного комитета DevOpsConf 2025 Gene Kim, Kevin Behr, George Spafford — The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win Джин Ким, Кевин Бер, Джордж Спаффорд — Проект «Феникс». Как DevOps устраняет хаос и ускоряет развитие компании. Gene Kim, Jez Humble, Patrick Debois, John Willis, Nicole Forsgren — The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations Джин Ким, Джез Хамбл, Патрик Дебуа, Джон Уиллис — Руководство по DevOps. Как добиться гибкости, надежности и безопасности мирового уровня в технологических компаниях Gene Kim — The Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of Data Участники @golodnyj Игорь Курочкин Telegram канал VK группа Яндекс Музыка iTunes подкаст Поддержи подкаст

In this insightful episode of "The Engineering Room," join us as we explore the world of software engineering with James Lewis, a prominent figure in microservices and software architecture. Explore the origins and evolution of microservices, the importance of domain boundaries, and the distinction between microservices and distributed monoliths. Discover how generative science and engineering principles can innovate software development, enhancing team efficiency and user experiences. Don't miss this opportunity to learn from an expert on building systems and enhancing organizational scalability.This conversation is a must-watch for anyone interested in software innovation and agile development practices.----LinkedIn James Lewis: https://www.linkedin.com/in/james-lewis-microservices/?originalSubdomain=ukX (Formerly ''Twitter'') James Lewis: https://twitter.com/boicyPatreon: https://www.patreon.com/continuousdelivery

Join us in the latest episode of "The Engineering Room," a monthly series featuring long-form discussions with influential figures in software development. In this episode, Dave talks with Dragan Stepanović, a principal engineer renowned for his efforts to evolve engineering cultures and eliminate bottlenecks. Dragan shares his journey in extreme programming (XP), emphasizing its profound impact on building collaborative and efficient teams. He dives into his fascinating research on pull requests, where he analyzed over 40,000 pull requests to uncover patterns in code review processes.If you're passionate about enhancing your software development practices through proven methodologies, this discussion is a must-watch. Remember, only our Patreon supporters get access to the full video episodes of The Engineering Room - thank you for all your support!----Dragan on X/Twitter - https://x.com/d_stepanovic?lang=en Dragan's Blog Posts - https://dragan-stepanovic.github.io/Patreon: https://www.patreon.com/continuousdelivery

Richard Coplan: The Impact of Product Owner Pressure on Agile Team Morale Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode, Richard shares his experience working in a toxic team environment at an insurance company. Brought in to replace a beloved Scrum Master, he found himself navigating a strained relationship between the Product Owner (PO) and the team. The PO's aggressive push for deliverables demotivated the team, and management sided with the PO, creating a vicious cycle of disengagement. How can a PO's leadership style make or break a team's performance? Richard explores this anti-pattern of PO-driven disengagement. Featured Book of the Week: Lean Enterprise by Jez Humble, et al. Richard reflects on how the book "Lean Enterprise" helped shape his approach as an Agile Coach, offering a holistic view of organizations. He also discusses "Team Topologies" and the importance of stream-aligned teams with CI/CD pipelines. What role does organizational agility play in the success of Scrum teams? Richard suggests that while many teams practice Scrum, organizations themselves are often not truly Agile.   [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!     About Richard Coplan Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures. You can link with Richard Coplan on LinkedIn.

Applying 'Accelerate' Principles to Embedded Systems | Agile Embedded PodcastWelcome to the latest episode of the Agile Embedded Podcast with Jeff Gable and Luca Ingianni! In this episode, we address a listener's question about the book 'Accelerate' by Nicole Forsgren, Jez Humble, and Gene Kim. Jeff and Luca delve into how the principles from this book, which focuses on Lean Software and DevOps, can be applied to embedded systems development. They discuss the nuances of embedded systems, the relevance of DORA metrics, and share insights on how capabilities and processes from the book translate to the unique challenges of embedded systems. Tune in to understand how you can adapt and implement these best practices in your projects.00:00 Introduction to the Agile Embedded Podcast00:06 Overview of the Book 'Accelerate'00:50 Research Methodology and Key Findings02:56 DORA Metrics Explained05:30 Key Capabilities for Effective Organizations18:41 Applying 'Accelerate' Principles to Embedded Systems20:19 Challenges and Considerations in Embedded Systems34:10 The Importance of Logging and Feedback Loops37:43 Empowering Teams and Encouraging Experimentation41:58 Final Thoughts and Recommendations You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereDavid Anderson - Software Architect at G-P/Globalization Partners & Author of "The Value Flywheel Effect"Charles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESDavidhttps://x.com/davidand393https://www.linkedin.com/in/david-anderson-belfasthttps://theserverlessedge.comCharleshttps://twitter.com/charleshumblehttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://blog.container-solutions.com/adrian-cockcroft-on-serverless-continuous-resiliencehttps://www.wardleymaps.comDESCRIPTIONDavid Anderson, co-author of "The Value Flywheel Effect", shares his experiences and insights from his time at Liberty Mutual, where he drove significant technological transformation through a serverless first approach in a conversation with Charles Humble.Anderson discusses the importance of aligning business and IT strategy, fostering an environment of psychological safety, and enabling teams with the right tools and frameworks to achieve rapid software development. He emphasizes the value of principles-driven development, collaborative processes, and the impact of using the AWS Cloud Development Kit (CDK) to create reusable patterns. Anderson also highlights the continuous nature of software evolution and the importance of timing and momentum in driving successful change in large organizations. [...]RECOMMENDED BOOKSDavid Anderson, Marck McCann & Michael O'Reilly • The Value Flywheel EffectGregor Hohpe • The Software Architect ElevatorGene Kim, Nicole Forsgren & Jez Humble • AccelerateJim Collins • Turning the FlywheelGene Kim & Steve Spear • Wiring the Winning OrganizationGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps HandbookElisabeth Hendrickson • Explore It!Gerald M. Weinberg • Becoming a Technical LeaderTwitterInstagramLinkedInFacebookLooking 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!

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereGene Kim - Author, Researcher, DevOps Enthusiast & Founder of IT RevolutionCharles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESGenehttps://twitter.com/RealGeneKimhttps://www.linkedin.com/in/realgenekimhttp://www.realgenekim.meCharleshttps://twitter.com/charleshumblehttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://youtu.be/vLHFuQjJR8Yhttps://youtu.be/5_rrQND3lpQhttps://youtu.be/dMwGfRINpz0https://youtu.be/KDHyxnLdOqchttps://youtu.be/AxqX9ovGViwhttps://youtu.be/JAl3QFae_dEhttps://youtu.be/l3XwpSKqNZwhttps://youtu.be/wtmW89I941Ihttps://youtu.be/5OjqD-ow8GEhttps://youtu.be/hIwVqt6qtc4DESCRIPTIONJoin Gene Kim and Charles Humble as they demystify the complexities of organizational dynamics, offering a comprehensive guide to navigating challenges and fostering success through his five ideals, backed by real-world stories and expert discussions.Discover the keys to organizational success with Gene Kim and Charles Humble in an insightful conversation, backed by real-world stories and expert discussions. [...]RECOMMENDED BOOKSGene Kim & Steve Spear • Wiring the Winning OrganizationGene Kim • The Unicorn ProjectGene Kim, Kevin Behr & George Spafford • The Phoenix ProjectGene Kim, Nicole Forsgren & Jez Humble • AccelerateGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps HandbookGene Kim & John Willis • Beyond The Phoenix ProjectDaniel Kahneman • Thinking, Fast and SlowElisabeth Hendrickson • Explore It!Gerald M. Weinberg • Becoming a Technical LeaderTwitterInstagramLinkedInFacebookLooking 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!

Join us in this episode of "The Engineering Room" as Dave explores the intricate relationship between continuous delivery, automated testing, and agile software development in the gaming industry. Dave's special guest, Henry Golding, shares his extensive experience as an engineering leader and consultant, with a background in pioneering continuous delivery on projects like Microsoft's "Sea of Thieves" and "Minecraft," Henry provides valuable insights into overcoming perceived barriers to adopting continuous delivery. We delve into the practical challenges of implementing automated testing in games, the cultural shifts required, and how to make testing an integral part of the development process. Henry's approach to easing adoption, involving developers, and gaining support from leadership offers a roadmap for teams aiming to restructure their development processes for better efficiency and higher quality output. Whether you are an industry professional or just curious about modern software development practices, this episode is packed with expert advice and real-world examples on sustainable delivery of high-quality software.Remember, only our Patreon supporters get access to the full video episodes of The Engineering Room, so if you haven't already, consider joining our community to get exclusive content and support our work!--- Patreon: https://www.patreon.com/continuousdeliveryHenry Golding LinkedIn: https://www.linkedin.com/in/hgolding/Join the Continuous Delivery community and access extra perks & content! ➡️ https://bit.ly/ContinuousDeliveryPatreon

Welcome Gary Gruver in this episode of The Engineering Room! Gary is an experienced executive and consultant known for transforming software development and delivery processes in large organisations. He discusses his journey, starting with his impactful work as the R&D director for the HP LaserJet firmware team, where he led productivity improvements of 2-3 times, and later as an independent consultant, speaker, and author. Join Dave Farley and Gary Gruver for a deep dive into the practical and philosophical aspects of software engineering, leadership, and the future of AI in the industry.Listen to the full episode to gain valuable insights and actionable strategies for improving software development and delivery in your organisation. Don't forget to check out the links for more resources and Gary's latest book, "Engineering the Digital Transformation.”~~~~Engineering The Digital Transformation - https://www.amazon.co.uk/Engineering-Digital-Transformation-Gary-Gruver/dp/1543975267Join the Continuous Delivery community and access extra perks & content! ➡️ https://bit.ly/ContinuousDeliveryPatreon

In this episode of the Engineering Room, we are pleased to welcome Dr. Nicole Forsgren. Dr. Forsgren is is an American technology executive, IT impact expert, and author. She joins Dave to talk about software developer productivity metrics, DORA, her part in one of the most impactful industry leading book's “accelerate”, her predictions for the future of software engineering under the influence of science and data and MUCH MORE.xxNicole on LinkedIn: https://www.linkedin.com/in/nicolefv/

In this episode, Dave Farley and Niklas Gustavsson, Chief Architect and VP of Engineering at Spotify, discuss the facets of Spotify's software development and operational strategies, discussing the company's unique approach to organising software development, notably through Fleet Management.Dave and Niklas discuss how to overcome common misconceptions and anti-patterns associated with microservices, and explore the role of Spotify's "Golden Technologies" in standardising technology stacks to reduce fragmentation.xxNiklass on LinkedIn: https://www.linkedin.com/in/protocol7/

Trisha Gee joins Dave to talk about developer productivity. What are the keys to creating an environment for software engineers to feel positive and happy while being at their most productive? Can we really measure developer productivity? Let's find out!xx

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereDaniel Bryant - Independent Technical ConsultantMatt Turner - DevOps Leader and Software Engineer at TetrateRESOURCEShttps://llvm.org/pubs/2002-08-09-LLVMCompilationStrategy.pdfhttps://www.thoughtworks.com/radarDanielhttps://twitter.com/danielbryantukhttps://github.com/danielbryantukhttps://linkedin.com/in/danielbryantukhttps://linktr.ee/danielbryantukMatthttps://mt165.co.ukhttps://twitter.com/mt165https://linkedin.com/in/mt165https://github.com/mt-insideDESCRIPTIONJoin two cloud native experts and passionate adopters of modern tech as they explore the shifting role and impact of APIs. They go beyond the usual tech stack to touch on key aspects of the modern infrastructure and software development space like: platform engineering, mechanical sympathy and the role that Wasm could play in this. Daniel Bryant and Matt Turner will share some of the important but not so well known best practices and questions that one might ask to make sure they are building the right thing with the right tools.RECOMMENDED BOOKSDaniel Bryant, James Gough & Matthew Auburn • Mastering API ArchitectureDaniel Bryant & Abraham Marín-Pérez • Continuous Delivery in JavaMauricio Salatino • Platform Engineering on KubernetesAdrian Mouat • Using DockerBurns, Beda & Hightower • Kubernetes: Up & RunningNicole Forsgren, Jez Humble & Gene Kim • AccelerateTwitterInstagramLinkedInFacebookLooking 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!

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereMark Rendle - Creator of Visual ReCode with 7 Microsoft MVP Awards & 30+ Years of Experience Building SoftwareHannes Lowette - Head of Learning & Development at Axxes, Monolith Advocate, Speaker & Whiskey LoverRESOURCESMark Rendle: https://youtu.be/Y9clBHENy4QHannes Lowette: https://youtu.be/wkFx2R4uk2ASir Tim Berners-Lee: https://youtu.be/Rxqko96C5ZIEli & Mark: https://youtu.be/Gs1exPFXnQ8Matt & Mark: https://youtu.be/vzqzLSJWo3kKevin, Dylan & Hannes: https://youtu.be/HevYXFZcb98Martin & Hannes: https://youtu.be/vzywu1ol-b8Anita Sengupta: https://youtu.be/Q_O9pmSpg_8Markhttps://twitter.com/markrendlehttps://github.com/markrendlehttps://linkedin.com/in/markrendleHanneshttps://twitter.com/hannes_lowettehttps://github.com/Belenarhttps://linkedin.com/in/hanneslowetteDESCRIPTIONHannes Lowette and Mark Rendle explore the highs and lows of programming, ranging from the monumental mistakes that have shaped the industry to the subtle yet impactful errors in code that translate to wasted time. They dissect the intricate world of FinTec, uncovering the dark side of digital markets and the pitfalls that emerge. The duo scrutinizes JavaScript's role in the programming landscape, questioning whether it's a revolutionary force or a coding misstep, while also delving into the potential drawbacks of package managers.The conversation takes a turn to the negative aspects of programming languages, highlighting their flaws and the havoc they can wreak on software development. Finally, they reflect on the interconnectedness of coding decisions and business failures, emphasizing the profound impact of programming choices on the success or downfall of a business in the tech realm.RECOMMENDED BOOKSTomasz Lelek & Jon Skeet • Software Mistakes & TradeoffsHenney & Monson-Haefel • 97 Things Every Software Architect Should KnowMerih Taze • Engineers Survival GuideDave Farley & Jez Humble • Continuous DeliveryNicole Forsgren, Jez Humble & Gene Kim • AccelerateTwitterInstagramLinkedInFacebookLooking 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!

What does the future of software development look like? How will AI shape software engineer jobs? In this episode of the Engineering Room podcast, Dave is joined by author, software engineer and well-known thought leader, Eric Evans. They talk about Eric's background, domain-driven design, artificial intelligence and what the next 10 years look like for the software industry with the emergence of AI.Eric wrote THE software design book that should be on every software engineer's bookshelf.xx

Jez Humble joins Dave Farley in the podcast episode where they discuss writing the award-winning book 'Continuous Delivery' - Jez' goal was to stop people wasting time by doing the wrong things, and showing people a better way of working so they don't have to spend their evenings and weekends to release new software! Dave and Jez share views on a divided SW industry, the real identity of a software developer, what mistakes they made, the importance of building teams with trust, the origins of TDD and Blue-Green deployment, current software engineering trends AND MORE.xxEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Join the Continuous Delivery community and access extra perks & content! JOIN HERE ➡️ https://bit.ly/ContinuousDeliveryPatreonDORA - https://www.devops-research.com/resea... Project Aristotle

Gregor Hohpe, author of "Enterprise Integration Patterns", talks to Dave Farley about software architecture and how architects can transform businesses. They chat about: Gregor's current role and work with AWS (Amazon Web Services), the challenge of finding new architectural models in the cloud, "Gregor's Law" AND MORE! Thanks to Gregor for joining Dave on this episode of the Engineering Room. xxJOIN PATREON HERE ➡️ https://bit.ly/ContinuousDeliveryPatreon

Gregor Hohpe. is a world-class expert on software architecture and the role of the architect, he is a technologist and expert on the topics of large-scale systems and the public Cloud as well as lots of other stuff. Gregor is currently part of the Serverless team working as an Enterprise Strategist for Amazon at AWS, Previously he was Technical Director in the Office of the CTO at Google, and before that was Chief SW Architect at Allianz the German Insurance giant. Gregor is an international speaker, author of Several great books, as well as writing on his always thought-provoking blog, “The Architect Elevator”. and he's just published a new book called “Platform Strategy”.xxEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0

Seb Rose is a Consultant, coach, trainer, analyst, and developer and an organiser of some of the UK's best software conferences. His name is closely associated with BDD, he is a contributor to the Cucumber open source project, which is one of the most widely used frameworks for BDD, and has written several books on this, and other software topics, including the “BDD Books” series, “Cucumber for Java” and he has the first chapter in “97 things every programmer should know”. Seb is also a blogger, and a regular conference speaker. He helps to run a charity, via the very excellent cyber-dojo.org site for teach TDD, that helps children to learn to code.xxEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0

Jessica Kerr talks to Dave Farley about a bunch of topics ranging from cybernetics, to systems theory, complex adaptive systems and the importance of data visualisation to observability. Jessica, known by many as @jessitron is Engineering Manager of Dev Relations at Honeycomb, a well known speaker and a symmathecist in the medium of code - which she describes as seeing development teams as learning systems made of people and running software. Jessica and Dave share a love for software development in all its complexity and in the complexity of its socio-technical setting.xxJessica's Website: ➡️ https://jessitron.com "Systems Thinking for Developers" ➡️ • Systems Thinking for Developers • Jes... Jessica Kerr on Medium: ➡️ / jessitron ⭐ PATREON: Join the Continuous Delivery community at access extra perks & content, join in our CD Discord discussions and support the CD YouTube channel. JOIN HERE ➡️ https://bit.ly/ContinuousDeliveryPatreon

Dave Farley is a consultant and renowned thought leader in the software development world, and a strong advocate for ensuring that our software is always releasable. He's co-authored a book and runs a popular YouTube channel, both called "Continuous Delivery". We spoke about what continuous delivery is, why it's important, the barriers to implementing it, and how product managers can help. Episode highlights: 1. Continuous delivery is what the best software organisations in the world do It's unambiguous. It's backed by data. It's the best way to build quality products. Applying these techniques means your software is always releasable, and every change is safe 2. But, this doesn't mean you need genius developers Any team can adopt continuous delivery. It's not a factor of 10x "rock star" developers, but empowered teams of developers working together, collaborating and *talking* to each other. 3. You build quality software by going fast Continuous feedback based on small changes, constantly validated, ensures high-quality products. You don't want to go back & fix it later. You can't inspect quality into a system at the end of a development cycle. Build it in upfront. 4. Just because you can release continuously doesn't mean you have to What you release to customers is a business decision. This isn't about throwing half-finished features at users but having software that you know works. You can use feature flags to manage availability. 5. Many product managers need to check themselves We need to move away from PMs giving developers human-language representations of code and telling them to convert it for a computer. The best devs are problem solvers and should be involved in working out the best solution. Buy "Continuous Delivery" "Getting software released to users is often a painful, risky, and time-consuming process.This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours―sometimes even minutes–no matter what the size of a project or the complexity of its code base." Check it out on Amazon. Check out Dave's course Dave has a course out that helps people get good at all the stuff we talked about in the podcast. If you're interested, check the course out here. Dave also mentioned a talk by his co-author Jez Humble. I'm not 100% sure if this is the one, but it looks pretty good anyway. Check it out. Contact Dave You can connect with Dave on Twitter. You can also check out the Continuous Delivery YouTube channel.

This week, Dan Neumann is joined by Mike Guiler to discuss the benefits of Agility, including employee satisfaction, predictable delivery, and speed to market among others.   Key Takeaways: Agility leads to employee satisfaction since every Team member is connected to the purpose of the work. Sustainable pace is enabled by Agile Methods Agile done well eliminates the “death march” Deliver slices of value  Deliver the most valuable items first Agile delivery is not “all-or-nothing,” enabling us to decide what we can release without Predictable delivery is mostly assured with Agile, and even when the mark is missed it can be adjusted back in a brief period. Reduction of Waste The Increment is inspected frequently We learn from what we deliver You can stop and pivot when going down a path that is not what the customer needs Make change easier Validate assumptions early Reduce Risk  Don't build the whole thing before we deliver it Reduce risk by gradually exposing your features to users versus an “all-or-nothing” release Incremental deliveries reduce risk by validating assumptions. You get real customer feedback. Speed to Market Deliver the right things, reduce waste, and get a slice delivered! Do not expect that your developers will “code faster” Faster Return on Investment Generate revenue with small slices Decide when to stop investing further in a product When you decide to transform your business outcomes, you need to consider the benefits you are striving for when you make decisions within your organization. Keep the end goal in mind at all times. We want to be efficient instead of effective. Collaboration works wonders; a Team is more resilient and efficient when collaborating. Some people are not ready to work in a Team; they need space and time to gradually start feeling more comfortable with teaming. Scrum is often perceived as having a lot of meetings when in reality, the meetings required are the minimum necessary to keep the Team aligned toward achieving the common purpose.   Mentioned in this Episode: Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren Ph.D., Jez Humble, and Gene Kim   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!  

#23: For over two decades Itamar Gilad held senior product management and engineering roles at Google, Microsoft and a number of startups. At Google, Itamar led parts of Gmail and was the head of Gmail's growth team. Axel sits down with Itamar to discuss some of the frameworks he's been crafting through his journey and how they can help fellow Product Managers improve their practice.We specifically dive into how frameworks can help PMs boost their confidence based on evidence and clear communication.Where to find ItamarLinkedIn: https://www.linkedin.com/in/itamargilad/Website: https://itamargilad.com/Where to find AxelLinkedIn: https://www.linkedin.com/in/axelsooriah/About PanashWe provide training and coaching programs to help product professionals unlock their true potential and become high performers.You can learn more about our programs here: https://www.panash.io/Our blog contains articles and free resources on key topics for product managers and leaders.Check it out here: https://collection.panash.io/Referenced in this episode:The Lean Startup by Eric RiesInspired by Marty CaganEmpowered by Marty Cagan with Chris JonesLean Enterprise by Jez Humble et al.Lean Analytics by Alistair CrollRunning Lean: Iterate from Plan A to a Plan That Works by Ash MauryaValue proposition canvas by StrategyzerAssumption Mapping by David J. BlandItamar's resourcesShow notes and highlights(01:35) Itamar's background(03:32) How does the MUST Framework help(12:42) Biggest traps people fall into when crafting strategy(18:04) Deferring the point of commitment(22:52) GIST: a framework to bridge strategy and execution(35:23) Using frameworks to boost confidence (44:26) Itamar's Treasure Chest───For inquiries about sponsoring the podcast, please reach out to podcast@panash.ioMentioned in this episode:Elevate your product careerDo you feel stuck, not knowing how to tackle a problem? Are you looking for a solution to help your team members grow in their craft? Either way, check out...

About GeneGene Kim is a multiple award-winning CTO, researcher and author, and has been studying high-performing technology organizations since 1999. He was founder and CTO of Tripwire for 13 years. He has written six books, including The Unicorn Project (2019), The Phoenix Project (2013), The DevOps Handbook (2016), the Shingo Publication Award winning Accelerate (2018), and The Visible Ops Handbook (2004-2006) series. Since 2014, he has been the founder and organizer of DevOps Enterprise Summit, studying the technology transformations of large, complex organizations.Links: The Phoenix Project: https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/1942788290/ The Unicorn Project: https://www.amazon.com/Unicorn-Project-Developers-Disruption-Thriving/dp/B0812C82T9 The DevOps Enterprise Summit: https://events.itrevolution.com/ @RealGeneKim TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Cloud Economist Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: If you asked me to rank which cloud provider has the best developer experience, I'd be hard-pressed to choose a platform that isn't Google Cloud. Their developer experience is unparalleled and, in the early stages of building something great, that translates directly into velocity. Try it yourself with the Google for Startups Cloud Program over at cloud.google.com/startup. It'll give you up to $100k a year for each of the first two years in Google Cloud credits for companies that range from bootstrapped all the way on up to Series A. Go build something, and then tell me about it. My thanks to Google Cloud for sponsoring this ridiculous podcast.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey Quinn: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by a man who needs no introduction but gets one anyway. Gene Kim, most famously known for writing The Phoenix Project, but now the Wall Street Journal best-selling author of The Unicorn Project, six years later. Gene, welcome to the show.Gene Kim: Corey so great to be on. I was just mentioning before how delightful it is to be on the other side of the podcast. And it's so much smaller in here than I had thought it would be.Corey Quinn: Excellent. It's always nice to wind up finally meeting people whose work was seminal and foundational. Once upon a time, when I was a young, angry Unix systems administrator—because it's not like there's a second type of Unix administrator—[laughing] The Phoenix Project was one of those texts that was transformational, as far as changing the way I tended to view a lot of what I was working on and gave a glimpse into what could have been a realistic outcome for the world, or the company I was at, but somehow was simultaneously uplifting and incredibly depressing all at the same time. Now, The Unicorn Project does that exact same thing only aimed at developers instead of traditional crusty ops folks.Gene Kim: [laughing] Yeah, yeah. Very much so. Yeah, The Phoenix Project was very much aimed at ops leadership. So, Bill Palmer, the protagonist of that book was the VP of Operations at Parts Unlimited, and the protagonist in The Unicorn Project is Maxine Chambers, Senior Architect, and Developer, and I love the fact that it's told in the same timeline as The Phoenix Project, and in the first scene, she is unfairly blamed for causing the payroll outage and is exiled to The Phoenix Project, where she recoils in existential horror and then finds that she can't do anything herself. She can't do a build, she can't run her own tests. She can't, God forbid, do her own deploys. And I just love the opening third of the book where it really does paint that tundra that many developers find themselves in where they're just caught in decades of built-up technical debt, unable to do even the simplest things independently, let alone be able to independently develop tests or create value for customers. So, it was fun, very much fun, to revisit the Parts Unlimited universe.Corey Quinn: What I found that was fun about—there are few things in there I want to unpack. The first is that it really was the, shall we say, retelling of the same story in, quote/unquote, “the same timeframe”, but these books were written six years apart.Gene Kim: Yeah, and by the way, I want to first acknowledge all the help that you gave me during the editing process. Some of your comments are just so spot on with exactly the feedback I needed at the time and led to the most significant lift to jam a whole bunch of changes in it right before it got turned over to production. Yeah, so The Phoenix Project is told, quote, “in the present day,” and in the same way, The Unicorn Project is also told—takes place in the present day. In fact, they even start, plus or minus, on the same day. And there is a little bit of suspension of disbelief needed, just because there are certain things that are in the common vernacular, very much in zeitgeist now, that weren't six years ago, like “digital disruption”, even things like Uber and Lyft that feature prominently in the book that were just never mentioned in The Phoenix Project, but yeah, I think it was the story very much told in the same vein as like Ender's Shadow, where it takes place in the same timeline, but from a different perspective.Corey Quinn: So, something else that—again, I understand it's an allegory, and trying to tell an allegorical story while also working it into the form of a fictional work is incredibly complicated. That's something that I don't think people can really appreciate until they've tried to do something like it. But I still found myself, at various times, reading through the book and wondering, asking myself questions that, I guess, say more about me than they do about anyone else. But it's, “Wow, she's at a company that is pretty much scapegoating her and blaming her for all of us. Why isn't she quitting? Why isn't she screaming at people? Why isn't she punching the boss right in their stupid, condescending face and storming out of the office?” And I'm wondering how much of that is my own challenges as far as how life goes, as well as how much of it is just there for, I guess, narrative devices. It needed to wind up being someone who would not storm out when push came to shove.Gene Kim: But yeah, I think she actually does the last of the third thing that you mentioned where she does slam the sheet of paper down and say, “Man, you said the outage is caused by a technical failure and a human error, and now you're telling me I'm the human error?” And just cannot believe that she's been put in that position. Yeah, so thanks to your feedback and the others, she actually does shop her resume around. And starts putting out feelers, because this is no longer feeling like the great place to work that attracted her, eight years prior. The reality is for most people, is that it's sometimes difficult to get a new job overnight, even if you want to. But I think that Maxine stays because she believes in the mission. She takes a great deal of pride of what she's created over the years, and I think like most great brands, they do create a sense of mission and there's a deep sense of the customers they serve. And, there's something very satisfying about the work to her. And yeah, I think she is very much, for a couple of weeks, very much always thinking about, she won't be here for long, one way or another, but by the time she stumbles into the rebellion, the crazy group of misfits, the ragtag bunch of misfits, who are trying to find better ways of working and willing to break whatever rules it takes to take over the very ancient powerful order, she falls in love with a group. She found a group of kindred spirits who very much, like her, believe that developer productivity is one of the most important things that we can do as an organization. So, by the time that she looks up with that group, I mean, I think she's all thoughts of leaving are gone.Corey Quinn: Right. And the idea of, if you stick around, you can theoretically change things for the better is extraordinarily compelling. The challenge I've seen is that as I navigate the world, I've met a number of very gifted employees who, frankly wind up demonstrating that same level of loyalty and same kind of loyalty to companies that are absolutely not worthy of them. So my question has always been, when do I stick around versus when do I leave? I'm very far on the bailout as early as humanly possible side of that spectrum. It's why I'm a great consultant but an absolutely terrible employee.Gene Kim: [laughing] Well, so we were honored to have you at the DevOps Enterprise Summit. And you've probably seen that The Unicorn Project book is really dedicated to the achievements of the DevOps Enterprise community. It's certainly inspired by and dedicated to their efforts. And I think what was so inspirational to me were all these courageous leaders who are—they know what the mission is. I mean, they viscerally understand what the mission is and understand that the ways of working aren't working so well and are doing whatever they can to create better ways of working that are safer, faster, and happier. And I think what is so magnificent about so many of their journeys is that their organization in response says, “Thank you. That's amazing. Can we put you in a position of even more authority that will allow you to even make a more material, more impactful contribution to the organization?” And so it's been my observation, having run the conference for, now, six years, going on seven years is that this is a population that is being out promoted—has been promoted at a rate far higher than the population at large. And so for me, that's just an incredible story of grit and determination. And so yeah, where does grit and determination becomes sort of blind loyalty? That's ultimately self-punishing? That's a deep question that I've never really studied. But I certainly do understand that there is a time when no amount of perseverance and grit will get from here to there, and that's a fact.Corey Quinn: I think that it's a really interesting narrative, just to see it, how it tends to evolve, but also, I guess, for lack of a better term, and please don't hold this against me, it seems in many ways to speak to a very academic perspective, and I don't mean that as an insult. Now, the real interesting question is why I would think, well—why would accusing someone of being academic ever be considered as an insult, but my academic career was fascinating. It feels like it aligns very well with The Five Ideals, which is something that you have been talking about significantly for a long time. And in an academic setting that seems to make sense, but I don't see it thought of or spoken of in the same way on the ground. So first, can you start off by giving us an intro to what The Five Ideals are, and I guess maybe disambiguate the theory from the practice?Gene Kim: Oh for sure, yeah. So The Five Ideals are— oh, let's go back one step. So The Phoenix Project had The Three Ways, which were the principles for which you can derive all the observed DevOps practices from and The Four Types of Work. And so in The Five Ideals I used the concept of The Five Ideals and they are—the first—Corey Quinn: And the next version of The Nine whatever you call them at that point, I'm sure. It's a geometric progression.Gene Kim: Right or actually, isn't it the pri—oh, no. four isn't, four isn't prime. Yeah, yeah, I don't know. So, The Five Ideals is a nice small number and it was just really meant to verbalize things that I thought were very important, things I just gravitate towards. One is Locality and Simplicity. And briefly, that's just, to what degree can teams do what they need to do independently without having to coordinate, communicate, prioritize, sequence, marshal, deconflict, with scores of other teams. The Second Ideal is what I think the outcomes are when you have that, which is Focus, Flow and Joy. And so, Dr. Mihaly Csikszentmihalyi, he describes flow as a state when we are so engrossed in the work we love that we lose track of time and even sense of self. And that's been very much my experience, coding ever since I learned Clojure, this functional programming language. Third Ideal is Improvement of Daily Work, which shows up in The Phoenix Project to say that improvement daily work is even more important than daily work itself. Fourth Ideal is Psychological Safety, which shows up in the State of DevOps Report, but showed up prominently in Google's Project Oxygen, and even in the Toyota production process where clearly it has to be—in order for someone to pull the andon cord that potentially stops the assembly line, you have to have an environment where it's psychologically safe to do so. And then Fifth Ideal is Customer Focus, really focus on core competencies that create enduring, durable business value that customers are willing to pay for, versus context, which is everything else. And yeah, to answer your question, Where did it come from? Why do I think it is important? Why do I focus on that? For me, it's really coming from the State of DevOps Report, that I did with Dr. Nicole Forsgren and Jez Humble. And so, beyond all the numbers and the metrics and the technical practices and the architectural practices and the cultural norms, for me, what that really tells the story of is of The Five Ideals, as to what one of them is very much a need for architecture that allows teams to work independently, having a higher predictor of even, continuous delivery. I love that. And that from the individual perspective, the ideal being, that allows us to focus on the work we want to do to help achieve the mission with a sense of flow and joy. And then really elevating the notion that greatness isn't free, we need to improve daily work, we have to make it psychologically safe to talk about problems. And then the last one really being, can we really unflinchingly look at the work we do on an everyday basis and ask, what the customers care about it? And if customers don't care about it, can we question whether that work really should be done or not. So that's where for me, it's really meant to speak to some more visceral emotions that were concretized and validated through the State of DevOps Report. But these notions I am just very attracted to.Corey Quinn: I like the idea of it. The question, of course, is always how to put these into daily practice. How do you take these from an idealized—well, let's not call it a textbook, but something very similar to that—and apply it to the I guess, uncontrolled chaos that is the day-to-day life of an awful lot of people in their daily jobs.Gene Kim: Yeah. Right. So, the protagonist is Maxine and her role in the story, in the beginning, is just to recognize what not great looks like. She's lived and created greatness for all of her career. And then she gets exiled to this terrible Phoenix project that chews up developers and spits them out and they leave these husks of people they used to be. And so, she's not doing a lot of problem-solving. Instead, it's this recoiling from the inability for people to do builds or do their own tests or be able to do work without having to open up 20 different tickets or not being able to do their own deploys. She just recoil from this spending five days watching people do code merges, and for me, I'm hoping that what this will do, and after people read the book, will see this all around them, hopefully, will have a similar kind of recoiling reaction where they say, “Oh my gosh, this is terrible. I should feel as bad about this as Maxine does, and then maybe even find my fellow rebels and see if we can create a pocket of greatness that can become like the sublimation event in Dr. Thomas Kuhn's book, The Structure of Scientific Revolutions.” Create that kernel of greatness, of which then greatness then finds itself surrounded by even more greatness.Corey Quinn: What I always found to be fascinating about your work is how you wind up tying so many different concepts together in ways you wouldn't necessarily expect. For example, when I was reviewing one of your manuscripts before this went to print, you did reject one of my suggestions, which was just, retitle the entire thing. Instead of calling it The Unicorn Project. Instead, call it Gene Kim's Love Letter to Functional Programming. So what is up with that?Gene Kim: Yeah, to put that into context, for 25 years or more, I've self-identified as an ops person. The Phoenix Project was really an ops book. And that was despite getting my graduate degree in compiler design and high-speed networking in 1995. And the reason why I gravitated towards ops, because that was my observation, that that's where the saves were made. It was ops who saved the customer from horrendous, terrible developers who just kept on putting things into production that would then blow up and take everyone with it. It was ops protecting us from the bad adversaries who were trying to steal data because security people were so ineffective. But four years ago, I learned a functional programming language called Clojure and, without a doubt, it reintroduced the joy of coding back into my life and now, in a good month, I spend half the time—in the ideal—writing, half the time hanging out with the best in the game, of which I would consider this to be a part of, and then 20% of time coding. And I find for the first time in my career, in over 30 years of coding, I can write something for years on end, without it collapsing in on itself, like a house of cards. And that is an amazing feeling, to say that maybe it wasn't my inability, or my lack of experience, or my lack of sensibilities, but maybe it was just that I was sort of using the wrong tool to think with. That comes from the French philosopher Claude Lévi-Strauss. He said of certain things, “Is it a good tool to think with?” And I just find functional programming is such a better tool to think with, that notions like composability, like immutability, what I find so exciting is that these things aren't just for programming languages. And some other programming languages that follow the same vein are, OCaml, Lisp, ML, Elixir, Haskell. These all languages that are sort of popularizing functional programming, but what I find so exciting is that we see it in infrastructure and operations, too. So Docker is fundamentally immutable. So if you want to change a container, we have to make a new one. Kubernetes composes these containers together at the level of system of systems. Kafka is amazing because it usually reveals the desire to have this immutable data model where you can't change the past. Version control is immutable. So, I think it's no surprise that as our systems get more and more complex and distributed, we're relying on things like immutability, just to make it so that we can reason about them. So, it is something I love addressing in the book, and it's something I decided to double down on after you mentioned it. I'm just saying, all kidding aside is this a book for—Corey Quinn: Oh good, I got to make it worse. Always excited when that happens.Gene Kim: Yeah, I mean, your suggestion really brought to the forefront a very critical decision, which was, is this a book for technology leaders, or even business leaders, or is this a book developers? And, after a lot of soul searching, I decided no, this is a book for developers, because I think the sensibilities that we need to instill and the awareness we need to create these things around are the developers and then you just hope and pray that the book will be good enough that if enough engineers like it, then engineering leaders will like it. And if enough engineering leaders like it, then maybe some business leaders will read it as well. So that's something I'm eagerly seeing what will happen as the weeks, months, and years go by. Corey Quinn: This episode is sponsored in part by DataStax. The NoSQL event of the year is DataStax Accelerate in San Diego this May from the 11th through the 13th. I've given a talk previously called the myth of multi-cloud, and it's time for me to revisit that with... A sequel! Which is funny given that it's a NoSQL conference, but there you have it. To learn more, visit datastax.com that's D-A-T-A-S-T-A-X.com and I hope to see you in San Diego. This May.Corey Quinn: One thing that I always admired about your writing is that you can start off trying to make a point about one particular aspect of things. And along the way you tie in so many different things, and the functional programming is just one aspect of this. At some point, by the end of it, I half expected you to just pick a fight over vi versus Emacs, just for the sheer joy you get in effectively drawing interesting and, I guess, shall we say, the right level of conflict into it, where it seems very clear that what you're talking about is something thing that has the potential to be transformative and by throwing things like that in you're, on some level, roping people in who otherwise wouldn't weigh in at all. But it's really neat to watch once you have people's attention, just almost in spite of what they want, you teach them something. I don't know if that's a fair accusation or not, but it's very much I'm left with the sense that what you're doing has definite impact and reverberations throughout larger industries.Gene Kim: Yeah, I hope so. In fact, just to reveal this kind of insecurity is, there's an author I've read a lot of and she actually read this blog post that she wrote about the worst novel to write, and she called it The Yeomans Tour of the Starship Enterprise. And she says, “The book begins like this: it's a Yeoman on the Starship Enterprise, and all he does is admire the dilithium crystals, and the phaser, and talk about the specifications of the engine room.” And I sometimes worry that that's what I've done in The Unicorn Project, but hopefully—I did want to have that technical detail there and share some things that I love about technology and the things I hate about technology, like YAML files, and integrate that into the narrative because I think it is important. And I would like to think that people reading it appreciate things like our mutual distaste of YAML files, that we've all struggled trying to escape spaces and file names inside of make files. I mean, these are the things that are puzzles we have to solve, but they're so far removed from the business problem we're trying to solve that really, the purpose of that was trying to show the mistake of solving puzzles in our daily work instead of solving real problems.Corey Quinn: One thing that I found was really a one-two punch, for me at least, was first I read and give feedback on the book and then relatively quickly thereafter, I found myself at my first DevOps Enterprise Summit, and I feel like on some level, I may have been misinterpreted when I was doing my live-tweeting/shitposting-with-style during a lot of the opening keynotes, and the rest, where I was focusing on how different of a conference it was. Unlike a typical DevOps Days or big cloud event, it wasn't a whole bunch of relatively recent software startups. There were serious institutions coming out to have conversations. We're talking USAA, we're talking to US Air Force, we're talking large banks, we're talking companies that have a 200-year history, where you don't get to just throw everything away and start over. These are companies that by and large, have, in many ways, felt excluded to some extent, from the modern discussions of, well, we're going to write some stuff late at night, and by the following morning, it's in production. You don't get to do that when you're a 200-year-old insurance company. And I feel like that was on some level interpreted as me making fun of startups for quote/unquote, “not being serious,” which was never my intention. It's just this was a different conversation series for a different audience who has vastly different constraints. And I found it incredibly compelling and I intend to go back.Gene Kim: Well, that's wonderful. And, in fact, we have plans for you, Mr. Quinn.Corey Quinn: Uh-oh.Gene Kim: Yeah. I think when I say I admire the DevOps Enterprise community. I mean that I'm just so many different dimensions. The fact that these, leaders and—it's not leaders just in terms of seniority on the organization chart—these are people who are leading technology efforts to survive and win in the marketplace. In organizations that have been around sometimes for centuries, Barclays Bank was founded in the year 1634. That predates the invention of paper cash. HMRC, the UK version of the IRS was founded in the year 1200. And, so there's probably no code that goes that far back, but there's certainly values and—Corey Quinn: Well, you'd like to hope not. Gene Kim: Yeah, right. You never know. But there are certainly values and traditions and maybe even processes that go back centuries. And so that's what's helped these organizations be successful. And here are a next generation of leaders, trying to make sure that these organizations see another century of greatness. So I think that's, in my mind, deeply admirable.Corey Quinn: Very much so. And my only concern was, I was just hoping that people didn't misinterpret my snark and sarcasm as aimed at, “Oh, look at these crappy—these companies are real companies and all those crappy SAS companies are just flashes in the pan.” No, I don't believe that members of the Fortune 500 are flash in the pan companies, with a couple notable exceptions who I will not name now, because I might want some of them on this podcast someday. The concern that I have is that everyone's work is valuable. Everyone's work is important. And what I'm seeing historically, and something that you've nailed, is a certain lack of stories that apply to some of those organizations that are, for lack of a better term, ossified into their current process model, where they there's no clear path for them to break into, quote/unquote, “doing the DevOps.”Gene Kim: Yeah. And the business frame and the imperative for it is incredible. Tesla is now offering auto insurance bundled into the car. Banks are now having to compete with Apple. I mean, it is just breathtaking to see how competitive the marketplaces and the need to understand the customer and deliver value to them quickly and to be able to experiment and innovate and out-innovate the competition. I don't think there's any business leader on the planet who doesn't understand that software is eating the world and they have to that any level of investment they do involves software at some level. And so the question is, for them, is how do they get educated enough to invest and manage and lead competently? So, to me it really is like the sleeping giant awakening. And it's my genuine belief is that the next 50 years, as much value as the tech giants have created: Facebook, Amazon, Netflix, Google, Microsoft, they've generated trillions of dollars of economic value. When we can get eighteen million developers, as productive as an engineer at a tech giant is, that will generate tens of trillions of dollars of economic value per year. And so, when you generate that much economic activity, all problems become solvable, you look at climate change, you take a look at the disparity between rich and poor. All things can be fixed when you significantly change the economic economy in this way. So, I'm extremely hopeful and I know that the need for things like DevOps are urgent and important.Corey Quinn: I guess that that's probably the best way of framing this. So you wrote one version that was aimed at operators back in 2013, this one was aimed at developers, and effectively retails and clarifies an awful lot of the same points. As a historical ops person, I didn't feel left behind by The Unicorn Project, despite not being its target market. So I guess the question on everyone's mind, are you planning on doing a third iteration, and if so, for what demographic?Gene Kim: Yeah, nothing at this point, but there is one thing that I'm interested in which is the role of business leaders. And Sarah is an interesting villain. One of my favorite pieces of feedback during the review process was, “I didn't think I could ever hate Sarah more. And yet, I did find her even to be more loathsome than before.” She's actually based on a real person, someone that I worked with.Corey Quinn: That's the best part, is these characters are relatable enough that everyone can map people they know onto various aspects of them, but can't ever disclose the entire list in public because that apparently has career consequences.Gene Kim: That's right. Yes, I will not say who the character is based on but there's, in the last scene of the book that went to print, Sarah has an interesting interaction with Maxine, where they meet for lunch. And, I think the line was, “And it wasn't what Maxine had thought, and she's actually looking forward to the next meeting.” I think that leaves room for it. So one of the things I want to do with some friends and colleagues is just understand, why does Sarah act the way she does? I think we've all worked with someone like her. And there are some that are genuinely bad actors, but I think a lot of them are doing something, based on genuine, real motives. And it would be fun, I thought, to do something with Elizabeth Henderson, who we decided to start having a conversation like, what does she read? What is her background? What is she good at? What does her resume look like? And what caused her to—who in technology treated her so badly that she treats technology so badly? And why does she behave the way she does? And so I think she reads a lot of strategy books. I think she is not a great people manager, I think she maybe has come from the mergers and acquisition route that viewed people as fungible. And yeah, I think she is definitely a creature of economics, was lured by an external investor, about how good it can be if you can extract value out of the company, squeeze every bit of—sweat every asset and sell the company for parts. So I would just love to have a better understanding of, when people say they work with someone like a Sarah, is there a commonality to that? And can we better understand Sarah so that we can both work with her and also, compete better against her, in our own organizations?Corey Quinn: I think that's probably a question best left for people to figure out on their own, in a circumstance where I can't possibly be blamed for it.Gene Kim: [laughing].That can be arranged, Mr. Quinn.Corey Quinn: All right. Well, if people want to learn more about your thoughts, ideas, feelings around these things, or of course to buy the book, where can they find you?Gene Kim: If you're interested in the ideas that are in The Unicorn Project, I would point you to all of the freely available videos on YouTube. Just Google DevOps Enterprise Summit and anything that's on the plenary stage are specifically chosen stories that very much informed The Unicorn Project. And the best way to reach me is probably on Twitter. I'm @RealGeneKim on Twitter, and feel free to just @ mention me, or DM me. Happy to be reached out in whatever way you can find me. Corey Quinn: You know where the hate mail goes then. Gene, thank you so much for taking the time to speak with me, I appreciate it.Gene Kim: And Corey, likewise, and again, thank you so much for your unflinching feedback on the book and I hope you see your fingerprints all over it and I'm just so delighted with the way it came out. So thanks to you, Corey. Corey Quinn: As soon as my signed copy shows up, you'll be the first to know.Gene Kim: Consider it done. Corey Quinn: Excellent, excellent. That's the trick, is to ask people for something in a scenario in which they cannot possibly say no. Gene Kim, multiple award-winning CTO, researcher, and author. Pick up his new book, The Wall Street Journal best-selling The Unicorn Project. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on Apple Podcasts. If you hated this podcast, please leave a five-star review on Apple Podcasts and leave a compelling comment.Announcer: This has been this week's episode of Screaming in the Cloud. You can also find more Corey at ScreamingintheCloud.com or wherever fine snark is sold.This has been a HumblePod production. Stay humble.

On the show this week, we're talking updated DevOps practices for 2022 with hosts Stephanie Wong and Chloe Condon and our guests Nathen Harvey and Derek DeBellis. Nathen and Derek start the show with a thorough discussion of DORA, the research program dedicated to helping organizations improve software delivery and operations, and the state of DevOps report that Google publishes every year. This year, the DevOps research team strengthened their focus on security and discovered that one of the biggest predictors in security practice adoption is company culture. Open, communicative, and trustful company cultures are some of the best for accepting and implementing optimized security practices. Derek tells us how company cultures are measured and scored for this purpose and Nathen talks about team and individual burnout and its affects on culture. Low, medium, high, and elite teams are another indicator of culture, and Nathen explains how teams earn their label through four keys of software delivery performance. Each year, they let the data show these four clusters of team performance. But this year there were only three, and Derek talks more about this phenomenon and why the elite cluster seems to have disappeared. When operational performance analysis was added, the four clusters reemerged and were renamed to better suit the new analysis metrics. Nathen details these four new clusters: starting, which performs neither well nor poorly and may be just starting out; flowing, teams that are performing well across throughput, stability, and operational performance; slowing teams, which don't have high throughput but excel in other areas; and retiring teams, which are reliable but not actively developing projects. We discuss how companies may shift from one cluster to another and how much context can affect this shift. We talk about key findings in the 2022 DevOps report, especially in the security space. Some of the most notable include the adoption of DevOps security practices and the decreased incidence of burnout on teams who leverage security practices. Nathen and Derek elaborate on how this year's research changed from last year and what remained the same. Nathen Harvey Nathen works with teams helping them learn about and apply the findings of our research into high performing teams. He's been involved in the DevOps community for more than a decade. Derek DeBellis Derek is a Quantitative User Experience Researcher at Google, where Derek focuses on survey research, logs analysis, and figuring out ways to measure concepts central to product development. Derek has published on Human-AI interaction, the impact of Covid-19's onset on smoking cessation, designing for NLP errors and the role of UX in ensuring privacy. Cool things of the week Try out Cloud Spanner databases at no cost with new free trial instances blog Chipotle Is Testing More Artificial Intelligence Solutions To Improve Operations article Gyfted uses Google Cloud AI/ML tools to match tech workers with the best jobs blog Interview 2022 Accelerate State of DevOps Report blog DevOps site 2022 State of the DevOps Report Report site DORA site DORA Community site SLSA site Security Software Development Framework site Westrum organizational culture site Google finds culture, not tech, is the biggest predictor of DevOps security outcomes article GCP Podcast Episode 205: DevOps with Nathen Harvey and Jez Humble podcast GCP Podcast Episode 284: State of DevOps Report 2021 with Nathen Harvey and Dustin Smith podcast GCP Podcast Episode 290: Resiliency at Shopify with Camilo Lopez and Tai Dickerson podcast What's something cool you're working on? Steph is working on talks for DevFest Nantes and a Google Cloud dev conference in London. She'll be talking about subsea fiber optics and Google Cloud networking products. Chloe is a Noogler, so she's been working on learning as much as she can! She is excited to make her podcast debut this week! Hosts Stephanie Wong and Chloe Condon