Podcasts about Software development

Kishen, Ivo en Saber bespreken hoe AI software development op z'n kop zet. Van de ontslagen bij Tailwind tot de uitdagingen voor Stack Overflow: businessmodellen staan onder druk. Maar AI is ook een enorme versneller, wat vroeger dagen kostte, doe je nu in een uur. Ze duiken in vibe coding vs. agentic engineering, spec-driven development, Claude Code en de vraag of developers straks nog zelf code schrijven. Plus: tips en een sci-fi aanrader.

In dieser Deep-Dive-Folge spricht Markus mit zwei der spannendsten Köpfe aus der europäischen AI- und Developer-Szene: Mario Zechner und Armin Ronacher. Beide sind zentrale Figuren im entstehenden Agentic-AI-Ökosystem rund um OpenClaw und Pi – und kommen aus Österreich.Wir reden darüber, wie Pi als minimaler Agent-Harness funktioniert und warum es zur Grundlage für OpenClaw wurde, wie „Normies" plötzlich programmieren können, was das für die Identität von Entwicklern bedeutet – und ob händisches Programmieren damit „tot" ist.Außerdem geht's um:die persönlichen Storys von Mario (Games, Machine Learning, Exit zu Microsoft) und Armin (Ubuntu-Community, Jinja, Flask, Sentry)die turbulenten Wochen nach Peters OpenClaw-Erfolg und seinem Wechsel zu OpenAIEuropas strukturelle Probleme: Kammern, Gewerbeordnung, Bürokratie – und warum es trotzdem Sinn macht, hier zu bauendie Polarisierung rund um Peters Armin-Wolf-Interview, Arbeitszeit & Arbeitnehmerrechtedie Frage, wie junge Entwickler*innen noch Software-Engineering lernen, wenn AI den Code schreibtAm Ende gibt's wie immer unsere Speed Round mit Learnings, Lifehacks, Buchempfehlungen und Moonshots.Production: Hanna Moser Musik (Intro/Outro): www.sebastianegger.com

Visit https://cupogo.dev/ for all the links.Using go fix to modernize Go codeEric S. Raymond's tweet about auto-converting his C code to GoEric's HomepageSkill-validatorLinkedIn, GitHub, AgentSkillReport.comcmd/vet: check for missing Err calls for bufio.Scanner and sql.Rows #17747Meetups Shay will be at:GoSF Go Israel April MeetupLightning Round:lazygitKoyeb is Joining Mistral AIPaged Out! #8 is out! ★ Support this podcast on Patreon ★

Today our hosts discuss experiments in gear: those times where you buy something, experience or learn something new with it, then realize it is no longer for you. They revisit one of Dan's objects of the past, take a lot of calls, and analyze a lot of common thoughts around what drives a gear purchase and, eventually, a gear sale. Buy some Old Blood: https://oldbloodnoise.com/ Join the conversation in Discord: https://discord.com/invite/PhpA5MbN5u Follow us all on the socials: @danfromdsf, @andyothling, @oldbloodnoise Subscribe to OBNE on Twitch: https://www.twitch.tv/oldbloodnoise Subscribe to Andy's Twitch channel: https://www.twitch.tv/powereconomy Leave us a voicemail at 505-633-4647!

Keith Shields is co-founder and CEO of Designli, a custom software development company that's helped non-technical founders build over 200 digital products in 13 years. After struggling to build apps through unreliable agencies in his own early startup, Keith focused on fixing the many painful experiences most founders have when hiring software development teams. Designli operates as a complete outsourced engineering department for practical software founders building SaaS and AI products, mobile apps, and web applications. Their SolutionLab program means founders invest $13,800 in a 2-week design sprint of prototyping and product planning before committing to full development, reducing the risk of expensive failures that plague most custom dev projects. The company focuses primarily on vertical SaaS founders who understand their industry problems intimately but lack technical expertise. Keith recommends velocity to first revenue over perfect features, outside audits for struggling teams, and getting gut checks on your development situation, which is far less risky than making huge changes blindly when you feel stuck. Key Takeaways Black Box Risk: Most agencies operate in the dark, leaving founders guessing what's being built, why it's late, and whether progress matches expectations. Dedicated Teams Win: Full-time focused developers outperform fractional freelancers because context, ownership, and velocity compound over long projects. Get Clarity Fast: Structured upfront design sprints align founders and teams on scope, timelines, and priorities before heavy coding begins. Audit Early: A quick external code and process audit can reveal hidden problems before they turn into year-long setbacks. Trust Your Gut: If a development relationship feels wrong, get an outside perspective and fix it before making risky, large changes. Quote from Keith Shields, CEO and Co-Founder of Designli "My advice for non-technical founders that already have a product is to trust your gut when you ask, Are we getting the value out of our development team in this situation? "If you already have a product and your dev team isn't working, get an outside perspective. It's not that hard to go and get what you're doing audited by people, sometimes for free, like us, or you pay for it. You send off a copy of your code in a zip file. It doesn't even have to be the living, breathing version and say, Can you audit this and give me a gut check? "Getting an outside review of your code doesn't happen that often, surprisingly. People feel stuck in their frustrating situation until they make a huge change, and then it's a risky, huge change. So get some outside perspective early and often." Links Keith Shields on LinkedIn Designli on LinkedIn Designli website Podcast Sponsor – Designli This podcast is sponsored by Designli, a digital product studio that helps entrepreneurs and startups turn their software ideas into reality. From strategy and design to full-scale development, Designli guides you through every step of building custom web and mobile apps. Learn more at designli.co/practical. The Practical Founders Podcast Tune into the Practical Founders Podcast for weekly in-depth interviews with founders who have built valuable software companies without big funding. Subscribe to the Practical Founders Podcast using your favorite podcast app or view on our YouTube channel. Get the weekly Practical Founders newsletter and podcast updates at practicalfounders.com. Practical Founders CEO Peer Groups Be part of a committed and confidential group of practical founders creating valuable software companies without big VC funding.  A Practical Founders Peer Group is a committed and confidential group of founders/CEOs who want to help you succeed on your terms. Each Practical Founders Peer Group is personally curated and moderated by Greg Head.

In this conversation, Sabine Kvenberg and Sheila Slick explore the journey of becoming an author without traditional writing, the importance of visibility in business, and how technology, particularly AI, can assist in transforming spoken content into published works. Sheila shares her experiences as a serial entrepreneur and software developer, emphasizing the value of gamifying education and the unique propositions that entrepreneurs can offer. The discussion also highlights the role of podcasts in amplifying messages and the significance of networking through speaking engagements. I am Interest in speaking or attending event: https://forms.gle/gj3oV1KgG1G5Qn9h9 Chapters 00:00Becoming an Author Without Writing 08:58The Journey of Software Development and Education 18:03Visibility and Standing Out in Business 27:39Transforming Spoken Words into Published Works   Get in touch with Sheila: https://fivemilestones.com/   Connect with Sabine: Youtube: https://www.youtube.com/SabineKvenberg  IG: https://www.instagram.com/sabinekvenberg/ LinkedIn: https://www.linkedin.com/in/sabine-kvenberg/ Facebook: https://www.facebook.com/sabine.kvenberg.2025/      

How can I be more productive as a software developer? Sometimes, things seem to drag on forever. Projects take too long, practicing what I learn takes too much time, and my progress as a developer seems to stay in place. How do I continue to see gains in my career as a software developer? These are the questions we will answer in today's episode of Dev Questions.Website: https://www.iamtimcorey.com/ Ask Your Question: https://suggestions.iamtimcorey.com/ Sign Up to Get More Great Developer Content in Your Inbox: https://signup.iamtimcorey.com/

In episode 560 of 'Coffee with Butterscotch,' the brothers check in on demo performance, wishlist growth, and what live events are actually doing for visibility. By comparing what has actually generated traction with what just sounds exciting, they unpack what real leverage looks like for an indie studio and contrast it with the current AI hype cycle, where convenience, cost, and risk do not always align.Support How Many Dudes!Official Website: https://www.bscotch.net/games/how-many-dudesTrailer Teaser: https://www.youtube.com/watch?v=IgQM1SceEpISteam Wishlist: https://store.steampowered.com/app/3934270/How_Many_Dudes00:00 Cold Open00:31 Introduction and Welcome02:14 Demo Performance and Wishlist Growth05:47 Event Participation and Marketing Strategies08:43 Game Development Updates and New Characters14:40 Discussion on Mewgenics and Industry Insights17:24 Game Popularity and Player Retention19:58 The Impact of AI on the Gaming Industry31:10 AI's Role in Software Development and Personalization43:52 Challenges in Open Source Maintenance46:15 The Impact of AI on Bug Bounty Programs49:24 Autonomous Agents and Their Consequences52:19 The Reverse Centaur Concept56:10 The Dangers of Autonomous AI AgentsTo stay up to date with all of our buttery goodness subscribe to the podcast on Apple podcasts (apple.co/1LxNEnk) or wherever you get your audio goodness. If you want to get more involved in the Butterscotch community, hop into our DISCORD server at discord.gg/bscotch and say hello! Submit questions at https://www.bscotch.net/podcast, disclose all of your secrets to podcast@bscotch.net, and send letters, gifts, and tasty treats to https://bit.ly/bscotchmailbox. Finally, if you'd like to support the show and buy some coffee FOR Butterscotch, head over to https://moneygrab.bscotch.net. ★ Support this podcast ★

I'm joined by Nirmal Mehta of AWS and Viktor Farcic from Upbound, to go through our 2025 year in review. We look into the AI tools that consumed us this year, from CLI agents to terminal emulators, IDEs, AI browsers - what worked, what flopped, what's worth your time and money, and what we think isn't!Check out the video podcast version here: https://youtu.be/mnagfUsh5bc

As we move into Q1 2026, Brian talks about 3 rooms where he'd like to be a fly on wall to see the blueprints of significant AI companies shaping the markets. SHOW: 1002SHOW TRANSCRIPT: The Cloudcast #1002 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET NEW TO CLOUD? CHECK OUT OUR OTHER PODCAST - "CLOUDCAST BASICS" A FLY ON THE WALL IN 3 ROOMS IN 2026Room1 - NVIDIA's M&A Room (Chips, Software Stack, Hosting Services, Agentic Tools, etc.)Room 2 - Anthropic's Agentic VisionRoom 3 - TSMC's 2028-2030 PlanningFEEDBACK?Email: show at the cloudcast dot netBluesky: @cloudcastpod.bsky.socialTwitter/X: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

MeetupsHello Stuttgart, 19 FebGo 1.26 is out!Go 1.26 release party with Anton ZhiyanovGo 1.26.0-1 available from MicrosoftLighting RoundBlog: Stepping out of Front-End with Go by ElGophertransition ppc64/linux (big-endian) from ELFv1 to ELFv2 in Go 1.27Discussion: Should Go accept CLs generated by AI? ★ Support this podcast on Patreon ★

Today our hosts are joined by Scott Harper, aka Knobs. Scott is a quiet figure who's had great influence in the world of effects pedal demos, bringing depth, fun, and true knowledge of the product to his presentations. He's also been creatively involved in bringing to light some modern classics from Chase Bliss, like MOOD and Blooper. Today we talk about the weirdo delay microlooper that marks a turning point in his journey, as well as many of ours: the Montreal Assembly Count to 5. There's also one and a half minutes of fountain pen conversation, and etc.Buy some Chase Bliss: https://www.chasebliss.com/Buy some Old Blood: https://oldbloodnoise.com/Join the conversation in Discord: https://discord.com/invite/PhpA5MbN5uFollow us all on the socials: @knobs.creative, @danfromdsf, @andyothling, @oldbloodnoiseSubscribe to OBNE on Twitch: https://www.twitch.tv/oldbloodnoiseSubscribe to Andy's Twitch channel: https://www.twitch.tv/powereconomyLeave us a voicemail at 505-633-4647!

Sherwin Wu leads engineering for OpenAI's API platform, where roughly 95% of engineers use Codex, often working with fleets of 10 to 20 parallel AI agents.We discuss:1. What OpenAI did to cut code review times from 10-15 minutes to 2-3 minutes2. How AI is changing the role of managers3. Why the productivity gap between AI power users and everyone else is widening4. Why “models will eat your scaffolding for breakfast”5. Why the next 12 to 24 months are a rare window where engineers can leap ahead before the role fully transforms—Brought to you by:DX—The developer intelligence platform designed by leading researchersSentry—Code breaks, fix it fasterDatadog—Now home to Eppo, the leading experimentation and feature flagging platform—Episode transcript: https://www.lennysnewsletter.com/p/engineers-are-becoming-sorcerers—Archive of all Lenny's Podcast transcripts: https://www.dropbox.com/scl/fo/yxi4s2w998p1gvtpu4193/AMdNPR8AOw0lMklwtnC0TrQ?rlkey=j06x0nipoti519e0xgm23zsn9&st=ahz0fj11&dl=0—Where to find Sherwin Wu:• X: https://x.com/sherwinwu• LinkedIn: https://www.linkedin.com/in/sherwinwu1—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Sherwin Wu(03:10) AI's role in coding at OpenAI(06:53) The future of software engineering with AI(12:26) The stress of managing agents(15:07) Codex and code review automation(19:29) The changing role of engineering managers(24:14) The one-person billion-dollar startup(31:40) Management lessons(37:28) Challenges and best practices in AI deployment(43:56) Hot takes on AI and customer feedback(48:57) Building for future AI capabilities(50:16) Where models are headed in the next 18 months(53:35) Business process automation(57:22) OpenAI's ecosystem and platform strategy(01:00:50) OpenAI's mission and global impact(01:05:21) Building on OpenAI's API and tools(01:08:16) Lightning round and final thoughts—Referenced:• Codex: https://openai.com/codex• OpenAI's CPO on how AI changes must-have skills, moats, coding, startup playbooks, more | Kevin Weil (CPO at OpenAI, ex-Instagram, Twitter): https://www.lennysnewsletter.com/p/kevin-weil-open-ai• OpenClaw: https://openclaw.ai• The creator of Clawd: “I ship code I don't read”: https://newsletter.pragmaticengineer.com/p/the-creator-of-clawd-i-ship-code• The Sorcerer's Apprentice: https://en.wikipedia.org/wiki/The_Sorcerer%27s_Apprentice_(Dukas)• Quora: https://www.quora.com• Marc Andreessen: The real AI boom hasn't even started yet: https://www.lennysnewsletter.com/p/marc-andreessen-the-real-ai-boom• Sarah Friar on LinkedIn: https://www.linkedin.com/in/sarah-friar• Sam Altman on X: https://x.com/sama• Nicolas Bustamante's “LLMs Eat Scaffolding for Breakfast” post on X: https://x.com/nicbstme/status/2015795605524901957• The Bitter Lesson: http://www.incompleteideas.net/IncIdeas/BitterLesson.html• Overton window: https://en.wikipedia.org/wiki/Overton_window• Developers can now submit apps to ChatGPT: https://openai.com/index/developers-can-now-submit-apps-to-chatgpt• Responses: https://platform.openai.com/docs/api-reference/responses• Agents SDK: https://platform.openai.com/docs/guides/agents-sdk• AgentKit: https://openai.com/index/introducing-agentkit• Ubiquiti: https://ui.com• Jujutsu Kaisen on Crunchyroll: https://www.crunchyroll.com/series/GRDV0019R/jujutsu-kaisen?srsltid=AfmBOoqvfzKQ6SZOgzyJwNQ43eceaJTQA2nUxTQfjA1Ko4OxlpUoBNRB• eero: https://eero.com• Opendoor: https://www.opendoor.com—Recommended books:• Structure and Interpretation of Computer Programs: https://www.amazon.com/Structure-Interpretation-Computer-Programs-Engineering/dp/0262510871• The Mythical Man-Month: Essays on Software Engineering: https://www.amazon.com/Mythical-Man-Month-Software-Engineering-Anniversary/dp/0201835959• There Is No Antimemetics Division: A Novel: https://www.amazon.com/There-No-Antimemetics-Division-Novel/dp/0593983750• Breakneck: China's Quest to Engineer the Future: https://www.amazon.com/Breakneck-Chinas-Quest-Engineer-Future/dp/1324106034• Apple in China: The Capture of the World's Greatest Company: https://www.amazon.com/Apple-China-Capture-Greatest-Company/dp/1668053373—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. To hear more, visit www.lennysnewsletter.com

If someone walked into your office today and asked you to build a framework for how to value software development, what would you think about it? SHOW: 1000SHOW TRANSCRIPT: The Cloudcast #1000 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET NEW TO CLOUD? CHECK OUT OUR OTHER PODCAST - "CLOUDCAST BASICS" SHOW NOTES:Chainguard introduces Factory 2.0On running a startup of Claude Code agentsAgentic Product Development and the Theory of ConstraintsSoftware AbundanceHOW SHOULD SOMEONE THINK ABOUT THE ECONOMICS OF SW DEV IN 2026?If someone walked into your office today and asked you to build a framework for how to value software development, how would you think about it? FEEDBACK?Email: show at the cloudcast dot netBluesky: @cloudcastpod.bsky.socialTwitter/X: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

Go 1.25.7 and 1.24.13 releasedUUIDs in the standard library?crypto/uuid: add API to generate and parse UUIDscrypto/rand: add UUIDv4 and UUIDv7 generatorsThe most popular Go dependency is...Lightning roundRust vs Go in 2026 by John ArundelWelcome to Gas Town by Steve YeggeInterview with Jakub CiolekOn GitHubHackerOne 'ghosted' me for months over $8,500 bug bounty, says researcher ★ Support this podcast on Patreon ★

What should network engineers know about software development? What should software developers know about networking? Ethan and Drew sit down with Chris Rapier and Nick Buraglio to discuss why crossing these silos can improve outcomes for everyone. They break down why being a little curious about the infrastructure can help software developers write better code,... Read more »

What should network engineers know about software development? What should software developers know about networking? Ethan and Drew sit down with Chris Rapier and Nick Buraglio to discuss why crossing these silos can improve outcomes for everyone. They break down why being a little curious about the infrastructure can help software developers write better code,... Read more »

What should network engineers know about software development? What should software developers know about networking? Ethan and Drew sit down with Chris Rapier and Nick Buraglio to discuss why crossing these silos can improve outcomes for everyone. They break down why being a little curious about the infrastructure can help software developers write better code,... Read more »

Today, our hosts welcome Emily Hopkins and Russ back to the show to discuss the newest Old Blood Noise Endeavors pedal, Parting! They were the creative force behind it, and have a lot of tales to tell about working with Dan to create, hone, and fully realize the vision of this glitchy and wondrous object. There's a lot of behind the scenes product development talk, and then some voicemails for good measure.Buy yourself a Parting: http://www.oldbloodnoise.com/partingJoin the conversation in Discord: https://discord.com/invite/PhpA5MbN5uFollow us all on the socials: @emilyharpist, @danfromdsf, @andyothling, @oldbloodnoise,See the video at Dan's studio: https://youtu.be/WRcm2b877ekSubscribe to OBNE on Twitch: https://www.twitch.tv/oldbloodnoiseSubscribe to Andy's Twitch channel: https://www.twitch.tv/powereconomyLeave us a voicemail at 505-633-4647!

Mazen and Robin sit down with Kræn Hansen from ElevenLabs to break down what Node API actually is and why it could be a game-changer for React Native library authors who want to write native modules once and use them everywhere, plus what still needs to happen before it's ready for prime time. Show NotesAnnouncing Node-API Support for React Native (Callstack)Kræn Hansen's React Universe TalkKræn Hansen on Callstack's livestreamHost package: React-native-node-apiHermes implementation discussionConnect With Us!Kræn Hansen: @KrænHansenRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With over a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

$300 billion wiped from software stocks in a single week. Is SaaS officially dead or is this the buying opportunity of a decade?In this episode of Bricks, Bucks & Bytes, Owen, Patric, Dustin, and Martin break down the so-called "SaaSpocalypse" rocking global markets, welcome back Bedrock CTO Kevin Peterson fresh off a massive $270M Series B that puts his autonomous excavator company into unicorn territory, and dissect the hilarious beef between Anthropic and OpenAI playing out on the Super Bowl stage.Topics discussed:The $300B+ SaaS valuation crash and whether it's a death sentence or a market correction back to normalWhy software engineers are now "juicing" with AI coding tools and what that means for the industryBedrock's journey from Series A to unicorn status, their autonomous excavators on real job sites, and why Google's Capital G is backing themWhere smart money is moving as investors flee software stocks (hint: Europe is winning)Anthropic's brilliant Super Bowl ad mocking OpenAI's plan to put ads in ChatGPT and Sam Altman's salty response38% of Stanford students claiming disability for perks and what it says about elite institutions

Why is it that production code is always so messy? Why don't developers follow best practices or design patterns? Why are there so many workarounds in programming? These are the questions we will answer in today's episode of Dev Questions.Website: https://www.iamtimcorey.com/ Ask Your Question: https://suggestions.iamtimcorey.com/ Sign Up to Get More Great Developer Content in Your Inbox: https://signup.iamtimcorey.com/

In a Tech Barometer podcast segment, part of a series of interviews with AI company CEOs, founders and leaders, Pendo...

Sean O'Dell of Dynatrace argues that enterprises are unprepared for a major shift brought on by AI: the rise of the developer. Speaking at Dynatrace Perform in Las Vegas, O'Dell explains that AI-assisted and “vibe” coding are collapsing traditional boundaries in software development. Developers, once insulated from production by layers of operations and governance, are now regaining end-to-end ownership of the entire software lifecycle — from development and testing to deployment and security. This shift challenges long-standing enterprise structures built around separation of duties and risk mitigation. At the same time, the definition of “developer” is expanding. With AI lowering technical barriers, software creation is becoming more about creative intent than mastery of specialized tools, opening the door to nontraditional developers. Experimentation is also moving into production environments, a change that would have seemed reckless just 18 months ago. According to O'Dell, enterprises now understand AI well enough to experiment confidently, but many are not ready for the cultural, operational, and security implications of developers — broadly defined — taking full control again.Learn more from The New Stack about the latest around enterprise developers and AI: Retool's New AI-Powered App Builder Lets Non-Developers Build Enterprise AppsSolving 3 Enterprise AI Problems Developers FaceEnterprise Platform Teams Are Stuck in Day 2 HellJoin 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.

Are we ready to move into an era of wild predictions about where the future of Enterprise software is headed in 2026 and beyond? SHOW: 999SHOW TRANSCRIPT: The Cloudcast #999 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET CLOUD NEWS OF THE WEEK: http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST: "CLOUDCAST BASICS"SHOW NOTESThe SPAC-king is going to fix legacy software All Enterprise software is dead Microsoft and Software Survival (Stratechery)WHAT HAPPENS TO ENTERPRISE SOFTWARE NEXT?How much do enterprises want to write their own software? How much do enterprises wish they could write more software?How much do enterprises not understand the economics of owning their own software?How much does “big SaaS” or just “big Enterprise software” actually help because people already know it?Is it possible that this new Agentic-driven software could create a type of new software community? Are “open” software communities prepared for the emerging economics of AI-created software? FEEDBACK?Email: show at the cloudcast dot netTwitter/X: @cloudcastpodBlueSky: @cloudcastpod.bsky.socialInstagram: @cloudcastpodTikTok: @cloudcastpod

AI agents failed spectacularly at teamwork, performing ~50% worse than one solo agent!This week, we're discussing Stanford's CooperBench study (a benchmark, testing whether AI agents can collaborate on real coding tasks across Python, TypeScript, Go, and Rust) and why AI-developer coordination collapses, even with a constant chat.Listen or watch as Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel dig into the methods and findings of Stanford's 2026 CooperBench experiment and learn about the three capability gaps that caused these failures: • Expectation Failures (42%): Agents ignored shared plans or misunderstood scope• Commitment Failures (32%): Promised work was never completed• Communication Failures (26%): Silence, spam, or hallucinationsThe experiment's findings seem to confirm human-refined agile practices. The episode ends with a concrete call to action: stop treating AI as teammates. Use them as solo contributors. And if you must coordinate? Build working agreements, not handoffs.This episode is for anyone navigating the AI hype cycle and wondering if swarms of agents are going to coordinate everyone out of a job!#Agile #AI #ProductManagementSOURCECooperBench: Benchmarking AI Agents' Cooperation (Stanford University & SAP Labs US)https://cooperbench.com/https://cooperbench.com/static/pdfs/main.pdfLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Mazen and Robin welcome back Cedric van Putten to discuss Expo Launch, a new tool that automates deploying React Native apps to the App Store. Learn how Expo is streamlining certificates, screenshots, and submission workflows.Show NotesExpo LaunchCedric van Putten's blog post: Introducing Expo LaunchMatt Palmer's blog post: From idea to app with Replit and ExpoExpo's AI StrategyConnect With Us!Cedric van Putten: @cedric_devRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @ReactNativeRdioThis episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With over a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

Sponsored by Quantcast!This episode was recorded live at San Francisco as part of GoSF.ProposalsAccepted: direct reference to embedded fields in struct literalsNew: Generic Methods for Go ★ Support this podcast on Patreon ★

In this conversation, Alex Morris, Chief Tribe Officer at Tribecode, discusses the transformative impact of AI on software engineering, emphasizing the shift towards autonomous code generation and the evolving roles of engineers and product managers. He highlights the importance of adapting to new tools, the necessity of upskilling, and the changing dynamics of client interactions. The discussion also touches on job security for engineers in an AI-driven world and the potential for increased productivity and efficiency in software development processes. In this conversation, the speakers delve into various themes surrounding the future of work, the evolution of software development skills, the impact of AI on job markets, and the role of education in the modern workforce. They discuss the changing landscape of tech innovation globally, the implications of outsourcing, and the skepticism surrounding AI and data centers. The conversation also touches on market trends, economic concerns, and personal insights into the future aspirations of the speakers.

Christopher shares a career spent in restaurants, not just behind a desk. He emphasizes the importance of focusing on KPIs before investing in technology, and standardizing operations while preserving your brands' identity.Welcome to Elevating Brick and Mortar. A podcast about how operations and facilities drive brand performance.On today's episode, we talk with Christopher Gumprecht, VP of Marketing and Information Technology at Craveworthy Brands. Craveworthy Brands was founded in 2022 to invigorate legacy restaurant brands while nurturing and growing emerging brands. GUEST BIOChristopher is a tech savvy restaurant leader with over 20 years of experience in food and beverage. He's had roles in Restaurant Operations, Learning and Development, Marketing, IT, Software Development, and Sales. He spends his time giving back to his community by mentoring local students and helping entrepreneurs reach their goals.TIMESTAMPS00:43 - About Craveworthy Brands04:50 - Chris' journey10:02 - Competing for attention13:16 - Gaining loyalty15:52 - The promise of off-premise catering23:23 - The challenge of tech in restaurants36:21 - Today's consumer expectations42:46 - Where to find Chris43:19 - Sid's takeawaysSPONSORServiceChannel brings you peace of mind through peak facilities performance.Rest easy knowing your locations are:Offering the best possible guest experienceLiving up to brand standardsOperating with minimal downtimeServiceChannel partners with more than 500 leading brands globally to provide visibility across operations, the flexibility to grow and adapt to consumer expectations, and accelerated performance from their asset fleet and service providers.LINKSConnect with Chris on LinkedInConnect with Sid Shetty on LinkedinCheck out the ServiceChannel Website Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

What happens when a side hustle photo business turns into a decade-long marketing career that no longer fits? In this episode, Michael Galo shares his non-linear journey to Nashville Software School (NSS). After feeling "stuck" in marketing and communications, Michael decided to follow the advice of local coffee shop regulars and dive into tech. Michael discusses the intensity of the six-month Software Development bootcamp, the "fire hose" of learning, and why he chose to immediately specialize further by joining NSS's brand-new Data Engineering program through the ProTech initiative. 01:33 Life Before NSS: A Decade in Photo Production, Marketing & Communications 02:31 The Spark: Too Many Alumni at the Coffee Shop 02:57 Why Software Development? 04:59 Navigating the Bootcamp Challenge: The Capstones 06:52 The Importance of Community and Teamwork 08:01 Specializing with Data Engineering and ProTech 10:41 Deepening Backend Skills and Data Architecture 12:18 Expanding the Job Search Target 14:24 Career Development: Beyond the Resume 16:18 Advice for the Job Search: Stay Connected 18:00 Is Now the Right Time to Invest in Yourself? 20:10 Final Thoughts: Busting Through the Walls

This show has been flagged as Clean by the host. Development isn't over until it's packaged Most software development I've done has been utilities for highly specific workflows. I've written code to ensure that metadata for a company's custom file format gets copied along with the rest of the data when the file gets archived, code that ensures a search field doesn't mangle input, lots of Git hooks, file converters, parsers, and of course my fair share of dirty hacks. Because most software projects I work on are designed for a specific task, very few of them have required packaging. My utilities have been either integrated into a larger code base I'm not responsible for, or else distributed across an infrastructure by an admin. It's like a magic trick, which has made my life conveniently easier but, as magic does, it has also tricked me into thinking that my development work is done once I can prove that my code does its job. The reality is that code development isn't actually done until you can deliver it to your users in a format they can install. I don't think I'm alone in forgetting that software delivery is the real final product. There are many reasons some developers stop short of providing an installable package for the code they've worked on for weeks or months or years. First of all, packaging is work, and after writing and troubleshooting code for months, sometimes you just want your work to be over just as soon as everything functions as expected. Secondly, there are a lot of software package formats out there, regardless of what platform you're delivering to. However, I view packaging as part of quality assurance. There are lots of benefits you gain by packaging your code into an installer, and you don't have to target every package format. In fact, you get the benefits of packaging by creating just one package. Checking for consistency When you package your code as an installable file, whether it's an RPM file or a Bash script or a Flatpak or AppImage or EXE or MSI or anything else, you are checking your code base for consistency. Pick whatever package format you're most comfortable with, or the one you think represents the bulk of your target audience, and you're sure to find that the package tooling expects to be automated. Nobody wants to start packaging from scratch every time they update code, so naturally packaging tools are designed to be configured once for a specific code base and then to create updated packages each time the code base is updated. If you're building a package for your project and discover that you have to manually intervene, then you've discovered a bug in your code. Imagine that you've got a project repository with a name in camel-case. You hadn't noticed before, but your code refers to itself in a mix of lowercase and camel-case. Your package build grinds to a halt because a variable used by the packaging tools suddenly can't find your code base because it was set to a lowercase title but the archive of your code uses camel-case. If this happens to you, it's also going to happen for every software packager trying to help you deliver your project to their users. Fix it for yourself, and you've fixed it for everyone. Discover surprise dependencies For decades, one of the most common problems of software troubleshooting has been the phrase “well, it works on my machine.” No matter how many tools we developers have at our disposal to make it easy to build and run software on a clean system, it's still common to accidentally deliver software with surprise dependencies. It's easy to forget to revert to a clean snapshot in a virtual machine, or to use a container that just happens to have a more recent version of a library than you'd realised, or to get the path of an important executable wrong in a script, or to forget that not all computers ship with a thing you take for granted. Not all packaging tools are immune to this problem, but very robust ones (like RPM and DEB, Flatpak, and AppImage) are. I can't count the times I've tried to deliver an RPM only to be reminded by rpmbuild that I haven't included the -devel version of a dependency (many Linux distributions separate development libraries from binaries.) You may not literally fix every problem with dependency management by building a single package, but you can clearly identify what your code requires. It only takes a single warning from your packaging tool for you to add a note to other packagers about what they must include in their own builds. As an additional bonus, it's also a good reminder to double check the licenses your project is using. In the haze of desperate hacking to get something to just-work-already, it's helpful to get a gentle reminder that you've linked to a library with a different license than everything else. Few packaging tools (if any?) detect licensing requirements directly, but sometimes all it takes is a reminder that you're using a library that comes from a non-standard repo for you to remember to review licensing. Every package is an example package Once you've packaged your code once, you create an example for everyone coming to your project to turn it into a package of their own. It doesn't matter whether your example package is an RPM or a DEB or just a TGZ for a front-end like SlackBuild or Arch's AUR, it's the interaction between a packaging system and the input script that counts. Even a novice package maintainer is likely to be able to reverse engineer a packaging script enough to reuse the same logic for their own package. Here's the build and install section of the RPM for GNU Hello: %prep %autosetup %build %configure make %{?_smp_mflags} %install %make_install %find_lang %{name} rm -f %{buildroot}/%{_infodir}/dir %post /sbin/install-info %{_infodir}/%{name}.info %{_infodir}/dir || : Here's the GNU Hello build script for Arch Linux: source=(https://ftp.gnu.org/gnu/hello/$pkgname-$pkgver.tar.gz) md5sums=('5cf598783b9541527e17c9b5e525b7eb') build(){ cd "$pkgname-$pkgver" ./configure --prefix=/usr make } package(){ cd "$pkgname-$pkgver" make DESTDIR="$pkgdir/" install } There are differences, but you can see the shared logic. There are macros or functions that abstract some common steps of the build process, there are variables to ensure consistency, and they both benefit from using automake as provided by the source code. Armed with these examples, you could probably write a DEB package or Flatpak ref for GNU Hello in an afternoon. Package your code at least once Packaging is quality assurance. Even though a packaging system is really just a front-end for whatever build system your code uses anyway, the rigour of creating a repeatable and automated process for delivering your project is a helpful exercise. It benefits your project, and it benefits the people eager to deliver your project to other users. Software development isn't over until it's packaged.Shownotes taken from https://www.both.org/?p=13264Provide feedback on this episode.

This week's episode is packed with Expo-heavy updates, early looks at AI agent tooling, and some honest numbers and lessons from Tiny Harvest. We also zoom out and talk about the idea that we might be living through an Industrial Revolution of Software.⚛️ React Native Radar

GopherJS 1.20 releasedListen to interview with Grant Nelson, Episode 53Results from the 2025 Go Developer SurveyInterview with Dominic St-Pierrego podcast()StaticBackendDominic on LinkedIn ★ Support this podcast on Patreon ★

In this episode of React Native Radio, Robin and Mazen are joined by Marc Rousavy to break down transforming packages to Nitro and why it's a big deal for high-performance native modules. They dig into Nitro's origins, how it stacks up against TurboModules and Expo, and what's coming next for VisionCamera. Show NotesNitroModulesChatGPT Nitro Module BuilderMarc's screencast: How to build a Nitro ModuleFrank Calise's Awesome Nitro ModulesRNR 310 - Nitro with Marc RousavyMargelo's Discord Connect With Us!Marc Rousavy: @mrousavyRobin Heinze: @robinheinzeMazen Chami: @mazenchamiReact Native Radio: @ReactNativeRdio This episode is brought to you by Infinite Red!Infinite Red is an expert React Native consultancy located in the USA. With over a decade of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter, core React Native contributors, creators of Ignite and Reactotron, and much, much more), Infinite Red is the best choice for helping you build and deploy your next React Native app.

I talk with David Flanagan, aka Rawkode, about his new opinionated Tech Matrix that helps you navigate the overwhelming CNCF landscape. https://rawkode.academy/technology/matrix

Want to share our last week's episode? Here is the link!Want to send a voice note for our 3 year episode? Here!News[security] Go 1.26 Release Candidate 2 is released[security] Go 1.25.6 and Go 1.24.12 are releasedGophercamp 2026Lightning RoundHow to Get Consistent Classification From Inconsistent LLMs?Yet another Nginx Web UIAd breakWant to send a voice note for our 3 year episode? Here!Go Rumours: Meetup in San Francisco || Hosted by QuantcastSF Go Meetup March '26 ★ Support this podcast on Patreon ★

Today, our hosts discuss the Spin Semiconductor FV-1, the chip at the heart of many digital pedals from the boutique pedal boom. They talk about what makes it special, both in strengths and weaknesses, and how key it was to Dan's arc as a pedal creator. Listen, enjoy, and ask yourself: is this really cool pedal made with an FV-1?Buy yourself some OBNE: http://www.oldbloodnoise.comJoin the conversation in Discord: https://discord.com/invite/PhpA5MbN5uFollow us all on the socials: @danfromdsf, @andyothling, @oldbloodnoiseSubscribe to OBNE on Twitch: https://www.twitch.tv/oldbloodnoiseSubscribe to Andy's Twitch channel: https://www.twitch.tv/powereconomyLeave us a voicemail at 505-633-4647!

The Investing Power Hour is live-streamed every Thursday on the Chit Chat Stocks Podcast YouTube channel at 5:00 PM EST. This week we discussed:(00:00) Introduction(01:15) The Software Apocalypse(21:36) AI and Software Development(30:30) Housing Market Insights(34:17) TripAdvisor: A Legacy Business in Transition(38:43) Viator Acquisition: A Strategic Move for Airbnb(44:38) TSMC's Growth and Market Position(52:34) Apple and Google's AI Partnership*****************************************************Subscribe to Emerging Moats Research: emergingmoats.com *********************************************************************Chit Chat Stocks is presented by Interactive Brokers. Get professional pricing, global access, and premier technology with the best brokerage for investors today: https://www.interactivebrokers.com/ Interactive Brokers is a member of SIPC. *********************************************************************Fiscal.ai is building the future of financial data.With custom charts, AI-generated research reports, and endless analytical tools, you can get up to speed on any stock around the globe. All for a reasonable price. Use our LINK and get 15% off any premium plan: ⁠https://fiscal.ai/chitchat *********************************************************************Disclosure: Chit Chat Stocks hosts and guests are not financial advisors, and nothing they say on this show is formal advice or a recommendation.

In this Q&A episode, Eric Naiburg, COO of Scrum.org, is joined by Darrell Fernandes, Executive Advisor at Scrum.org to explore how AI is showing up in Scrum Teams today—and what it really takes to make it valuable.Drawing from questions raised during a recent webinar: Managing Your AI Teammate: Turning AI from Experiment to Strategic Partner, they discuss practical ways teams are using AI as a research assistant, DevOps helper, and development aid. They emphasize why Scrum's iterative mindset is critical for working with AI, especially given how quickly models, capabilities, and limitations evolve.The conversation tackles common misconceptions about AI replacing people, the importance of validating AI outputs, and why teams should consider writing a “job description” for AI to clearly define expectations, measures of success, and accountability. Eric and Darrell also explore how AI may automate some work while creating entirely new roles and opportunities for professionals.This is Part 1 of an ongoing conversation focused on helping Scrum Teams thoughtfully integrate AI while staying grounded in empiricism, collaboration, and value delivery.Key LearningsWhy there is no single model for integrating AI into Scrum—and why experimentation mattersHow Scrum's inspect-and-adapt mindset applies directly to AI usagePractical examples of AI as a research assistant, DevOps helper, and development toolWhy teams must validate AI outputs to manage bias, accuracy, and complianceHow defining a job description for AI helps measure effectiveness and valuWhy AI is better viewed as a teammate or tool, not a replacement for peopleHow AI may eliminate some tasks while creating new roles and opportunitiesLinksWebinar - Managing Your AI Teammate: Turning AI from Experiment to Strategic PartnerWhitepaper - The AI Teammate Framework: A Four-Step Framework for Product Teams

A CloudBees survey reveals that enterprise migration projects often fail to deliver promised modernization benefits. In 2024, 57% of enterprises spent over $1 million on migrations, with average overruns costing $315,000 per project. In The New Stack Makers podcast, CloudBees CEO Anuj Kapur describes this pattern as “the migration mirage,” where organizations chase modernization through costly migrations that push value further into the future. Findings from the CloudBees 2025 DevOps Migration Index show leaders routinely underestimate the longevity and resilience of existing systems. Kapur notes that applications often outlast CIOs, yet new leadership repeatedly mandates wholesale replacement. The report argues modernization has been mistakenly equated with migration, which diverts resources from customer value to replatforming efforts. Beyond financial strain, migration erodes developer morale by forcing engineers to rework functioning systems instead of building new solutions. CloudBees advocates meeting developers where they are, setting flexible guardrails rather than enforcing rigid platforms. Kapur believes this approach, combined with emerging code assistance tools, could spark a new renaissance in software development by 2026.Learn more from The New Stack about enterprise modernization: Why AI Alone Fails at Large-Scale Code ModernizationHow AI Can Speed up Modernization of Your Legacy IT SystemsJoin 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.

GopherCon 2026 Early tickets until Jan 31! Get them while they last!Go 1.26 coming soonOfficial release notesInteractive release notes by Anton ZhiyanovInterview with Arthur VaverkoVenn.cityJob openingsArthur Vaverko on LinkedIn ★ Support this podcast on Patreon ★

Today, our hosts are joined by Tom Cosm, electronic musician and technical director of Telepathic Instruments. We talk about the beauty of music composed on the highly limited computing devices of yesteryear, and ways those workflows are still inspiring to this day. We get a bit of insight into the musician, producer, and tinkerer that is Tom Cosm, as well as the device he's been developing over the last five years, the Orchid ideas machine.Sign up for the Orchid waitlist: https://telepathicinstruments.com/products/orchid-orc-1Buy yourself some OBNE: http://www.oldbloodnoise.comJoin the conversation in Discord: https://discord.com/invite/PhpA5MbN5uFollow us all on the socials: @tomcosm, @danfromdsf, @andyothling, @oldbloodnoiseSubscribe to OBNE on Twitch: https://www.twitch.tv/oldbloodnoiseSubscribe to Andy's Twitch channel: https://www.twitch.tv/powereconomyLeave us a voicemail at 505-633-4647!

In this live episode of Founded & Funded, Madrona Managing Director Soma Somasegar sits down with Jay Parikh, EVP of Core AI at Microsoft, to unpack the company's evolution from a software factory to an agent factory Jay leads the team responsible for Microsoft's core AI stack, the systems that power Copilot, the tools developers rely on, like GitHub, and the infrastructure that makes large-scale AI possible. In short, his group builds the underlying tech that Microsoft and thousands of companies use to create AI-powered applications and agents. In this conversation, Soma and Jay dive into what Jay calls the Agent Factory, which is a new paradigm reshaping how software gets built in the reasoning era. They explore how AI changes the development lifecycle, why observability and evals are becoming mission-critical for enterprises, what it means to collapse traditional engineering functions, and how organizations should prepare for a world where models, agents, and human builders all collaborate in real time. This is a must-watch for founders, developers, and enterprise leaders who want to understand what's coming — and how to prepare for a world of real-time collaboration between humans, models, and agents. Full Transcript: http://www.madrona.com/microsofts-agent-factory-the-future-of-ai-software-with-evp-of-core-ai-jay-parikh Chapters: (00:00) Introduction (2:43) Jay's Background & Microsoft Role (4:33) The Reasoning Revolution (6:45) From Software Factory to Agent Factory (8:38) Building the Agent Factory (10:54) Impact on Microsoft's Future (12:49) AI Code Generation & Productivity (14:46) Shifting Engineering Focus with AI (16:22) Future of Software Development (18:17) Real-World AI Productivity Gains (20:18) Microsoft's AI Infrastructure Investments (24:01) Challenges with AI Evaluation & Observability (26:12) Model Choices & Microsoft's Strategy (28:40) Audience Q&A 

When you're managing $60 trillion in assets across dozens of products and 30 global jurisdictions, technical debt isn't just an inconvenience—it's an existential risk.Jason Adams, Interim CTO of Charles River, a State Street Company, leads 800 engineers building mission-critical trading platforms for the world's largest asset managers. Joined by Sid Pardeshi, Co-Founder and CTO of Blitzy, he explains how State Street is using an AI-augmented SDLC to modernize decades-old systems, refactor legacy code, and dramatically increase developer productivity—without compromising the rigor required in financial services.Jason frames the strategy around three pillars: AI for engineering (copilots and polyglot support),AI for operations (APM, observability, and proactive monitoring), andAI embedded in products (LLM-powered explainers).Using Blitzy's agentic approach—iterative context building, dependency mapping, and targeted code generation—State Street compressed months of work into weeks while maintaining strict quality gates.About the Guests:Jason AdamsJason Adams is the Interim CTO of Charles River, a State Street Company. He brings deep expertise in modernizing legacy fintech infrastructure into scalable, cloud-native systems that support mission-critical financial services at global scale.Previously, Jason was Head of Platform Product and Strategy at Charles River Development and CTO of Mercatus (acquired by State Street and now part of Charles River for Private Markets). He has led high-impact initiatives across engineering, product, and cloud infrastructure, with extensive experience guiding end-to-end delivery teams.Today, Jason is driving a comprehensive SaaS transformation at CRD, focused on building resilient, future-ready architectures. From scaling global engineering organizations to delivering secure, high-performance platforms, he is committed to advancing innovation, agility, and long-term growth across Charles River, State Street Alpha, and State Street.Sid PardeshiSid Pardeshi is a technology leader and entrepreneur, currently Co-Founder and CTO of Blitzy. He holds a Harvard MS/MBA and previously served as a Software Architect at NVIDIA, where he built deep expertise at the intersection of AI, large-scale software systems, and product innovation.At NVIDIA, Sid was recognized as a Master Inventor, earning the Inventor's Jacket for driving AI-powered product innovation, with more than 25 U.S. patents filed across gaming, augmented reality, and virtual reality. He is also a seasoned software engineer with a strong track record in application performance optimization, delivering native client load-time improvements of up to 90%.Beyond hands-on engineering, Sid has led and coordinated software design, framework requirements, and application architecture across global teams of 500+ engineers. Today, he applies this blend of innovation, technical depth, and organizational leadership to building autonomous software development platforms that help enterprises modernize at scale.Timestamps:00:30 – Jason on Managing $60 Trillion in Assets01:55 – Challenges and Strategies in Financial Services07:00 – Embracing AI for Modernization09:10 – AI in Software Development Lifecycle15:55 – Ensuring Quality and Compliance with AI23:55 – AI in Operations and Incident Response26:00 – Proactive Workflow Monitoring26:20 – AI in SDLC: Creation to Operations30:00 – Challenges in AI Recommendations33:20 – Iterative Context Building with AI36:00 – Human Side of AI Transformation42:30 – Adopting AI Tools in Financial ServicesGuest Highlights:"One of the things that excites me the most right now is the ability to use an AI-augmented SDLC to drive modernization. Otherwise, with this many systems, it's too hard." — Jason "You have to invest in the non-attractive parts first. You have to build a foundation that's gonna support being able to bring on solutions and tools that could change your overall enterprise SDLC. That's a lot of work and that's a major investment." — Jason "We are unlocking by adding these additional capabilities and additional assurance that improves quality exponentially more than we could have in the past. Now I can have an agent swarm check itself—multiple agents doing code review at a level of depth we just don't have time to get to." — JasonGet Connected:Jason Adams on LinkedInSid Pardeshi on LinkedInYousuf Kahn on LinkedInIan Faison on LinkedInHungry for more tech talk? Check out latest episodes at ciopod.com: Ep 63 - How Autonomous AI is Solving the Enterprise Modernization ChallengeEp 62 - Running IT Like a Growth EngineEp 61 - What Manufacturing Can Teach You About Scaling Enterprise AILearn more about Caspian Studios: caspianstudios.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Send us a textThis episode is a rerun.Andrew and Lisa are Menlonians (team members at Menlo Innovations). They do things different there. And even though they develop software products, the processes they use are supremely applicable to developing hard goods products, as well. Join us as we discuss “the Menlo way” and paired work, kindergarten skills, storycards, and other methods of producing the right product, on budget, and on schedule.Download the Essential Guide to Designing Test Fixtures: https://pipelinemedialab.beehiiv.com/test-fixtureAbout Being An Engineer The Being An Engineer podcast is a repository for industry knowledge and a tool through which engineers learn about and connect with relevant companies, technologies, people resources, and opportunities. We feature successful mechanical engineers and interview engineers who are passionate about their work and who made a great impact on the engineering community. The Being An Engineer podcast is brought to you by Pipeline Design & Engineering. Pipeline partners with medical & other device engineering teams who need turnkey equipment such as cycle test machines, custom test fixtures, automation equipment, assembly jigs, inspection stations and more. You can find us on the web at www.teampipeline.us

Xmas Special: Why project management tools fail software development - and what works instead! In this BONUS episode, we dive deep into The Project Management Trap, continuing our exploration from Episode 1 where we established that software is societal infrastructure being managed with tools from the 1800s. We examine why project management frameworks - designed for building railroads and ships - are fundamentally misaligned with software development, and what happens when we treat living capabilities like construction projects with defined endpoints. The Origin Story - Where Project Management Came From "The problem isn't that project management is bad. The problem is that software isn't building a railroad or a building, or setting up a process that will run forever (like a factory)." Project management emerged from industries with hard physical constraints - building the Transcontinental Railroad in the 1860s, coordinating factory machinery, managing finite and expensive materials. The Gantt chart, invented in the 1910s for factory scheduling, worked brilliantly for coordinating massive undertakings with calculable physics, irreversible decisions, and clear completion points. When the rails met, you were done. When the bridge was built, the project ended. These tools gave us remarkable precision for building ships, bridges, factories, and highways. But software operates in a completely different reality - one where the raw materials are time and brainpower, not minerals and hardware, and where the transformation happens in unique creative moments rather than repeated mechanical movements. The Seductive Clarity Of Project Management Artifacts "In software, we almost never know either of those things with certainty." Project management is tempting for software leaders because it offers comforting certainty. Gantt charts show every task laid out, milestones mark clear progress, "percent complete" gives us a number, and a defined "done" promises relief. The typical software project kickoff breaks down into neat phases: requirements gathering (6 weeks), design (4 weeks), development (16 weeks), testing (4 weeks), deployment (2 weeks) - total 32 weeks, done by Q3. Leadership loves this. Finance can budget it. Everyone can plan around it. But this is false precision. Software isn't pouring concrete where you measure twice and pour once. Every line of code is a hypothesis about what users need and how the system should behave. That 32-week plan assumes we know exactly what to build and exactly how long each piece takes - assumptions that are almost never true in software development. The Completion Illusion "Software products succeed by evolving. Projects end; products adapt." "Done" is the wrong goal for living software. We expand on the Slack story from Episode 1 to illustrate this point. If Slack's team had thought in project terms in 2013, they might have built a functional tool with channels, direct messages, file sharing, and search - shipped on time and on budget by Q2 2014, project complete. But that wasn't the end; it was the beginning. Through continuous user feedback and evolution, Slack added threaded conversations (2017), audio/video calls (2016), workflow automation (2019), and Canvas for knowledge management (2023). Each wasn't maintenance or bug fixing - these were fundamental enhancements. Glass's research shows that 60% of maintenance costs are enhancements, not fixes. By 2021, when Salesforce acquired Slack for $27.7 billion, it bore little resemblance to the 2014 version. The value wasn't in that initial "project" - it was in the continuous evolution. If they'd thought "build it, ship it, done," Slack would have died competing against HipChat and Campfire. When Projects Succeed (Well, Some Do, Anyway) But Software Fails "They tried to succeed at project management. They ended up failing at both software delivery AND project management!" Vasco references his article "The Software Crisis is Real," examining five distinct cases from five different countries that represent what's wrong with project thinking for software. These projects tried hard to do everything right by project management standards: detailed requirements (thousands of pages), milestone tracking, contractor coordination, hitting fixed deadlines, and proper auditing. What they didn't have was iterative delivery to test with real users early, feedback loops to discover problems incrementally, adaptability to change based on learning, or a "living capability" mindset. Project thinking demanded: get all requirements right upfront (otherwise no funding), build it all, test at the end, launch on deadline. Software thinking demands: launch something minimal early, get real user feedback, iterate rapidly, evolve the capability. These projects succeeded at following project management rules but failed at delivering valuable software. What Software-Native Delivery Management Looks Like "Software is unpredictable not because we're bad at planning - it's unpredictable because we're creating novel solutions to complex problems, and in a completely different economic system." If not projects, then what? Vasco has been exploring this question for years, since publishing the NoEstimates book. The answer starts with thinking in products and capabilities, not projects - recognizing that products have ongoing evolution, capabilities are cultivated and improved rather than "delivered" and done, and value is measured in outcomes rather than task completion. Instead of comprehensive planning, we need iteration and constant decision-making based on validated hypotheses: start with "We believe users need X," run experiments by building small and testing with real users, then learn and adapt. Instead of fixed scope, define the problem (not the solution), allow the solution to evolve as you learn, and optimize for learning speed rather than task completion.  The contrast is clear: project thinking says "We will build features A, B, C, D, and E by Q3, then we're done." Software-native thinking says "We're solving problem X for users. We'll start with the riskiest hypothesis, build a minimal version, ship it to 100 users next week, and learn whether we're on the right track." The appropriate response to software's inherent unpredictability isn't better planning - it's faster learning. References for Further Reading Vasco Duarte's article on the Software Leadership Workshop newsletter: "The Software Crisis is Real"  Glass, Robert L. "Facts and Fallacies of Software Engineering" - Fact 42: "Enhancement is responsible for roughly 60 percent of software maintenance costs. Error correction is roughly 17 percent. Therefore, software maintenance is largely about adding new capability to old software, not fixing it." NoEstimates Book: How To Measure Project Progress Without Estimating Slack evolution timeline: Company history and feature releases  The unexpected design challenge behind Slack's new threaded conversations Slack voice and video chat Slack launches admin workflow automation and announcement channels  Meet Slack Canvas - Slack's answer to the knowledge management problem. About Vasco Duarte Vasco Duarte is a thought leader in the Agile space, co-founder of Agile Finland, and host of the Scrum Master Toolbox Podcast, which has over 10 million downloads. Author of NoEstimates: How To Measure Project Progress Without Estimating, Vasco is a sought-after speaker and consultant helping organizations embrace Agile practices to achieve business success. You can link with Vasco Duarte on LinkedIn.

Xmas Special: Software Industry Transformation - Why Software Development Must Mature Welcome to the 2025 Xmas special - a five-episode deep dive into how software as an industry needs to transform. In this opening episode, we explore the fundamental disconnect between how we manage software and what software actually is. From small businesses to global infrastructure, software has become the backbone of modern society, yet we continue to manage it with tools designed for building ships in the 1800s. This episode sets the stage for understanding why software development must evolve into a mature discipline. Software Runs Everything Now "Without any single piece, I couldn't operate - and I'm tiny. Scale this reality up: software isn't just in tech companies anymore." Even the smallest businesses today run entirely on software infrastructure. A small consulting and media business depends on WordPress for websites, Kajabi for courses, Stripe for payments, Quaderno for accounting, plus email, calendar, CRM systems, and AI assistants for content creation. The challenge? We're managing this critical infrastructure with tools designed for building physical structures with fixed requirements - an approach that fundamentally misunderstands what software is and how it evolves. This disconnect has to change. The Oscillation Between Technology and Process "AI amplifies our ability to create software, but doesn't solve the fundamental process problems of maintaining, evolving, and enhancing that software over its lifetime." Software improvement follows a predictable pattern: technology leaps forward, then processes must adapt to manage the new complexity. In the 1960s-70s, we moved from machine code to COBOL and Fortran, which was revolutionary but led to the "software crisis" when we couldn't manage the resulting complexity. This eventually drove us toward structured programming and object-oriented programming as process responses, which, in turn, resulted in technology changes! Today, AI tools like GitHub Copilot, ChatGPT, and Claude make writing code absurdly easy - but writing code was never the hard part. Robert Glass documents in "Facts and Fallacies of Software Engineering" that maintenance typically consumes between 40 and 80 percent of software costs, making "maintenance" probably the most important life cycle phase. We're overdue for a process evolution that addresses the real challenge: maintaining, evolving, and enhancing software over its lifetime. Software Creates An Expanding Possibility Space "If they'd treated it like a construction project ('ship v1.0 and we're done'), it would never have reached that value." Traditional project management assumes fixed scope, known solutions, and a definable "done" state. The Sydney Opera House exemplifies this: designed in 1957, completed in 1973, ten times over budget, with the architect resigning - but once built, it stands with "minimal" (compared to initial cost) maintenance. Software operates fundamentally differently. Slack started as an internal tool for a failed gaming company called Glitch in 2013. When the game failed, they noticed their communication tool was special and pivoted entirely. After launching in 2014, Slack continuously evolved based on user feedback: adding threads in 2017, calls in 2016, workflow builder in 2019, and Canvas in 2023. Each addition changed what was possible in organizational communication. In 2021, Salesforce acquired Slack for $27.7 billion precisely because it kept evolving with user needs. The key difference is that software creates possibility space that didn't exist before, and that space keeps expanding through continuous evolution. Software Is Societal Infrastructure "This wasn't a cyber attack - it was a software update gone wrong." Software has become essential societal infrastructure, not optional and not just for tech companies. In July 2024, a faulty software update from cybersecurity firm CrowdStrike crashed 8.5 million Windows computers globally. Airlines grounded flights, hospitals canceled surgeries, banks couldn't process transactions, and 911 services went down. The global cost exceeded $10 billion. This wasn't an attack - it was a routine update that failed catastrophically. AWS outages in 2021 and 2023 took down major portions of the internet, stopping Netflix, Disney+, Robinhood, and Ring doorbells from working. CloudFlare outages similarly cascaded across daily-use services. When software fails, society fails. We cannot keep managing something this critical with tools designed for building physical things with fixed requirements. Project management was brilliant for its era, but that era isn't this one. The Path Ahead: Four Critical Challenges "The software industry doesn't just need better tools - it needs to become a mature discipline." This five-episode series will address how we mature as an industry by facing four critical challenges: Episode 2: The Project Management Trap - Why we think in terms of projects, dates, scope, and "done" when software is never done, and how this mindset prevents us from treating software as a living capability Episode 3: What's Already Working - The better approaches we've already discovered, including iterative delivery, feedback loops, and continuous improvement, with real examples of companies doing this well Episode 4: The Organizational Immune System - Why better approaches aren't universal, how organizations unconsciously resist what would help them, and the hidden forces preventing adoption Episode 5: Software-Native Organizations - What it means to truly be a software-native organization, transforming how the business thinks, not just using agile on teams Software is too important to our society to keep getting it wrong. We have much of the knowledge we need - the challenge is adoption and evolution. Over the next four episodes, we'll build this case together, starting with understanding why we keep falling into the same trap. References For Further Reading Glass, Robert L. "Facts and Fallacies of Software Engineering" - Fact 41, page 115  CrowdStrike incident: https://en.wikipedia.org/wiki/2024_CrowdStrike_incident  AWS outages: 2021 (Dec 7), 2023 (June 13),  and November 2025 incidents  CloudFlare outages: 2022 (June 21), and November 2025 major incident  Slack history and Salesforce acquisition: https://en.wikipedia.org/wiki/Slack_(software)  Sydney Opera House: https://en.wikipedia.org/wiki/Sydney_Opera_House About Vasco Duarte Vasco Duarte is a thought leader in the Agile space, co-founder of Agile Finland, and host of the Scrum Master Toolbox Podcast, which has over 10 million downloads. Author of NoEstimates: How To Measure Project Progress Without Estimating, Vasco is a sought-after speaker and consultant helping organizations embrace Agile practices to achieve business success. You can link with Vasco Duarte on LinkedIn.

How is AI going to change software development? Live from the Philly.NET user group, Carl and Richard have Jeff Fritz and Bill Wolff chat about how AI technologies are impacting software development. The conversation opens with a listener concerned about the costs and controls around AI technology. There are a variety of approaches to using these tools; Jeff and Bill talk about the work they have done and some of the challenges. There is enormous potential here, but the paths forward aren't clear yet - more is to come!

Originally published on the a16z Infra podcast. We're resurfacing it here for our main feed audience.AI coding is already actively changing how software gets built.a16z Infra Partners Yoko Li and Guido Appenzeller break down how "agents with environments" are changing the dev loop; why repos and PRs may need new abstractions; and where ROI is showing up first. We also cover token economics for engineering teams, the emerging agent toolbox, and founder opportunities when you treat agents as users, not just tools. Resources:Follow Yoko on X: https://x.com/stuffyokodrawsFollow Guido on X: https://x.com/appenz Stay Updated:If you enjoyed this episode, be sure to like, subscribe, and share with your friends!Find a16z on X: https://x.com/a16zFind a16z on LinkedIn: https://www.linkedin.com/company/a16zListen to the a16z Podcast on Spotify: https://open.spotify.com/show/5bC65RDvs3oxnLyqqvkUYXListen to the a16z Podcast on Apple Podcasts: https://podcasts.apple.com/us/podcast/a16z-podcast/id842818711Follow our host: https://x.com/eriktorenbergPlease note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see http://a16z.com/disclosures Stay Updated:Find a16z on XFind a16z on LinkedInListen to the a16z Show on SpotifyListen to the a16z Show on Apple PodcastsFollow our host: https://twitter.com/eriktorenberg Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.