Podcasts about Software development

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

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.

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.

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

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!

As AI adoption accelerates across the software industry, engineering leaders are increasingly focused on a harder question: how to understand whether these tools are actually improving developer experience and organizational outcomes.In this year-end episode of the Engineering Enablement podcast, host Laura Tacho is joined by Brian Houck from Microsoft, Collin Green and Ciera Jaspan from Google, and Eirini Kalliamvakou from GitHub to examine what 2025 research reveals about AI impact in engineering teams. The panel discusses why measuring AI's effectiveness is inherently complex, why familiar metrics like lines of code continue to resurface despite their limitations, and how multidimensional frameworks such as SPACE and DORA provide a more accurate view of developer productivity.The conversation also looks ahead to 2026, exploring how AI is beginning to reshape the role of the developer, how junior engineers' skill sets may evolve, where agentic workflows are emerging, and why some widely shared AI studies were misunderstood. Together, the panel offers a grounded perspective on moving beyond hype toward more thoughtful, evidence-based AI adoption.Where to find Brian Houck:• LinkedIn: https://www.linkedin.com/in/brianhouck/ • Website: https://www.microsoft.com/en-us/research/people/bhouck/ Where to find Collin Green: • LinkedIn: https://www.linkedin.com/in/collin-green-97720378 • Website: https://research.google/people/107023Where to find Ciera Jaspan: • LinkedIn: https://www.linkedin.com/in/ciera • Website: https://research.google/people/cierajaspan/Where to find Eirini Kalliamvakou: • LinkedIn: https://www.linkedin.com/in/eirini-kalliamvakou-1016865/• X: https://x.com/irina_kAl • Website: https://www.microsoft.com/en-us/research/people/eikalliWhere to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact) https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro(02:35) Introducing the panel and the focus of the discussion(04:43) Why measuring AI's impact is such a hard problem(05:30) How Microsoft approaches AI impact measurement(06:40) How Google thinks about measuring AI impact(07:28) GitHub's perspective on measurement and insights from the DORA report(10:35) Why lines of code is a misleading metric(14:27) The limitations of measuring the percentage of code generated by AI(18:24) GitHub's research on how AI is shaping the identity of the developer(21:39) How AI may change junior engineers' skill sets(24:42) Google's research on using AI and creativity (26:24) High-leverage AI use cases that improve developer experience(32:38) Open research questions for AI and developer productivity in 2026(35:33) How leading organizations approach change and agentic workflows(38:02) Why the METR paper resonated and how it was misunderstoodReferenced:• Measuring AI code assistants and agents• Kiro• Claude Code - AI coding agent for terminal & IDE• SPACE framework: a quick primer• DORA | State of AI-assisted Software Development 2025• Martin Fowler - by Gergely Orosz - The Pragmatic Engineer• Seamful AI for Creative Software Engineering: Use in Software Development Workflows | IEEE Journals & Magazine | IEEE Xplore• AI Where It Matters: Where, Why, and How Developers Want AI Support in Daily Work - Microsoft Research• Unpacking METR's findings: Does AI slow developers down?• DX Annual 2026

Podcast: Within Reason with Hank GreenPodcast: Within Reason with VsaucePodcast: Acquired: Microsoft Volume IFavorite Cup o' Go episodes of 2025May 17, Episode 110: Thanks, Ian.

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.

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.

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.

Go 1.26rc1 is outBook: Gist of Go: Concurrency by Anton Zhiyanov

Today, our hosts try to fend off the December doldrums, the cold weather sleepies, the fog of too many video conferences, by thinking broadly about the year that was and the year to come. It's the last episode of the year, so let's be honest: they're taking voicemails and chitchatting. Come be a fly on the wall!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!

In our popular year-end recap, our hosts are all back tother and joined by guest Josh Yoes to review the biggest React Native developments of 2025! They cover major releases, the shift to the new architecture, React 19 support, and how tooling and performance evolved across the ecosystem. Connect With Us!Blog Post | React Native Wrapped 2025 by Joshua Yoes Connect With Us!Josh Yoes: @JoshuaYoesJamon Holmgren: @jamonholmgrenRobin 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.

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!

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!

In this episode of Supply Chain Connections, Greg Slawson joins Brian Glick to share insights from a career spanning automotive manufacturing, global consulting, logistics tech startups, and leading freight forwarders. The conversation dives deep into how large organizations approach decision-making, how to handle cultural differences in global logistics, and what the future holds for technology in the industry.Topics covered include: The evolution of Greg's supply chain journey from Ford to Deloitte to DSV Lessons on navigating bureaucracy, change management, and cross-cultural communication The challenge of balancing customer needs with asset utilization in large carriers The emerging role of agentic AI and orchestration in reducing manual, low-value tasks Practical AI applications for 3PLs to boost efficiency and profitability Why real partnerships between shippers and service providers are rare—but powerful when they happen The ongoing shift toward more volatile, opportunity-rich global supply chainsAbout the Guest: Greg Slawson brings over 35 years of supply chain and logistics leadership spanning automotive, technology, and consulting sectors. His career includes senior roles at Ford Motor Company in supply chain and logistics operations, followed by executive positions as VP at G-Log/Oracle, CEO at OPS, and EVP Vertical Lead at DSV, one of the world's largest logistics providers. Throughout his career, Greg has driven operational excellence and strategic transformation across complex global supply chains.Connect with GregConnect with BrianFollow Chain.io on LinkedIn

In this episode, Jenna interviews Woodson Martin, CEO of OutSystems, about how AI only really assists with a portion of the software development life cycle.They discuss:The areas that will still require a human touchThe evolution of the developer role and how success should be measured differentlyThe bottlenecks that still exist even with AI-assisted coding

Julian Sequeira from PyBites joins Sean and Kelly to share their top holiday gift picks for coders, makers, and educators. This episode features 15+ gift ideas ranging from budget-friendly maker tools to classroom robots—plus book recommendations, coding platforms, and a few surprises. Show Notes Wins of the Week Julian: Staying focused on "the one thing" at PyBites, plus 3D printing a custom cappuccino stencil for his local café Kelly: Surviving a muddy, clay-covered hill in North Carolina while on vacation Sean: Designing and 3D printing a custom bracket for his screen door using Fusion 360 Holiday Gift Ideas Julian's Picks Hoverboard with Go-Kart Attachment (~$299 AUD) - Two-wheeled self-balancing boards that can convert to a go-kart with a third wheel attachment. Available at Hoveroo (https://hoveroo.com.au) in Australia. Secret Coders Book Series (~$10-20 USD each) - A six-book graphic novel series that wraps coding puzzles and concepts into mystery stories. Recommended by Faye Shaw from the Boston PyLadies community. Great for ages 8-15. 3D Printer (~$200-300 USD) - Entry-level printers like the Bambu Lab A1 Mini or Elegoo Neptune 4 Pro have dropped significantly in price. Look for auto bed leveling as a key feature. Duolingo Chess (~$13/month with subscription) - A new addition to Duolingo that teaches chess tactics, strategy, and formal terminology through structured lessons. Great for building problem-solving skills. Classic Video Games (Zelda, Pokémon) - Story-driven games that build resilience and problem-solving skills, as an alternative to dopamine-heavy platforms like Roblox. Kelly's Picks Soccer Bot (~$59.99) - An indoor soccer training robot that challenges footwork skills. Works best on hard floors. "The Worlds I See" by Dr. Fei-Fei Li - Memoir of the computer scientist behind ImageNet and modern image recognition, covering her immigrant journey and rise in AI. A must-read for anyone interested in AI. LEGO Retro Radio Building Set (~$99) - A 1970s-style radio that you build, then insert your phone to play music. Features working dials that create authentic radio crackle sounds. Spydroid Loco Hex Robot (classroom investment) - A large spider-shaped robot that codes in Python and block programming. Features LIDAR and AI-based mapping. Seen at ISTE. Richtie Mini from Hugging Face ($299-$449) - An adorable AI desktop companion robot with onboard models. Two versions: one that connects to your computer and one that's self-contained. Sean's Picks LED Pucks (LED 001 Kit) (~$6-13) - Small USB-powered LED discs perfect for 3D printed projects like planet lamps. Available from Bambu Labs or Amazon. RGB versions include remote controls. Daily Desk Calendar (~$15-20) - A throwback gift that provides daily doses of humor, trivia, or inspiration. Suggestions include The Far Side, "They Can Talk," or "How to Win Friends and Influence People." PyBites Coding Platform (subscription) - Bite-sized Python challenges for sharpening coding skills. Great for teachers, students, and professionals looking for practical coding practice. Digital Calipers (~$40-50) - USB-rechargeable precision measuring tools essential for 3D printing and maker projects. Great for teaching geometry and measurement concepts. Deburring Tool (~$10) - A small tool with a curved swiveling blade for cleaning up 3D prints. A quality-of-life improvement for any maker's toolkit. Links Mentioned PyBites (https://pybit.es) - Python coaching and coding challenges Hoveroo (https://hoveroo.com.au) - Hoverboards (Australia) Bambu Lab (https://bambulab.com) - 3D printers and LED pucks Printables (https://www.printables.com) - 3D printing models MakerWorld (https://makerworld.com) - 3D printing models Hugging Face Richtie Mini (https://huggingface.co) - AI companion robot Duolingo (https://duolingo.com) - Language learning app with chess Secret Coders book series - Available on Amazon "The Worlds I See" by Dr. Fei-Fei Li - Available at bookstores Upcoming Events PyCon US 2026 - Long Beach, California Education Summit - Proposals open after the holidays, deadline around March/April Submit proposals when the website opens! Special Guest: Julian Sequeira.

Gin is a very bad software library by Efron LichtBun SQL injection via error messagesModernizing Reddit's Comment Backend Infrastructure by Katie ShannonInterview with Erik St. Martin & Johnny BoursiquotGopherCon ★ Support this podcast on Patreon ★

For episode 50, Andy (who wants to be "the guy who doesn't know what we're talking about") presents Dan (who wants to "feel prepared") with the ultimate surprise: LIVE HOMEWORK. Deep down the rabbit hole, this week is no voicemails and all surprises. Dive in with us.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!

From applied cryptography and offensive security in France's defense industry to optimizing nuclear submarine workflows, then selling his e-signature startup to Docusign (https://www.docusign.com/company/news-center/opentrust-joins-docusign-global-trust-network and now running AI as CTO of Superhuman Mail (Superhuman, recently acquired by Grammarly https://techcrunch.com/2025/07/01/grammarly-acquires-ai-email-client-superhuman/), Loïc Houssier has lived the full arc from deep infra and compliance hell to obsessing over 100ms product experiences and AI-native email. We sat down with Loïc to dig into how you actually put AI into an inbox without adding latency, why Superhuman leans so hard into agentic search and “Ask AI” over your entire email history, how they design tools vs. agents and fight agent laziness, what box-priced inference and local-first caching mean for cost and reliability, and his bet that your inbox will power your future AI EA while AI massively widens the gap between engineers with real fundamentals and those faking it. We discuss: Loïc's path from applied cryptography and offensive security in France's defense industry to submarines, e-signatures, Docusign, and now Superhuman Mail What 3,000+ engineers actually do at a “simple” product like Docusign: regional compliance, on-prem appliances, and why global scale explodes complexity How Superhuman thinks about AI in email: auto-labels, smart summaries, follow-up nudges, “Ask AI” search, and the rule that AI must never add latency or friction Superhuman's agentic framework: tools vs. agents, fighting “agent laziness,” deep semantic search over huge inboxes, and pagination strategies to find the real needle in the haystack How they evaluate OpenAI, Anthropic, Gemini, and open models: canonical queries, end-to-end evals, date reasoning, and Rahul's infamous “what wood was my table?” test Infra and cost philosophy: local-first caching, vector search backends, Baseten “box” pricing vs. per-token pricing, and thinking in price-per-trillion-tokens instead of price-per-million The vision of Superhuman as your AI EA: auto-drafting replies in your voice, scheduling on your behalf, and using your inbox as the ultimate private data source How the Grammarly + Coda + Superhuman stack could power truly context-aware assistance across email, docs, calendars, contracts, and more Inside Superhuman's AI-dev culture: free-for-all tool adoption, tracking AI usage on PRs, and going from ~4 to ~6 PRs per engineer per week Why Loïc believes everyone should still learn to code, and how AI will amplify great engineers with strong fundamentals while exposing shallow ones even faster — Loïc Houssier LinkedIn: https://www.linkedin.com/in/houssier/ Where to find Latent Space X: https://x.com/latentspacepod Substack: https://www.latent.space/ Chapters 00:00:00 Introduction and Loïc's Journey from Nuclear Submarines to Superhuman 00:06:40 Docusign Acquisition and the Enterprise Email Stack 00:10:26 Superhuman's AI Vision: Your Inbox as the Real AI Agent 00:13:20 Ask AI: Agentic Search and the Quality Problem 00:18:20 Infrastructure Choices: Model Selection, Base10, and Cost Management 00:27:30 Local-First Architecture and the Database Stack 00:30:50 Evals, Quality, and the Rahul Wood Table Test 00:42:30 The Future EA: Auto-Drafting and Proactive Assistance 00:46:40 Grammarly Acquisition and the Contextual Advantage 00:38:40 Voice, Video, and the End of Writing 00:51:40 Knowledge Graphs: The Hard Problem Nobody Has Solved 00:56:40 Competing with OpenAI and the Browser Question 01:02:30 AI Coding Tools: From 4 to 6 PRs Per Week 01:08:00 Engineering Culture, Hiring, and the Future of Software Development

This year's DORA report focuses on AI-assisted software development. While one of the key themes is just how ubiquitous AI is today in software engineering, that's only part of the picture. In fact, the report outlines many of the challenges the adoption of these technologies are posing and explores the barriers and obstacles that need to be addressed to ensure AI-assistance leads to long-term success. In this episode of the Technology Podcast, host Ken Mugrage is joined by Chris Westerhold — Global Practice Director for Engineering Excellence at Thoughtworks — to discuss this year's DORA report (for which Thoughtworks is a Platinum sponsor). They dive into some of the reports findings, and explore the risks of increasing throughput, the changing demands on software developers, the importance of developer experience and how organizations can go about successfully measuring AI impact. You can find the 2025 DORA report here: https://cloud.google.com/resources/content/2025-dora-ai-assisted-software-development-report Read Chris Westerhold's article on this year's findings: https://www.thoughtworks.com/insights/articles/the-dora-report-2025--a-thoughtworks-perspective  

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.

Visit https://cupogo.dev/ for all the links. Seriously, we have the entire internet there!... with enough click depth, that is

Today we're talking talking talking loopers! Andy presents the Boomerang III Phrase Sampler, his trusted loop pedal for over a decade. They talk about what features set it apart, some other favorite loopers, where a looper should go in your signal chain (spoiler alert: everywhere), the difference in attitudes between a looper and a microlooper, and of course take some calls on the hogline.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!

Mazen and Jamon chat with Simon Grimm about his move from Ionic pioneer to React Native creator. Simon highlights key cross-platform trends, why React Native's future looks exciting, and how he supports developers through Galaxies.dev. Show NotesSimon Grimm's podcast, Rocket Ship: https://podcast.galaxies.devZero to Hero, Launch Your First Real Mobile App in 30 Days: https://galaxies.dev/missions/zero-to-hero  Connect With Us!Simon Grimm: @schlimmsonMazen Chami: @mazenchamiJamon Holmgren: @jamonholmgrenReact 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.

In Episode 164 of Cybersecurity Where You Are, Tony Sager sits down with Curt Dukes, EVP and General Manager of Security Best Practices at the Center for Internet Security® (CIS®), and Steve Lipner, Executive Director of SAFECode.org. Together, they explore the evolution of secure software development and why secure by design is critical for reducing risk in today's complex environments.Here are some highlights from our episode:01:08. Introductions to Curt and Steve04.01. The historical challenge of implementation errors in software security08:41. The emergence of secure by design and the need to measure against specified criteria14:39. The value of artifacts as evidence of secure software development28:52: How the CIS Critical Security Controls® (CIS Controls®) support secure software39:59. The use of community projects to address challenges like secure by designResourcesSecure by Design: A Guide to Assessing Software Security PracticesHow Secure by Design Helps Developers Build Secure SoftwareCIS, SAFECode Launch Secure by Design Guide to Help Developers Meet National Software Security ExpectationsEpisode 107: Continuous Improvement via Secure by DesignSecure by DesignSecure Software Development FrameworkEpisode 63: Building Capability and Integration with SBOMsIf you have some feedback or an idea for an upcoming episode of Cybersecurity Where You Are, let us know by emailing podcast@cisecurity.org.

In this episode of the Shift AI Podcast, Jeff Reihl, Technology Chairman at LexisNexis and former CTO, joins host Boaz Ashkenazy to discuss how one of the world's largest legal information companies executed a dramatic pivot to generative AI. Jeff shares the remarkable story of how LexisNexis transformed their entire 2023 strategy in response to ChatGPT's emergence, leveraging their 160 billion document repository to solve AI hallucination problems that plague the legal profession.From modernizing mainframe systems written in IBM assembly language to implementing multi-model AI strategies using GPT and Claude, Jeff provides a masterclass in enterprise AI adoption. The conversation explores critical topics including maintaining trust and accuracy in legal AI applications, the evolving role of junior lawyers in an AI-augmented world, and how LexisNexis achieved 300% ROI for their customers while dramatically accelerating their own internal processes. Whether you're leading digital transformation at an established enterprise or simply curious about how AI is reshaping professional services, this episode offers invaluable lessons from the frontlines of the legal AI revolution.Chapters[01:40] Jeff's Background and Career Journey[05:54] LexisNexis, RELX, and the Legal Information Industry[07:21] The ChatGPT Revolution and Strategic Pivot[10:17] Solving the Hallucination Problem with RAG[13:26] Liability, Accountability, and the Role of Legal Professionals[16:16] ROI Metrics and Customer Adoption[21:02] Agentic Workflows and Strategic Partnerships[26:18] The Future of Junior Lawyers and Legal Education[29:05] The Future of Work and Software Development[31:33] Framework for AI Integration in Organizations[34:46] Two Words for the Future: Transformative and PersonalizedConnect with Jeff Reihlhttps://www.linkedin.com/in/jeffreihl/Connect with Boaz AshkenazyLinkedIn: https://linkedin.com/in/boazashkenazy Email: info@shiftai.fm

What if your sales team woke up on Monday to a calendar already full of qualified discovery calls? In this episode of Sharkpreneur, Seth Greene interviews Gabe Lullo, CEO of Alleyoop, who has helped companies from startups to giants like Microsoft, Peloton, and ZoomInfo transform their sales pipelines. Under his leadership, Alleyoop.io has pioneered a two-step model that separates prospecting from closing—backed by 11 million cold calls a year and a focus on authenticity in outreach. In this episode, Gabe shares the systems, stories, and strategies that have fueled Alleyoop.io's rapid growth and its role in scaling billion-dollar brands. Key Takeaways: → The two-step approach that separates prospecting from closing. → How Alleyoop.io serves both startups and global enterprises. → The “hot lead vs. warm lead” model—and why timing matters. → What really causes sales teams to stall (hint: it's not always leads). → Why most “lead gen companies” aren't actually prospecting. Gabe Lullo's expertise in sales, marketing, recruiting, and management began when he started his own business after graduation from the Barney School of Business at the University of Hartford. He owned and operated his own sales, training, and marketing firm for more than a decade. He excelled in training sales and marketing professionals, and additionally, Gabe has had a successful career in executive recruiting. He has been instrumental in expanding the company's search and placement for IT, Software Development, Sales, Customer Success, Marketing, and Executive leaders. Gabe's most recent success has been with us here at Alleyoop. For many years he has been working to build and grow the company by focusing on our culture, environment, customer success, and sales. Connect With Gabe Lullo: Website: https://alleyoop.io/ LinkedIn: https://www.linkedin.com/company/alleyoop-io/ Learn more about your ad choices. Visit megaphone.fm/adchoices

What if your sales team woke up on Monday to a calendar already full of qualified discovery calls? In this episode of Sharkpreneur, Seth Greene interviews Gabe Lullo, CEO of Alleyoop, who has helped companies from startups to giants like Microsoft, Peloton, and ZoomInfo transform their sales pipelines. Under his leadership, Alleyoop.io has pioneered a two-step model that separates prospecting from closing—backed by 11 million cold calls a year and a focus on authenticity in outreach. In this episode, Gabe shares the systems, stories, and strategies that have fueled Alleyoop.io's rapid growth and its role in scaling billion-dollar brands. Key Takeaways: → The two-step approach that separates prospecting from closing. → How Alleyoop.io serves both startups and global enterprises. → The “hot lead vs. warm lead” model—and why timing matters. → What really causes sales teams to stall (hint: it's not always leads). → Why most “lead gen companies” aren't actually prospecting. Gabe Lullo's expertise in sales, marketing, recruiting, and management began when he started his own business after graduation from the Barney School of Business at the University of Hartford. He owned and operated his own sales, training, and marketing firm for more than a decade. He excelled in training sales and marketing professionals, and additionally, Gabe has had a successful career in executive recruiting. He has been instrumental in expanding the company's search and placement for IT, Software Development, Sales, Customer Success, Marketing, and Executive leaders. Gabe's most recent success has been with us here at Alleyoop. For many years he has been working to build and grow the company by focusing on our culture, environment, customer success, and sales. Connect With Gabe Lullo: Website: https://alleyoop.io/ LinkedIn: https://www.linkedin.com/company/alleyoop-io/ Learn more about your ad choices. Visit megaphone.fm/adchoices

In today's episode, Dan wants to talk about flangers, and the turning point in his own journey that was the Ibanez SF10 Swell Flanger. He also asks Andy all about the OBNE Custom Shop, currently live for the 2025 Black Friday shopping event.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!

In this episode, we sit down with Quincy Tennyson, who teaches an impressive four-year computer science pathway at Fern Creek High School. Quincy's background in the Marine Corps and as a network engineer brings a unique perspective to CS education. He discusses his curriculum progression from introductory courses through AP Computer Science Principles (heavily inspired by UC Berkeley's CS61A), AP Computer Science A (Java), and a culminating Project-Based Programming course. We dive deep into his philosophy of being a "warm demander" - setting high expectations while providing intensive coaching and support. The conversation touches on several compelling topics including teaching agile methodology to high school students, the importance of transparency about failure, and how behavioral economics concepts (from thinkers like Daniel Kahneman) inform his approach to helping students understand their own thinking processes. Quincy also shares insights on supporting underserved students, running a successful Girls Who Code chapter, and navigating the integration of AI tools in the classroom. His students' enthusiasm at PyCon 2024 was infectious, and this episode reveals the thoughtful pedagogy behind their success. Key resources mentioned include CS61A from UC Berkeley (https://cs61a.org/), CodeHS (https://codehs.com/), Code.org (https://code.org/), Sandra McGuire's book "Teach Students How to Learn," Eric Matthes' Python Crash Course (https://nostarch.com/python-crash-course-3rd-edition), and Al Sweigart's (https://alsweigart.com/) educational resources including his new Buttonpad library for Tkinter. Special Guest: Quincy Tennyson.

golang.org/x/crypto v0.45.0 released

In today's episode, two people who barely understand modular synth discuss modular synth! Dan recently got himself a Pittsburgh Modular Taiga Keyboard, and is in the discovery stage of a potential journey with analog synthesis. Our hosts talk happy accidents, ephemera-inspiring workflows, and when and why you should read the manual!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!

     What if you could transform the future of military medicine with the power of AI and technology? Join us for a captivating conversation with retired Navy Master Chief and Independent Duty Corpsman Joe Espinosa, who takes us through his remarkable journey in military healthcare. From his early days navigating the austere environments with the 2nd Battalion, 1st Marines, to becoming a strategic leader shaping the hospital corps, Joe offers invaluable lessons on adaptability, preparation, and the critical balance between clinical confidence and humility.      Listen as Master Chief Espinosa shares his pivotal experiences on smaller Navy ships and the USS Stockdale, where he honed skills in resource management and prioritization—an essential foundation for his role as Force Medical Master Chief. His insights into leadership are enriched by real-world frontline experiences, underscoring the vitality of robust support systems for those serving in combat zones. A decisive encounter with a Master Chief mentor propelled Joe into a leadership role, ultimately guiding the strategic direction of the corpsman community and championing the integration of healthcare technology with T6 Health Systems.     Explore the future of military healthcare as Joe discusses the integration of AI and predictive logistics to enhance decision-making and improve survivability in the most critical situations. Delve into the innovative developments aiming to address communication challenges in deployed healthcare systems and the seamless integration of technologies like MHS Genesis. With an emphasis on how emerging tools can support the military's medical personnel, this episode serves as a beacon for understanding the evolving landscape of military medicine and the pivotal role technology plays in shaping its future.   Chapters: (00:04) Master Chief Espinosa's Path in Military Medicine (11:58) Healthcare Leadership and Strategic Planning (20:58) Transition and Future of Military Medicine (29:51) Future of Military Healthcare Communication (35:41) Software Development and Military Healthcare (40:23) AI Integration in Military Healthcare (45:17) Future Developments and Challenges in Military Healthcare   Chapter Summaries: (00:04) Master Chief Espinosa's Path in Military Medicine    Retired Navy Master Chief Joe Espinosa shares his journey in military medicine, emphasizing mentorship and the need for innovation and technology.   (11:58) Healthcare Leadership and Strategic Planning    Transition from smaller to larger ships, managing medical supplies, frontline experiences, unexpected path to leadership.   (20:58) Transition and Future of Military Medicine     Enlisted voices shape military medical systems and face challenges transitioning to civilian life, but can use leadership skills in new roles.   (29:51) Future of Military Healthcare Communication    Improving communication in deployed military healthcare systems with bi-directional feedback and innovative solutions like animated QR codes.   (35:41) Software Development and Military Healthcare     MHS Genesis integrates with other systems, ensuring seamless transfer of healthcare records for veterans in military and VA services.   (40:23) AI Integration in Military Healthcare     Technology and healthcare intersect in military and civilian settings, with AI and wearables aiding decision-making for medical personnel.   (45:17) Future Developments in Military Healthcare     The role of technology in healthcare, predictive logistics for medical supply management, and transitioning from military to civilian healthcare technology.   Balancing functionality and resource efficiency in military healthcare through agile development and user feedback.   Take Home Messages: Intersection of Military Medicine and Technology: The episode explores the transformative impact of technology on military medicine, highlighting how advancements like AI and predictive logistics are revolutionizing communication and decision-making in challenging environments. This integration empowers medical personnel, especially junior corpsmen, to enhance their clinical decision-making and improve patient outcomes. Mentorship and Leadership Development: Emphasizing the importance of mentorship, the episode discusses how strategic planning and resource management are vital for effective healthcare leadership. Experiences from frontline medical roles significantly shape leaders, underscoring the need for adaptability and open communication within the military healthcare system. Navigating Career Transitions: Transitioning from a military to a civilian career can be challenging. The episode offers insights into recognizing the value of leadership and problem-solving skills gained in the military and encourages an open-minded approach to exploring diverse career opportunities beyond traditional paths. Improving Healthcare Communication: Addressing longstanding communication challenges in deployed settings, the episode discusses innovative solutions like bi-directional communication systems and animated QR codes that ensure seamless information transfer, enhancing the overall experience for medical personnel and patients in disconnected environments. Future of Military Healthcare: The episode envisions a future where technology, including mobile devices and AI, plays a crucial role in healthcare delivery. It discusses the potential for real-time data capture and analysis to alleviate cognitive burdens on healthcare providers, fostering confidence and improving decision-making in critical situations. Episode Keywords: Military medicine, healthcare innovation, AI integration, Joe Espinosa, War Docs podcast, frontline experiences, medical leadership, T6 Health Systems, predictive logistics, healthcare technology, Navy Master Chief, mentorship in healthcare, medical department setup, medical resource management, communication in healthcare, AI in military medicine, clinical decision support, military healthcare systems, medical mentorship, operational medicine Hashtags: #MilitaryMedicine #AIinHealthcare #HealthcareInnovation #FrontlineMedicine #JoeEspinosa #MentorshipInMedicine #WarDocsPodcast #PredictiveLogistics #MedicalLeadership #HealthcareTechnology   **This Episode was supported by an Educational Grant from one of our WarDocs Sponsors- T6 Health Systems**   Honoring the Legacy and Preserving the History of Military Medicine The WarDocs Mission is to honor the legacy, preserve the oral history, and showcase career opportunities, unique expeditionary experiences, and achievements of Military Medicine. We foster patriotism and pride in Who we are, What we do, and, most importantly, How we serve Our Patients, the DoD, and Our Nation.   Find out more and join Team WarDocs at https://www.wardocspodcast.com/ Check our list of previous guest episodes at https://www.wardocspodcast.com/our-guests Subscribe and Like our Videos on our YouTube Channel: https://www.youtube.com/@wardocspodcast Listen to the “What We Are For” Episode 47. https://bit.ly/3r87Afm   WarDocs- The Military Medicine Podcast is a Non-Profit, Tax-exempt-501(c)(3) Veteran Run Organization run by volunteers. All donations are tax-deductible and go to honoring and preserving the history, experiences, successes, and lessons learned in Military Medicine. A tax receipt will be sent to you. WARDOCS documents the experiences, contributions, and innovations of all military medicine Services, ranks, and Corps who are affectionately called "Docs" as a sign of respect, trust, and confidence on and off the battlefield,demonstrating dedication to the medical care of fellow comrades in arms.     Follow Us on Social Media Twitter: @wardocspodcast Facebook: WarDocs Podcast Instagram: @wardocspodcast LinkedIn: WarDocs-The Military Medicine Podcast YouTube Channel: https://www.youtube.com/@wardocspodcast

What is "spec-driven development," and why is this structured approach the key to unlocking complex AI projects? We're joined by Amit Patel, Director of Software Development for Kiro at AWS, to explore this methodology. He explains why "vibe coding" in a chat window fails on multi-day initiatives: the AI (and the developer) loses context. Kiro solves this by turning requirements and design into a persistent, structured spec that acts as the agent's long-term memory, enabling it to maintain context and build sophisticated applications.Amit shares the inside story of how his team at AWS built Kiro from scratch in under a year. He reveals their virtuous feedback loop with internal developers testing nightly builds and providing real-time feedback. This rapid iteration, which included six full revs of the spec experience, was so successful that the Kiro team famously "used the tool to build the tool," turning a multi-week feature into a two-day task. LinearB: Your AI productivity journey starts hereFollow the show:Subscribe to our Substack Follow us on LinkedInSubscribe to our YouTube ChannelLeave us a ReviewFollow the hosts:Follow AndrewFollow BenFollow DanFollow today's guest(s):Learn more and try Kiro: kiro.devJoin the Kiro Community: Kiro Discord Channel OFFERS Start Free Trial: Get started with LinearB's AI productivity platform for free. Book a Demo: Learn how you can ship faster, improve DevEx, and lead with confidence in the AI era. LEARN ABOUT LINEARB AI Code Reviews: Automate reviews to catch bugs, security risks, and performance issues before they hit production. AI & Productivity Insights: Go beyond DORA with AI-powered recommendations and dashboards to measure and improve performance. AI-Powered Workflow Automations: Use AI-generated PR descriptions, smart routing, and other automations to reduce developer toil. MCP Server: Interact with your engineering data using natural language to build custom reports and get answers on the fly.

Optimizing Software Development in Non-Tech Enterprises: Lessons from Nate Amidon of Form100 ConsultingIn this episode, host Josh Elledge interviews Nate Amidon, Founder and CEO of Form100 Consulting and Lieutenant Colonel in the Air Force Reserves. Nate shares how his background in both military leadership and enterprise consulting informs his approach to optimizing software development in non-tech organizations. From process mapping to team structure, he offers practical strategies for business leaders looking to improve efficiency, clarity, and scalability in their software operations.Optimizing Software in Non-Tech EnvironmentsNate explains that many organizations—manufacturers, service providers, and consumer brands—struggle with software development because it's not their core business. These companies often lack visibility into progress, rely on legacy processes, and face alignment issues across teams. His firm, Form100 Consulting, helps such enterprises identify bottlenecks, streamline workflows, and adopt lean, agile, and AI-driven practices that improve delivery speed without sacrificing quality.By mapping out the current workflow, teams can uncover where time and resources are being lost. Nate emphasizes focusing on the true constraint rather than over-optimizing non-critical steps. He also warns against chasing “shiny object” tools or AI solutions that don't solve the underlying process issues. Instead, organizations should apply AI incrementally to enhance existing systems.Drawing from his Air Force experience, Nate advocates for small, mission-focused teams—6 to 9 people—that communicate effectively and make decisions quickly. He stresses that sustainable improvement requires governance, ownership, and regular review. Ultimately, success comes from aligning teams, measuring progress, and committing to continuous improvement—much like in a high-performing military unit.About Nate AmidonNate Amidon is the Founder and CEO of Form100 Consulting, a firm that helps non-software-first enterprises optimize their software development processes. A Lieutenant Colonel in the U.S. Air Force Reserves, Nate combines military leadership principles with enterprise strategy to help teams increase alignment, efficiency, and long-term performance.About Form100 ConsultingForm100 Consulting partners with major enterprises—including Hershey, Boeing, Rite Aid, and Alaska Airlines—to modernize software development practices through process improvement, agile adoption, and data-driven transformation. The firm's mission is to bring structure, clarity, and sustainable efficiency to organizations where software is a critical enabler—not the core product.Links Mentioned in This EpisodeForm100 Consulting WebsiteNate Amidon LinkedIn ProfileKey Episode HighlightsCommon software challenges in non-tech companiesHow to identify and fix bottlenecks in development workflowsThe value of lean and agile principles for non-software teamsIncremental, ROI-focused AI integrationBuilding and scaling small, high-performing teamsApplying military leadership lessons to software developmentConclusionNate Amidon's insights bridge the gap between military precision and corporate innovation. By mapping processes, focusing on constraints, and scaling teams thoughtfully, businesses can transform software development from a bottleneck into a competitive advantage. His pragmatic, data-driven approach helps leaders cut through...