Podcasts about software delivery

A few weeks after Dynatrace acquired DevCycle, Michael Beemer and Andrew Norris discussed on The New Stack Makers podcast how feature flagging is becoming a critical safeguard in the AI era. By integrating DevCycle's feature flagging into the Dynatrace observability platform, the combined solution delivers a “360-degree view” of software performance at the feature level. This closes a key visibility gap, enabling teams to see exactly how individual features affect systems in production. As “agentic development” accelerates—where AI agents rapidly generate code—feature flags act as a safety net. They allow teams to test, control, and roll back AI-generated changes in live environments, keeping a human in the loop before full releases. This reduces risk while speeding enterprise adoption of AI tools. The discussion also highlighted support for the Cloud Native Computing Foundation's OpenFeature standard to avoid vendor lock-in. Ultimately, developers are evolving into “conductors,” orchestrating AI agents with feature flags as their baton.   Learn more from The New Stack about the latest around AI enterprise development:  Why You Can't Build AI Without Progressive Delivery  Beyond automation: Dynatrace unveils agentic AI that fixes problems on its own  Join our community of newsletter subscribers to stay on top of the news and at the top of your game.   

Peter Maddison and Dave Sharrock sit down with Steve Pereira, founder of Visible Flow Consulting, to talk about something most organizations get backwards: the obsession with efficiency at the expense of actual flow.Steve works with large companies to improve operational performance through value stream mapping and continuous delivery. But the conversations he keeps having aren't about cutting costs. They're about untethering capable people from the systems that are quietly holding them back.In this episode, the three dig into why high utilization is often the enemy of good work, how lean thinking applies to knowledge work without losing what makes knowledge work different, and why adding AI on top of a broken system just makes things break faster.If your organization feels like it should be doing more than it is, this one's worth your time. And if you want all 4 takeaways, don't miss the last few minutes of the episode.This week´s takeaways: Step back from the work to look at how the work works. Whether it's a value stream mapping session or a quiet moment of reflection, intentional distance helps you see not just whether the saw is dull, but whether you're sawing the right tree.High utilization is not efficiency. Running people and teams at full capacity removes the slack needed to respond, adapt, and make good decisions. Optimal is closer to 80 percent. The rest needs to be budgeted, not eliminated.Understand your system before adding new tools. Whether it's AI, automation, or the latest framework, bolting new capabilities onto a system you don't fully understand tends to make existing problems worse, not better. Map first. Then act.Extra Resources:

Dynatrace is at a pivotal point, expanding beyond traditional observability into a platform designed for autonomous operations and security powered by agentic AI. In an interview on *The New Stack Makers*, recorded at the Dynatrace Perform conference, Chief Technology Strategist Alois Reitbauer discussed his vision for AI-managed production environments. The conversation followed Dynatrace's acquisition of DevCycle, a feature-management platform. Reitbauer highlighted feature flags—long used in software development—as a critical safety mechanism in the age of agentic AI. Rather than allowing AI agents to rewrite and deploy code, Dynatrace envisions them operating within guardrails by adjusting configuration settings through feature flags. This approach limits risk while enabling faster, automated decision-making. Customers, Reitbauer noted, are increasingly comfortable with AI handling defined tasks under constraints, but not with agents making sweeping, unsupervised changes. By combining AI with controlled configuration tools, Dynatrace aims to create a safer path toward truly autonomous operations. Learn more from The New Stack about the latest in progressive delivery: Why You Can't Build AI Without Progressive Delivery Continuous Delivery: Gold Standard for Software Development Join our community of newsletter subscribers to stay on top of the news and at the top of your game.  Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

AI coding tools are writing more code than ever, but your software isn't shipping any faster. Welcome to the AI Paradox and the solution, intelligent orchestration.Bill Staples, CEO of GitLab, explains why AI-accelerated coding is actually creating massive downstream bottlenecks in code reviews, security checks, and deployment, and why adding more AI tools only makes the problem worse. GitLab's solution: intelligent orchestration across the entire software development lifecycle.You'll discover:✅ The "AI Paradox:" why faster coding isn't translating into faster software delivery✅ How tool fragmentation and context-switching are killing developer productivity✅ Why agents that thrive on context fail when your tools are siloed✅ The "inner loop architecture" that makes AI agents 40% more accurate and 25% faster✅ How GitLab's intelligent orchestration approach combines workflows, context, and guardrails✅ Why mid-level developers are about to become strategic orchestrators (not just coders)✅ The exact metrics CIOs should track, and why "lines of code" is the wrong one✅ First steps: audit, consolidate, and pilot before going all-in on AI⏱️ TIMESTAMPS0:00 The AI Paradox: Why faster coding doesn't mean faster delivery1:10 How tool fragmentation creates developer bottlenecks3:40 Why AI agents make complexity worse (not better)5:12 Solving the AI automation problem: people, process, and technology6:36 Inner loop architecture: co-locating agents and data9:14 Intelligent orchestration: workflows, context, and guardrails10:32 How GitLab's knowledge graph supercharges agent accuracy12:49 Universal guardrails for humans and AI agents13:39 Real-world results: 2-3x more merge requests, pipeline fixes in minutes15:00 Common threads driving customer success16:36 How AI transforms the mid-level developer's role19:06 Advice for CIOs and CTOs putting this into practice20:49 First steps: audit, measure, and pilot22:45 Core metrics to evaluate AI's real value25:02 Wrap-up

What really happens when AI helps teams write code faster, but everything else in the delivery process starts to slow down? In this episode of Tech Talks Daily, I'm joined once again by returning guest and friend of the show, Martin Reynolds, Field CTO at Harness. It has been two years since we last spoke, and a lot has changed since then. Martin has relocated from London to North Carolina, gaining back hours of his working week. Still, the bigger shift has been in how AI is reshaping software delivery inside modern enterprises. Our conversation centers on what Martin calls the AI velocity paradox. Development teams are producing more code at speed, often thanks to AI coding agents, yet testing, security, governance, and release processes are struggling to keep up. The result is a growing gap between how fast software is written and how safely it can be delivered.  Martin shares research showing how this imbalance is already leading to production incidents, hidden vulnerabilities, and mounting technical debt. We also dig into why this AI-driven transition feels different from previous waves, such as cloud, mobile, or DevOps. Many of the same concerns around security, trust, and control still exist, but this time, everything is happening far faster. Martin explains why AI works best as a human amplifier, strengthening good engineering practices while exposing weak ones sooner than ever before. A significant theme in the episode is visibility. From shadow AI usage to expanding attack surfaces, Martin outlines why security teams are finding it harder to see where AI is being used and how data is flowing through systems. Rather than slowing teams down, he argues that the answer lies in embedding governance directly into delivery pipelines, making security automatic rather than an afterthought. We also explore the rise of agentic AI in testing, quality assurance, and security, where specialized agents act like virtual teammates. When well-designed, these agents help developers stay focused while improving reliability and resilience throughout the lifecycle. If you are responsible for engineering, platform, or security teams, this episode offers a grounded look at how to balance speed with responsibility in an AI-native world. As AI becomes part of every stage of software delivery, are your processes designed to safely absorb that change, or are they quietly becoming the bottleneck? Useful Links Learn More About Harness The State of AI in Engineering The State of AI Application Security EngineeringX Follow Harness on LinkedIn Connect With Martin Reynolds Thanks to our sponsors, Alcor, for supporting the show.

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!

What happens when you need to ship software in environments where failure isn't just expensive, it's catastrophic? Ivan Gekht, CEO of Gehtsoft, joins Peter and Dave to challenge how we think about agile delivery in high-stakes, regulated systems.Forget the innovation lab. Ivan argues that real innovation happens 10 minutes at a time, every day, at your desk. He shares why learning without outcomes is just an expensive distraction, why retrospectives reveal more than sprint planning ever will, and how the biggest transformation killer isn't resistance, it's apathy.Plus, the dinner party analogy that will change how you negotiate scope vs. time, and why organizations that obsess over features are asking the wrong questions entirely.Key Topics:Why "nobody cares" is the hardest transformation problem to solveThe reversed iron triangle: hitting dates by flexing scopeTheory of Inventive Problem Solving (TRIZ) and structured innovationGoals vs. features: reframing conversations with leadershipWhy agile fails when it becomes anarchyThis Week's Takeaways:Language and framing matter more than we think. Finding the right words and the right way to present ideas can genuinely shift how change happens in an organization.The Theory of Inventive Problem Solving deserves a deeper look. Innovation isn't the big thing happening in the cool kids area; it's the thing that happens every day at your desk.The dinner party analogy is going straight into my next executive presentation. When sales want locked dates and fixed scope, this framework shows why that's wishful thinking, and what actually works instead.We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

What actually separates a fully engaged mob from one that feels flat, quiet, or stuck? And why does that difference matter far beyond team morale? In this episode of the Mob Mentality Show, we explore how team engagement directly impacts software delivery, learning, and long-term sustainability. Drawing from real mob programming experiences—ranging from high-energy, large-group collaboration to small teams struggling with disengagement—we unpack the patterns behind why engagement rises or fades. Rather than offering a one-size-fits-all playbook, this conversation treats engagement as a systems and complexity problem. We discuss how engagement shows up differently in quiet vs. loud mobs, how personal context and learning overload can influence participation, and why disengagement is often a signal—not a character flaw. You'll hear practical ways facilitators and teams can probe, sense, and respond when engagement drops, including: - The difference between intrinsic and extrinsic motivation in mob settings - When small format changes help—and when they're only a temporary band-aid - How psychological safety affects learning, contribution, and retention - Techniques for surfacing hidden confusion without negatively calling people out - Why repeated work and lack of progress quietly drain motivation - When disengagement points to deeper systemic or environmental issues We also connect engagement to outcomes leaders care about: flow, learning speed, delivery quality, and business impact. This isn't about forcing fun or “rah-rah” energy—it's about creating conditions where people want to contribute, can contribute, and see the value of innovating together. Whether you're a developer, facilitator, tech lead, or engineering manager, this episode offers concrete signals to watch for and experiments to try—while respecting the complexity of human systems. If you've ever wondered why one mob feels alive and another feels exhausting, this conversation can help you see what's really going on beneath the surface. Video and Show Notes: https://youtu.be/P0-PWstQhqk  

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/408Michael Nygard - Chief Architect at Nubank & Author of "Release It!"Charles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantFULL TALK TITLEBuilding Software That Survives: Autonomy, Architecture & Alignment at ScaleRESOURCESMichaelhttps://www.linkedin.com/in/mtnygardhttps://twitter.com/mtnygardhttp://www.michaelnygard.comCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comDESCRIPTIONMichael Nygard, author of the influential "Release It!" and Chief Architect at Nuank, discusses his journey from programmer to technical leader.In this conversation, he shares insights from major transformation projects at Sabre and Nubank, exploring the nuances of centralization versus autonomy, the often-misunderstood implications of Conway's Law, and how architectural boundaries can reduce the need for constant organizational alignment.He emphasizes that effective technical leadership involves more than reorganizations - it requires understanding communication structures, celebrating the right behaviors, and creating systems that enable teams to operate independently within well-defined boundaries.RECOMMENDED BOOKSMichael Nygard • Release It! 2nd Edition • https://amzn.to/3WJeKV8Michael Nygard • Release It! 1st Edition • https://amzn.to/3XCkiRfRichard Monson-Haefel • 97 Things Every Software Architect Should Know • https://amzn.to/3JdRYU2Charles Humble • Professional Skills for Software Engineers • https://www.conissaunce.com/professional-skills-shortcutPatterson, Grenny, McMillan & Switzler • Crucial Conversations • https://amzn.to/3LhGHTaYevgeniy Brikman • Fundamentals of DevOps and Software Delivery • https://amzn.to/3WMPMFUTod Golding • Building Multi-Tenant SaaS Architectures • https://amzn.to/3YfM49oJacqui Read • Communication Patterns • https://amzn.to/3E37lvvMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQJames Stanier • Become an Effective Software Engineering Manager • https://amzn.to/3vHrx1EBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/405Yevgeniy "Jim" Brikman - Author of "Fundamentals of DevOps and Software Delivery" & Co-Founder of GruntworkKief Morris - Author of "Infrastructure as Code" & Distinguished Engineer at ThoughtworksRESOURCESYevgeniy (Jim)https://bsky.app/profile/brikis98.bsky.socialhttps://twitter.com/brikis98https://github.com/brikis98/https://www.linkedin.com/in/jbrikmanhttps://www.ybrikman.comKiefhttps://bsky.app/profile/kief.comhttps://twitter.com/kiefhttps://github.com/kiefhttps://www.linkedin.com/in/kiefmorrishttps://infrastructure-as-code.comhttps://kief.comLinkhttps://terragrunt.gruntwork.ioDESCRIPTIONYevgeniy (Jim) Brikman, author of "Fundamentals of DevOps and Software Delivery", discusses his journey from app developer to DevOps advocate, triggered by LinkedIn's deployment crisis that required freezing all product development for months. The discussion with Kief Morris explores the practical definition of DevOps as efficient software delivery methodology, the relationship between infrastructure as code and application orchestration tools, the necessity of frameworks over custom wrapper scripts, and emerging paradigms including infrastructure from code, infrastructure as graph models, and interactive runbooks.Jim emphasizes that while new approaches are interesting, maturity and standardization in existing tools often provides more value than constantly chasing new technologies.RECOMMENDED BOOKSYevgeniy Brikman • Fundamentals of DevOps and Software Delivery • https://amzn.to/3WMPMFUYevgeniy Brikman • Terraform: Up and Running • https://amzn.to/4otpxQLYevgeniy Brikman • Hello, Startup • https://amzn.to/3JmV0VRKief Morris • Infrastructure as Code • https://amzn.to/4e6EBQcMauricio Salatino • Platform Engineering on Kubernetes • https://amzn.to/3X14qZKCharity Majors, Liz Fong-Jones & George Miranda • Observability Engineering • https://amzn.to/38scbmaBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

Former GitHub CEO Thomas Dohmke's claim that AI-based development requires progressive delivery frames a conversation between analyst James Governor and The New Stack's Alex Williams about why modern release practices matter more than ever. Governor argues that AI systems behave unpredictably in production: models can hallucinate, outputs vary between versions, and changes are often non-deterministic. Because of this uncertainty, teams must rely on progressive delivery techniques such as feature flags, canary releases, observability, measurement and rollback. These practices, originally developed to improve traditional software releases, now form the foundation for deploying AI safely. Concepts like evaluations, model versioning and controlled rollouts are direct extensions of established delivery disciplines. Beyond AI, Governor's book “Progressive Delivery” challenges DevOps thinking itself. He notes that DevOps focuses on development and operations but often neglects the user feedback loop. Using a framework of four A's — abundance, autonomy, alignment and automation — he argues that progressive delivery reconnects teams with real user outcomes. Ultimately, success isn't just reliability metrics, but whether users are actually satisfied. Learn more from The New Stack about progressive delivery: Mastering Progressive Hydration for Enhanced Web Performance Continuous Delivery: Gold Standard for Software Development Join our community of newsletter subscribers to stay on top of the news and at the top of your game.   Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

AWS Principal Solutions Architect Wallace Printz explains how agents are reshaping SaaS business models, pricing strategies, and technical architectures.Topics Include:Wallace Printz discusses agentic workloads transforming SaaS with largest AWS customersNew interaction models include generative UI, voice agents, and proactive workAgents extending SaaS products to interact with external systems and businessesVirtual teammates enabling cross-department collaboration and upskilling non-expert users effectivelyMonetization strategies evolving as predictable costs become variable with agentsThree patterns: dedicated agents, shared agents, and multi-tenant personalized agentsMulti-tenant agents enable hyper-personalized experiences using individual tenant context enrichmentAgent-centric business strategy requires real assessment beyond AI hype cycleAgent orchestration complexity grows with multiple specialized agents interacting togetherTenant isolation requires JWT tokens and AWS Bedrock Agent Core identityCost-per-tenant management needs LLM throttling, tiering, and unified control planeMulti-tenancy creates sticky personalized experiences; AWS white paper releasing soonParticipants:Wallace Printz - Principal Solution Architect, Amazon Web ServicesSee how Amazon Web Services gives you the freedom to migrate, innovate, and scale your software company at https://aws.amazon.com/isv/

Better late than never. Small Batches returns in 2025. In this episode, Adam shares his learnings over the past year through the works of the Zen master Kaizenji. This is special follow-up episode to the previous episodes on the Zen of Programming. ★ Support this podcast on Patreon ★

Sujeevan und Dirk reden über den fünften Geburtstag des TILpod, den Arrival Failure, Secure SDLC (Teil 2), das kleine Handbuch des Stoizismus, Chabos und Lychee.

In this episode, Shiv is in conversation with Naresh Choudhary, Senior Vice President, Quality & Productivity, Infosys Ltd.Naresh shares his career journey starting from humble beginnings in Mumbai, studying engineering at VJTI, working at Arvind Mills, and eventually contributing to Infosys for 25 years. The discussion covers his transition from manufacturing to IT, the influence of mentors, various roles at Infosys, and the importance of reframing roles. Naresh also emphasizes the value of great work, networking, mentorship, and maintaining a work-life balance. He talks about driving innovation and change management effectively within a large organization through transparent communication, planning, and continuous feedback. Finally, Naresh offers personal practices like journaling, exercising, and separating work from family time to stay grounded and calm.00:00 Welcome and Introduction00:23 Early Career and Education02:00 Transition to Infosys03:43 Roles and Responsibilities at Infosys07:16 Mentorship and Career Growth10:28 Defining Great Work15:32 Overcoming Self-Doubt and Imposter Syndrome19:28 The Importance of Mentors24:23 Networking and Time Management29:19 Clearing the Mind for Focus29:51 Work-Life Balance and Breaks30:59 Organizational Change and Trust33:51 Planning and Transparency in Change34:51 Process Over Tools36:04 Sponsorship and Milestone Reviews37:46 Encouraging Knowledge Sharing43:58 Innovation and Idea Management47:33 Staying Grounded Amidst Responsibilities53:00 Personal Practices for Balance56:48 Conclusion and Final ThoughtsBio:In his stint at Infosys over 2 decades, Naresh has worked in different roles in Software Delivery, Consulting, Quality Assurance, Open Source, Enterprise Platforms, Products, Tools & Technology that have provided him opportunities to work on key transformation programs.Naresh has experience in Software Development, Quality System Design, Process definition, Implementation and Consulting, Product & Platform Engineering, Software Reuse, Knowledge Management, Training, Audits and Assessments. He possesses a sound understanding of various quality models, methodologies and frameworks like CMMI, ISO, Six Sigma, MBNQA, AI, Automation,  Agile, DevSecOps & SRE.Naresh participates on several product councils and advisory boards with Infosys' global technology partners and is currently leading the effort on reimagining the tooling, engineering excellence, digital platforms, Lean and automation landscape for the enterpriseHe is a self confessed Foodie, History enthusiast, Amateur Chef, Motivational Speakerhttps://www.linkedin.com/in/nareshchoudhary/

Watch the podcast to hear experts from Broadcom, Google Cloud and stackArmor discuss how agencies accelerate software delivery, improve customer experience and maintain compliance while meeting deadlines and staying within budget. Gain insights into how the Federal Government navigates FedRAMP's evolving framework, leverages AI tools for portfolio management and breaks down information silos with a unified platform.

I invited Egil Østhus to unpack a simple idea that tends to get lost in release day pressure. DevOps gets code to production quickly, but users experience features, not pipelines. Egil is the founder of Unleash, an open source feature management platform with close to 30 million downloads, and he argues that the next step is FeatureOps. It is a mindset and a set of practices that separate deployment from release, so teams can place code in production, light it up for a small cohort, learn, and only then scale out with confidence. Here is the thing. Controlled rollouts, clear telemetry, and fast rollback reduce risk without slowing teams down. Egil explains how FeatureOps connects engineering effort to business outcomes through gradual exposure, full stack experimentation, and what he calls surgical rollback. Instead of ripping out an entire release when one part misbehaves, teams can disable the offending capability and keep the rest of the value in place. It sounds straightforward because it is, and that is the point. Less drama, more learning, better results. We also talk about culture. When releases repeatedly disappoint, trust between product and engineering frays. Egil shares examples where Unleash helped a hardware and software company move from blame to shared ownership by making rollout plans visible and collaborative. Another client, an ERP vendor, discovered that early feedback from a small group of users allowed them to ship a leaner version that met the need without months of extra scope. That is how FeatureOps saves money and tempers expectations while still delighting customers. AI enters the story too. Code is shipping faster, but reliability can wobble when autogenerated changes move through pipelines. Egil sees feature management as a practical control plane for this new reality. Feature flags provide a real time safety net and, if needed, a kill switch for AI powered functionality. Teams can keep experimenting while protecting users and brand equity. If you want to move beyond release day roulette, this episode offers a practical playbook. We cover privacy first design, open source flexibility, and why metadata from FeatureOps will help leaders study how their organizations truly build. To learn more, visit getunleash.io or search for Unleash in your favorite tool, then tell me how you plan to measure your next rollout's impact. ********* Visit the Sponsor of Tech Talks Network: Land your first job  in tech in 6 months as a Software QA Engineering Bootcamp with Careerist https://crst.co/OGCLA      

Asgaut Mjølne Söderbom and Ola Hast, two developers with Sparebank1 speak about their journey towards continuous deployment and pair programming. During the conversation, they share how they use the "waste clock" to identify areas of improvement or how TDD helps them deliver high-quality code. Read a transcript of this interview: https://bit.ly/4lNvYgI Subscribe to the Software Architects' Newsletter for your monthly guide to the essential news and experience from industry peers on emerging patterns and technologies: https://www.infoq.com/software-architects-newsletter Upcoming Events: InfoQ Dev Summit Munich (October 15-16, 2025) Essential insights on critical software development priorities. https://devsummit.infoq.com/conference/munich2025 QCon San Francisco 2025 (November 17-21, 2025) Get practical inspiration and best practices on emerging software trends directly from senior software developers at early adopter companies. https://qconsf.com/ QCon AI New York 2025 (December 16-17, 2025) https://ai.qconferences.com/ QCon London 2026 (March 16-19, 2026) https://qconlondon.com/ The InfoQ Podcasts: Weekly inspiration to drive innovation and build great teams from senior software leaders. Listen to all our podcasts and read interview transcripts: - The InfoQ Podcast https://www.infoq.com/podcasts/ - Engineering Culture Podcast by InfoQ https://www.infoq.com/podcasts/#engineering_culture - Generally AI: https://www.infoq.com/generally-ai-podcast/ Follow InfoQ: - Mastodon: https://techhub.social/@infoq - X: https://x.com/InfoQ?from=@ - LinkedIn: https://www.linkedin.com/company/infoq/ - Facebook: https://www.facebook.com/InfoQdotcom# - Instagram: https://www.instagram.com/infoqdotcom/?hl=en - Youtube: https://www.youtube.com/infoq - Bluesky: https://bsky.app/profile/infoq.com Write for InfoQ: Learn and share the changes and innovations in professional software development. - Join a community of experts. - Increase your visibility. - Grow your career. https://www.infoq.com/write-for-infoq

Ever wonder how technology leaders adapt between nimble startups and tech giants, or what it truly takes to ship software that matters? In this insightful TBCY episode (S7 E062), Ashutosh Garg sits down with Thanos Diacakis—software delivery coach, fractional CTO, patent-holder, and independent consultant—to unpack 25+ years of lessons from the front lines of engineering and startup life.Below you'll find key topics explored in the episode, organized by timestamp, complete with guiding questions to help you navigate the most relevant insights for your journey.

Rob Zuber sits down with Tara Hernandez, VP of Developer Productivity at MongoDB and former Netscape engineer who helped create early continuous integration systems, to explore strategic frameworks for build vs. buy decisions in modern software delivery.Hernandez shares insights from scaling MongoDB's proprietary CI system—processing 10 engineer years of compute daily—and reveals how organizations can evaluate when custom infrastructure drives competitive advantage versus when strategic partnerships accelerate growth. Her perspective on navigating the evolving landscape of CI/CD tooling offers actionable guidance for engineering leaders balancing innovation with operational efficiency.Have someone in mind you'd like to hear on the show? Reach out to us on X at @CircleCI!

Join Thoughtworks CTO Rachel Laycock for a candid look at what AI-first software delivery really means, beyond the buzzwords. In this episode, she discusses how this emerging technology is reshaping software development life cycles, and how it can be used to tackle the most complex modernization challenges. If you're navigating the fast-changing landscape of tech strategy, this one's for you.   Host: Kimberly Boyd Guest: Rachel Laycock, CTO at Thoughtworks

You Don't Need Agile... YES You Do Need Agile!When Agile was introduced many years ago, it gave software delivery an option to do things differently. From there, many offshoots have come from Agile that come from Agile that provide even more options for Software Delivery.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Can agile teams really move fast without breaking stuff? In this episode, Dave and Peter dig into one of the biggest tensions in modern software delivery: the push for speed versus the need to manage risk.They unpack the idea that when agile is done right, it actually helps reduce risk, not amplify it. You'll hear stories and analogies (yep, including a messy kitchen and airplane cockpits) that bring this idea to life. Along the way, they highlight why teams that obsess over "faster delivery" often end up with systems that are, well, kind of fragile.Whether you're navigating compliance hurdles, trying to foster psychological safety, or just figuring out how to move fast without chaos, this conversation brings a grounded, practical take on how agile and risk can work together, not against each other. This week's takeaways:Learning continuously is more powerful than just moving quicklyTeams should feel safe to say “something doesn't feel right”Focus on what's working, not just what's broken

BONUS: From Waterfall to Flow—Rethinking Mental Models in Software Delivery With Henrik Mårtensson In this BONUS episode, we explore the origins and persistence of waterfall methodology in software development with management consultant Henrik Mårtensson. Based on an article where he details the history of Waterfall, Henrik explains the historical context of waterfall, challenges the mental models that keep it alive in modern organizations, and offers insights into how systems thinking can transform our approach to software delivery. This conversation is essential for anyone looking to understand why outdated methodologies persist and how to move toward more effective approaches to software development. The True Origins of Waterfall "Waterfall came from the SAGE project, the first large software project in history, where they came up with a methodology based on an economic analysis." Henrik takes us on a fascinating historical journey to uncover the true origins of waterfall methodology. Contrary to popular belief, the waterfall approach wasn't invented by Winston Royce but emerged from the SAGE project in the 1950s. Bennington published the original paper outlining this approach, while it was Bell and Tayer who later named it "waterfall" when referencing Royce's work. Henrik explains how gated process models eventually led to the formalized waterfall methodology and points out that an entire generation of methods existed between waterfall and modern Agile approaches that are often overlooked in the conversation. In this segment we refer to:  The paper titled “Production of Large Computer Programs” by Herbert D. Benington (direct PDF link) Updated and re-published in 1983 in Annals of the History of Computing ( Volume: 5, Issue: 4, Oct.-Dec. 1983) Winston Royce's paper from 1970 that erroneously is given the source of the waterfall term. Direct PDF Link. Bell and Thayer's paper “Software Requirements: Are They Really A Problem?”, that finally “baptized” the waterfall process. Direct PDF link.   Mental Models That Keep Us Stuck "Fredrik Taylor's model of work missed the concept of a system, leading us to equate busyness with productivity." The persistence of waterfall thinking stems from outdated mental models about work and productivity. Henrik highlights how Frederick Taylor's scientific management principles continue to influence software development despite missing the crucial concept of systems thinking. This leads organizations to equate busyness with productivity, as illustrated by Henrik's anecdote about 50 projects assigned to just 70 people. We explore how project management practices often enforce waterfall thinking, and why organizations tend to follow what others do rather than questioning established practices. Henrik emphasizes several critical concepts that are often overlooked: Systems thinking Deming's principles Understanding variation and statistics Psychology of work Epistemology (how we know what we know) In this segment, we refer to:  Frederik Taylor's book “The Principles of Scientific Management” The video explaining why Project Management leads to Coordination Chaos James C. Scott's book, “Seeing Like a State” Queueing theory Little's Law The Estimation Trap "The system architecture was overcomplicated, and the organizational structure followed it, creating a three-minute door unlock that required major architectural changes." Henrik shares a compelling story about a seemingly simple feature—unlocking a door—that was estimated to take three minutes but actually required significant architectural changes due to Conway's Law. This illustrates how organizational structures often mirror system architecture, creating unnecessary complexity that impacts delivery timelines. The anecdote serves as a powerful reminder of how estimation in software development is frequently disconnected from reality when we don't account for systemic constraints and architectural dependencies. In this segment, we refer to Conway's Law, the observation that explicitly called out how system architecture is so often linked to organizational structures. Moving Beyond Waterfall "Understanding queueing theory and Little's Law gives us the tools to rethink flow in software delivery." To move beyond waterfall thinking, Henrik recommends several resources and concepts that can help transform our approach to software development. By understanding queueing theory and Little's Law, teams can better manage workflow and improve delivery predictability. Henrik's article on coordination chaos highlights the importance of addressing organizational complexity, while James C. Scott's book "Seeing Like a State" provides insights into how central planning often fails in complex environments. About Henrik Mårtensson Henrik Mårtensson is a management consultant specializing in strategy, organizational development, and process improvement. He blends Theory of Constraints, Lean, Agile, and Six Sigma to solve complex challenges. A published author and licensed ScrumMaster, Henrik brings sharp systems thinking—and a love of storytelling—to help teams grow and thrive. You can link with Henrik Mårtensson on LinkedIn and connect with Henrik Mårtensson on Twitter.

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!

(06:49) Brought to you by Lemon.io⁠Lemon.io⁠ is your go-to platform for hiring top-tier, pre-vetted software engineers from Europe and Latin America. You'll get matched with your developer in just 48 hours.Tech Lead Journal listeners get 15% off your first 4 weeks of work at ⁠lemon.io⁠.Want to learn the key principles and future of DevOps that can help you ship code faster and more reliably?In this episode, I sit down with Yevgeniy Brikman, co-founder of Gruntwork and author of “Terraform: Up & Running,” to discuss his upcoming book, “The Fundamentals of DevOps and Software Delivery.”We explore:- Common pitfalls and anti-patterns in DevOps implementations- The concept of “minimum effective dose” and "incrementalism" in adopting technologies- Why application developers should understand infrastructure and software delivery- The future of DevOps, including “infrastructureless” and the impact of GenAI- The importance of “secure-by-default” practices in modern software development- Recent changes in open source licensing and their impact on the tech industry- The power of continuous learning and sharing knowledge in tech careersListen out for:(00:02:15) Career Turning Points(00:08:32) Deliberate Time for Learning(00:16:27) Transitioning from App Dev to Infra (00:24:19) Understanding How to Deliver Software(00:32:05) Minimum Effective Dose(00:40:34) DevOps Antipatterns(00:44:02) Incrementalism(00:49:37) The Future of DevOps and Software Delivery(01:10:39) Recent Trend in Open Source License Changes(01:20:32) 3 Tech Lead Wisdom_____Yevgeniy Brikman's BioYevgeniy (Jim) Brikman loves programming, writing, speaking, traveling, and lifting heavy things. He does not love talking about himself in the 3rd person. He is the co-founder of Gruntwork, a company that offers products & services for setting up world-class DevOps Foundations. He's also the author of three books published by O'Reilly Media: Fundamentals of DevOps and Software Delivery, Terraform: Up & Running, and Hello, Startup. Previously, he spent more than a decade building infrastructure and products that served hundreds of millions of users while working as a software engineer at LinkedIn, TripAdvisor, Cisco Systems, and Thomson Financial.Follow Yevgeniy: LinkedIn – linkedin.com/in/jbrikman X / Twitter – @brikis98 Website – ybrikman.com

In this episode of Game Changers for Government Contractors, host Michael LeJeune dives into the innovative concept of Continuous Authority to Operate (CATO) with Bryon Kroger, founder of Rise8. Bryon explains how CATO enables faster, more secure software delivery, aligning with modern DevOps practices while ensuring compliance with NIST RMF standards. Learn how this approach transforms the traditional ATO process, the benefits for government contractors and end users, and the critical role of collaboration between developers, assessors, and end-users. Bryon also shares actionable strategies for implementing CATO, overcoming challenges, and scaling operations. Whether you're navigating compliance or looking to improve your software delivery speed, this episode is packed with valuable insights to help you succeed in the GovCon space. ----- Frustrated with your government contracting journey? Join our group coaching community here: federal-access.com/gamechangers Grab my #1 bestselling book, "I'm New to Government Contract. Where Should I Start?" Here: amzn.to/4c5Vb0d

Small Batches will return in 2025. Until then, I recommend checking out the Complexity Lounge on YouTube, hosted by my friend Jocko Selberg. ★ Support this podcast on Patreon ★

In this episode, Adam reads haikus from The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book.Want more?

In this episode, Adam reads book four in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features koans from the fabled zen Master Lan-Hsi.Want more?

In this episode, Adam reads book three in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features analects from the fabled zen Master Rinzai.Want more?

In this episode, Adam reads book two in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features folktales from the fabled zen Master Noa-Op.Want more?

In this episode, Adam reads book two in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features chronicles from the fabled zen Master Ninjei.Want more?

In this episode, Adam reads the preface, forward, and introduction to The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. Want more?

In this episode, Adam welcomes Dan Slimmon, an experienced Site Reliability Engineer (SRE) to discuss aspects of incident response and troubleshooting in software engineering. Dan explains his methodology for clinical troubleshooting, the importance of maintaining a common mental model, and techniques for leading effective incident response efforts. They also delve into the value of continuous ops reviews and ongoing mental model updates to prevent issues, emphasizing the need for structured processes and effective communication.Want more?

In this episode of Small Batches, host Adam Hawkins welcomes Alex Nesbitt, a strategy expert and member of the Flow Collective, to delve into the nuances of strategic thinking. The discussion covers different types of strategies, pro-tips on strategic thinking, and how strategy relates to the concept of flight levels. Nesbitt shares insights from his extensive consulting career, touching on topics like identifying leverage points, the relationship between strategy and tactics, and why being strategic is often more critical than having a strategy. The episode also stresses the importance of having a clear vision, enabling organizational constraints, and the roles of resilience and maintenance in strategic planning. Alex mentions practical examples, resources, and tips to help software and business leaders enhance their strategic approach.Want more?

Adam discusses strategy in preparation for the next episode.Want more?

Adam discusses three (new-ish) ideas from time on a new gemba. Want more?

Adam describes using Hexagonal Architecture, also known as Ports and Adapters, for software delivery excellence.Want more?

In this episode we dive into the exciting release of Elixir 1.17.0-rc.1 and other news from the community. Our main segment features an in-depth interview with Ellie Fairholm and Josep Giralt D'Lacoste about their new Elixir book "Engineering Elixir Applications - Navigate Each Stage of Software Delivery with Confidence." We explore their professional experiences, the concept of "BeamOps," and the unique DevOps challenges and advantages in the BEAM ecosystem. Ellie and Josep share insights about the writing process, their collaboration, and what's next for the book. Tune in to hear all this and more! Show Notes online - http://podcast.thinkingelixir.com/206 (http://podcast.thinkingelixir.com/206) Elixir Community News - https://x.com/josevalim/status/1797607009715691637 (https://x.com/josevalim/status/1797607009715691637?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim announces the release of Elixir 1.17.0-rc.1. - https://hexdocs.pm/elixir/1.17/gradual-set-theoretic-types.html (https://hexdocs.pm/elixir/1.17/gradual-set-theoretic-types.html?utm_source=thinkingelixir&utm_medium=shownotes) – Introduction to gradual set-theoretic types in Elixir 1.17. - https://github.com/elixir-lang/elixir/blob/v1.17/CHANGELOG.md (https://github.com/elixir-lang/elixir/blob/v1.17/CHANGELOG.md?utm_source=thinkingelixir&utm_medium=shownotes) – Detailed changelog of Elixir 1.17.0-rc.1. - Added mix profile.tprof profiler in Erlang/OTP 27+ and Deprecated mix profile.cprof and mix profile.eprof. - https://2024.elixirconf.com/ (https://2024.elixirconf.com/?utm_source=thinkingelixir&utm_medium=shownotes) – Information about ElixirConfUS 2024, including keynotes, speakers, and training. - David speaking on “Dancing with Data, Guide to ETLs” at ElixirConfUS 2024. - Mark speaking on “Elixir & AI - Creating Autonomous Agents with LangChain” at ElixirConfUS 2024. - https://dashbit.co/blog/elixir-ml-s1-2024-mlir-arrow-instructor (https://dashbit.co/blog/elixir-ml-s1-2024-mlir-arrow-instructor?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim's post on the Dashbit blog discussing the state of ML in Elixir in 2024. - https://mlir.llvm.org/ (https://mlir.llvm.org/?utm_source=thinkingelixir&utm_medium=shownotes) – Introduction of MLIR (Multi-Level Intermediate Representation) in Elixir's ML projects. - Broader ML/AI community and new projects in Elixir, including instructor_ex and Elixir LangChain. - https://x.com/germsvel/status/1796127412511551857 (https://x.com/germsvel/status/1796127412511551857?utm_source=thinkingelixir&utm_medium=shownotes) – German Velasco's video showcasing new OTP 27 process labels feature. - https://www.youtube.com/watch?v=XNQhDl4a9Ko (https://www.youtube.com/watch?v=XNQhDl4a9Ko?utm_source=thinkingelixir&utm_medium=shownotes) – Google algorithm leak exposed through a GitHub project explained using Elixir. - https://x.com/akoutmos/status/1796637514704273870 (https://x.com/akoutmos/status/1796637514704273870?utm_source=thinkingelixir&utm_medium=shownotes) – Akoutmos discusses the Google algorithm leak and its analysis using Elixir. - https://hexdocs.pm/googleapicontent_warehouse/api-reference.html (https://hexdocs.pm/google_api_content_warehouse/api-reference.html?utm_source=thinkingelixir&utm_medium=shownotes) – Hexdocs publish the Google algorithm API reference. - https://ipullrank.com/google-algo-leak (https://ipullrank.com/google-algo-leak?utm_source=thinkingelixir&utm_medium=shownotes) – Analysis of Google's algorithm leak and relevancy to Elixir. - https://x.com/PJUllrich/status/1796198764681506898 (https://x.com/PJUllrich/status/1796198764681506898?utm_source=thinkingelixir&utm_medium=shownotes) – Introducing Crawly, an application framework for web crawling and data extraction. - https://github.com/elixir-crawly/crawly (https://github.com/elixir-crawly/crawly?utm_source=thinkingelixir&utm_medium=shownotes) – GitHub repository for the Crawly web crawling framework. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://pragprog.com/titles/beamops/engineering-elixir-applications/ (https://pragprog.com/titles/beamops/engineering-elixir-applications/?utm_source=thinkingelixir&utm_medium=shownotes) – PragProg book listing - https://twitter.com/pragprog/status/1779253657097117890 (https://twitter.com/pragprog/status/1779253657097117890?utm_source=thinkingelixir&utm_medium=shownotes) - https://twitter.com/sm_debenedetto/status/1779558393373409481 (https://twitter.com/sm_debenedetto/status/1779558393373409481?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.hashicorp.com/ (https://www.hashicorp.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.erlang-solutions.com/ (https://www.erlang-solutions.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://opentofu.org/ (https://opentofu.org/?utm_source=thinkingelixir&utm_medium=shownotes) - https://xkcd.com/927/ (https://xkcd.com/927/?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/Blue%E2%80%93green_deployment (https://en.wikipedia.org/wiki/Blue%E2%80%93green_deployment?utm_source=thinkingelixir&utm_medium=shownotes) - https://docs.docker.com/engine/swarm/ (https://docs.docker.com/engine/swarm/?utm_source=thinkingelixir&utm_medium=shownotes) Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Dave Lucia - @davydog187 (https://twitter.com/davydog187)

Adam welcomes Steve Pereira and Andrew Davis to discuss their new book, Flow Engineering. They discuss the book's origin story and the use of cybernetics to drive effective action.Want more?

Welcome back to another episode of Building Better Developers. Today, we're tackling an issue that every developer faces at some point: panic during software delivery. Whether it's a critical bug or a new feature that isn't functioning as expected, panic can strike anytime your software fails in the hands of a user. Rob and Michael cover handling software delivery panic with practical tips and real-life examples. Listen to the Podcast on Handling Software Delivery Panic The Inevitable Bug: Why Panic Happens Delivering software is a delicate process. Even when you've thoroughly tested your code and believe it to be bulletproof, something can always go wrong. Often, the panic ensues because: Unexpected User Behavior: Users may interact with the software in ways you didn't anticipate. This is particularly common in beta tests or early releases where feedback is crucial. Overlooked Bugs: Some users have a knack for breaking things. These users often find bugs that slipped through your QA processes. Critical Stakeholders: When a manager, CEO, or client encounters a problem, the stakes feel much higher. Their frustration can quickly escalate to panic. Real-Life Panic: A Case Study on Handling Software Delivery Panic Recently, Rob faced this scenario with a technically knowledgeable customer. Despite understanding the development process, the customer encountered a show-stopping bug in an alpha version. Their immediate reaction was that the project was nowhere near completion, creating a sense of panic. During our call, he expressed concerns that none of the features seemed to work. He acknowledged that bugs and design flaws were expected at this stage, but the issue was so severe that it led to a dramatic loss of confidence in the project. Handling Software Delivery Panic Step 1: Stay Calm and Analyze The first and most crucial step when faced with panic is to stay calm. Take a deep breath and focus on understanding the situation: Reproduce the Issue: Identify the user's steps to encounter the bug. Sometimes, it's as simple as a permission issue or an unanticipated input. Prioritize Fixes: Address the most critical issues first, especially those that block user progress. Step 2: Effective Communication Reassure the stakeholders that you're on top of the situation: Acknowledge the Problem: Validate their concerns and show you understand the impact. Outline the Next Steps: Explain how you plan to fix the issue and provide a realistic timeline. Step 3: Learn and Improve Use this experience to strengthen your development and testing processes: Enhance Testing: Incorporate the steps that led to the bug into your testing scenarios. Automated tests can help catch these issues earlier. Add Logging: Improve logging to gather more information if a similar problem arises in the future. Real-Life Tips from Experience Michael shares an insightful story about a shared work experience. Despite rigorous testing, their boss would find bugs within minutes of a release. This constant scrutiny drove home the importance of thorough testing and the psychological pressure of delivering seemingly flawless code. One key takeaway from Michael's story is the value of Test-Driven Development (TDD). By writing tests before the actual code, you ensure that each function meets the specified requirements. This approach not only catches potential issues early but also clarifies the expected behavior for each part of your application. Practical Advice for Developers Before starting on a new feature or bug fix, consider the following: Clarify Requirements: Ensure you have detailed requirements, including user input constraints and expected outputs. Define Acceptance Criteria: Clearly outline what constitutes a successful implementation. Implement Robust Logging: Log critical operations to simplify debugging and provide insights into any issues that arise. Using Static Code Analysis Tools To Handling Software Delivery Panic SonarQube SonarQube Is a code quality assurance tool that performs in-depth code analysis and generates an analysis report to ensure code reliability. Language Support: Java, JavaScript, C#, PHP, Python, C++, and more. Features: Provides comprehensive code quality and security analysis, integrates with CI/CD pipelines, and offers detailed reports. Strengths: Strong community support, extensive plugin ecosystem, and good integration with various development tools. ESLint ESLint statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your continuous integration pipeline. Language Support: JavaScript, TypeScript. Features: Identifies and reports on patterns in JavaScript, customizable rules, and integration with most text editors and build systems. Strengths: Highly customizable, large number of plugins, and widely used in the JavaScript community. PMD PMD is an extensible multilanguage static code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, etc. Language Support: Java, JavaScript, Salesforce Apex, PLSQL, XML, XSL. Features: Detects common coding issues like bugs, unused variables, and performance bottlenecks. Strengths: Simple rule configuration, supports multiple languages, and can be integrated into build tools like Maven and Gradle. PyLint Pylint is a static code analyser for Python 2 or 3. The latest version supports Python 3.8.0 and above. Pylint analyses your code without actually running it. It checks for errors, enforces a coding standard, looks for code smells, and can make suggestions about how the code could be refactored. Language Support: Python. Features: Checks for coding standards, errors, and code smells, provides suggestions for code improvements. Strengths: Highly configurable, integrates well with IDEs and CI/CD pipelines, and widely used in the Python community. Final Thoughts on Handling Software Delivery Panic Panic during software delivery is unavoidable, but it's manageable. By staying calm, communicating effectively, and learning from each incident, you can turn these challenging moments into opportunities for improvement. Remember, every bug is a lesson in disguise, pushing you toward becoming a better developer. That's it for today's episode. We hope these insights help you handle panic more effectively and continue building better software. Until next time, keep calm and code on! Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Code Refactoring: Maintaining Clean, Efficient Code Deciphering Code Chaos: Strategies for Writing Maintainable Code Test-Driven Development – A Better Object Oriented Design Approach Behind the Scenes Podcast Video

Adam presents the mental model behind T1 and T2 signals, a necessary lexicon for understanding production operations.Want more?

Adam answers a listener's request of advice on succeeding in high-level company or project environments with seven tips.Want more?

This week, Bonnie is joined by Bryon Kroger, founder and CEO of Rise8, about the pivotal role of software in government and military operations. Bryon shares his insights on the challenges of bridging the gap between acquisitions and operations, the importance of continuous software delivery, and the ethos of fostering a culture of outcomes over outputs. Drawing on the lessons learned from the creation of Kessel Run and his subsequent venture, Rise8, Bryon outlines a new paradigm for agile, user-focused software development and systems integration in the federal space. TIMESTAMPS: (1:37) Bryon's first experience with deadly software (3:59) How Kessel Run changes the game in software delivery (6:07) The secret to continuous software delivery (14:46) Why Bryon founded Rise8 (19:53) Reimagining requirements & user engagement (22:34) How output and behavior impact mission (33:49) Challenge bureaucracy, innovate, and don't feel powerless LINKS: Follow Bryon: https://www.linkedin.com/in/bryon-kroger/ Follow Bonnie: https://www.linkedin.com/in/bonnie-evangelista-520747231/ CDAO: https://www.ai.mil/ Tradewinds AI: https://www.tradewindai.com/ Rise8: https://www.rise8.us/

Adam presents TDD as skill zero, the one that unlocks all the others.Want more?

On this week's episode, host Conor Bronsdon is joined by Jason Krohn, Global Head of Delivery at Syngenta. Jason delves into how his teams at Syngenta leverage software engineering intelligence to achieve predictable delivery at scale. Jason also explores how aligning work with employees' passions contributes to success and retention at Syngenta. He discusses the challenges and solutions in implementing efficient DevOps processes and ensuring organizational buy-in for the vision. Additionally, Jason highlights the importance of empowering teams with autonomy and providing the necessary tools for proactive decision-making.Whether you're leading a small team or managing an enterprise, Jason's insights offer valuable lessons on driving efficiency, scaling effectively, and fostering a culture of continuous improvement.Episode Highlights: 1:46 Scaling teams that are empowered and autonomous 4:01: The four pillars for retaining talent in tech teams.12:51 Tackling organizational change 18:41 Using metrics to achieve predictable delivery 21:45 Why your engineering teams' need to care about metrics, not just be compliant 26:20 Addressing production delays and DevOps integration28:55 Leadership's role in communicating the 'why'33:05 The Importance of Coaching When Mentoring Show Notes:SyngentaJason KrohnSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

ONUS: Rethinking Agile Roles and Structures, With Craig Smith and Michael Huynh   In this episode, we kick things off by revisiting a captivating talk delivered by Michael and Craig at the Agile Online Summit 2023. The duo urged us to reevaluate the roles of the Scrum Master and Product Owner, and even hinted at potential shifts within Agile organizations. This discussion sparked a larger contemplation in my mind, extending beyond the core arguments presented by Michael and Craig. I took to Twitter to ponder the possibility of Agile serving as a foundational change in how we perceive organizational structures and leadership, leading to a potential revolution. What might this mean for you and your organization? Rethinking Agile Roles Before delving into what the future might hold for Agile practitioners, we asked Craig and Michael to provide a concise summary of their main points from the talk. They urged us to go beyond following “agile dogma” Questioning the purpose of Scrum Master and Product Owner roles Refocus on value generation in Agile practices The need for systemic thinking In this episode, we also explore how it's not just Agile roles, but leaders at various levels, that have strayed from the essence of what Agile truly stands for. CTOs and Chief Product Owners find themselves ensnared in a rigid adherence to processes as well, even when those processes go against their stated intent of adopting Agile. Are Agile Roles Overhead? Craig and Michael raise critical questions about Agile roles, challenging their perceived value and longevity within organizations. Is there a risk of losing sight of the original intent behind roles like Scrum Master and Product Owner? Are these positions temporary or do they inadvertently add another layer of complexity? The conversation als touches on the heart of Agile transformation: business agility. How can organizations efficiently deliver value to the market? There's concern that leaders have become disconnected from the actual work done by their teams. The very essence of leadership may be at risk of being diluted or misunderstood. Leadership in Software Organizations: A Glimpse into the Future In this segment, we discuss the Culture, Structure and Process aspects that we need to take into account to keep our organizations truly Agile, no matter what roles we end up having.  Culture: Shaping Behaviors for Success The importance of culture in shaping organizational behavior cannot be overstated. Leaders must adapt to the unique cultures of their organizations, whether they're fast-moving and less structured or operate within a different paradigm. Structure: Redefining Hierarchies In a rapidly evolving technological landscape, do we need traditional hierarchies? Leaders must understand the core of their businesses and ensure they are moving in the right direction, but do they require the conventional structures that have become commonplace? Process: The Evolution Beyond Projects The notion of projects may be antiquated for software businesses. Start-stop methodologies may no longer align with the dynamic nature of the industry. The changes needed pose a significant challenge to the Agile community. Join the Scrum Master Community For those eager to continue the conversation, we invite you to connect with the vibrant Scrum Master community, get your membership here. About Craig Smith and Michael Huynh Craig Smith is a Business Agility Product Lead at SoftEd, and a veteran Agile Practitioner, Coach, and Trainer with 20+ years of experience. He co-hosts "The Agile Revolution" podcast, and is a driving force in the Agile community. Craig excels in Agile training, coaching, and fostering technical excellence, advocating for quality-driven change. You can link with Craig Smith on LinkedIn.    Michael Huynh is a seasoned agile coach and trainer, recognized for guiding organizations in successful agile adoption. With SoftEd, he collaborates with leaders and teams to foster efficient delivery and swift decision-making. Michael's extensive expertise spans Lean, SDLC, XP, SAFe, Scrum, Kanban, and more, enabling him to tailor approaches for each organization's success. As a dedicated contributor to the agile community, he leads and speaks at international conferences. You can link with Michael Huynh on LinkedIn.

AI-assisted software delivery refers to the utilization of artificial intelligence to assist, enhance, or automate various phases of the software development lifecycle. AI can be used in numerous aspects of software development, from requirements gathering to code generation to testing and monitoring. The overarching aim is to streamline software delivery, reduce errors and, ideally, reduce The post AI for Software Delivery with Birgitta Böckeler appeared first on Software Engineering Daily.