Advertise on podcast: How Many CTOs

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub interview software pioneer Kent Beck about his background (JUnit, test-driven development, extreme programming, Agile Manifesto, and his book "Tidy First?") and his current focus on "augmented development" with AI, which he calls a "genie." Beck argues that while AI shortens the build–feedback loop, it can also remove productive struggle that builds competence, agency, and flow, leaving developers exhausted and hollow. He critiques the "agent" metaphor, long tool latencies, and productivity measured as more code, proposing tools optimized for sub-second feedback, smaller safe increments, and even pushing changes to production thousands of times a day. Beck predicts programming demand will rise (Jevons Paradox), but warns mid-level "paycheck" developers must adapt. He advises leaders to use the tools themselves, build trust, and adopt via the technology adoption curve rather than mandates and layoffs. 00:00 Cold Open 00:22 Meet Kent Beck 04:31 Early Computing Origins 07:49 XP and AI Shift 11:29 Augmented Development Feel 13:06 Struggle Builds Competence 17:18 Beyond Agents Metaphor 20:39 Toil Versus Struggle 25:03 Flow and Feedback Loops 27:38 Amanuensis Junior Programmer 29:52 Manager Mode Reality 32:54 Optimize for One Second 36:35 Tech Cycles And Humans 41:01 Jobs And Jevons Paradox 46:56 Rethinking Productivity 52:15 Limbo Micro Deployments 56:01 Tool Seeds Sharing 59:34 Debugger Joy And TDD 01:02:19 Leading Adoption With Trust 01:08:57 Wrap Up And Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Kent Beck: https://kentbeck.com/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #AIRevolution #ExtremeProgramming #AgileManifesto #KentBeck #TechPioneers #FutureOfCoding #AIConversations #CodingCommunity #AIChallenges #HumanSideOfTech

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss TaskRabbit's overnight AWS region migration from us-west-1 to us-west-2, describing the months of preparation, detailed runbook, large war-room call, minor cleanup issues, and why periodic region moves can serve as valuable "hygiene" to relearn and document complex systems while advancing disaster recovery and business continuity. They then explain tabletop exercises as structured incident-response drills designed to uncover gaps in process and documentation, sharing scenario ideas like data deletion, token leaks, cloud outages, ransomware, and internal actors, including an embezzlement case where the perpetrator joined incident response. The conversation touches on an alleged AI sandbox escape involving Hugging Face, then debates claims that "unit tests are dead," arguing AI makes end-to-end testing easier but unit, integration, contract, and mutation testing remain important—especially for edge cases and dependency failures—and that agents can now generate extensive test coverage.   00:00 Cold Open Banter 00:35 Light Bulb Struggles 01:12 TaskRabbit Region Move 05:23 Tabletop Exercises Explained 10:06 Designing Scenarios 13:37 Insider Threat Tabletop 16:51 AI Sandbox Escape Story 21:19 Unit Tests Are Dead 25:16 Why E2E Misses Edge Cases 28:30 Mutation Testing Explained 31:25 Integration Tests Basics 33:23 Contract and API Testing 38:27 Third Party Outage Example 41:55 Golden Age of Validation 43:59 Wrap Up and Credits   Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/ Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/   #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #AWS #AWSMigration #DisasterRecovery #TabletopDrills #TabletopExercises #UnitTesting #EndToEndTesting #APITesting #Microservices #IncidentResponse #UnitTestsAreDead #UnitTestsAren'tDead #TestingStrategies #AIStories

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss growing fear about AI among engineers and managers, framing it as an "adaptive moment" requiring leaders to disrupt old stabilizing practices. They explore concerns that AI lowers the barrier for others to change systems, increasing accountability, on-call risk, and architectural drift—problems that existed pre-AI but are now intensified. Their proposed response is to strengthen the software factory/SDLC with non-human, deterministic guardrails: robust automated tests, CI/CD quality gates, mutation testing, and better observability, rather than human gatekeeping or fiefdoms. They share examples of risky AI agent behavior (attempting to access credentials to reorder Jira tickets) and real-world harm from AI claim adjudication pilots, concluding that best practices are now the floor and that engineers who build quality gates become more valuable. 00:00 Cold Open 01:04 AI Fear in Engineering 02:00 Adaptive Leadership Moment 03:55 Software Factory Mindset 06:10 Fear of Accountability 08:09 Old Problem New Pressure 11:58 Non Human Quality Gates 13:41 Scaling Creates Fiefdoms 16:34 Architecture Agent Example 20:26 Apocolyptic AI Concerns 23:51 AI in Medicare Risks 32:29 Best Practices Are Floor 33:41 Wrap Up and Subscribe Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #SoftwareFactory #AIChallenges #EngineeringManagement #AdaptiveLeadership #QualityGates #TechTalkingPoints #InnovationStrategy #LeadershipInsights #TechInnovation #AIThreat #AIFear #AIInTech

In this episode of "How Many CTOs Does It Take?" podcast, host Brad Hefta-Gaub is joined by guest Frank Bravo, a Bay Area technologist who spent 30 years as CTO in local media, helping put a newspaper's full editorial content online in 1994, and now serves as CTO at ProLegal, a legal services startup. Frank describes modernizing an old Act! database into a custom CRM, launching ProLegal Suite, and building systems that integrate with Uber and Lyft to schedule client rides on a lien. He explains how ProLegal uses AI to analyze case documents and train models on company-specific context, while keeping humans in the loop and reviewing AI-generated code. The conversation focuses on simplifying technology for non-technical users, the importance of shared terminology, troubleshooting and telemetry, and advice for CTOs on communicating clearly without acronyms.   00:00 Cold Open 00:41 Meet Frank Bravo 01:28 From Newsrooms to Startups 05:01 Building ProLegal Tech 08:18 AI in Legal Funding 12:04 Translating Tech for Humans 17:34 Choosing the Right Solution 18:41 Picking Podcast Topics with AI 21:58 Trust and Tech Backlash 26:01 How Fast Tech Changed 28:09 Phones as Invisible Tech 29:30 Wi-Fi vs Internet Confusion 32:30 Wired Beats Wireless 33:13 Buffering and Brand Names 34:33 Explaining Tech Simply 38:28 Empathy Through Support 41:49 AI as a Thought Partner 43:35 Telemetry for Troubleshooting 46:21 Career Through Line 48:50 Where to Find Frank 49:39 Show Credits and Outro Resources: How Many CTOs Pod: https://howmanyctospod.com Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Frank Bravo: https://www.linkedin.com/in/fabravo/  Your Tech Makeover Podcast: https://www.yourtechmakeover.com/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #LegalTech #TechSimplified #AIInsights #ProLegal #InnovativeTech #BridgingTech #FrankBravo #Telemetry #TechBacklash #Trust #Troubleshooting

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss how AI is changing software engineering referencing Kent Beck's idea that AI makes much existing knowledge less useful while making a smaller portion far more valuable. They describe teams collaborating through "cohorts" of AI agents for PR review and adversarial checking, and debate whether engineers will be evaluated on agent quality versus their ability to direct and manage agents like a driver or jockey. Scott shares TaskRabbit's approach to shifting from organic AI adoption to "systemic usage" using an AI maturity matrix, gap analysis, and incremental rollout of agents (code review, security, architecture) with a six-week versioned cadence to help the whole organization keep up. They address skepticism, incentives in for-profit organizations, and the rapid pace of AI tooling innovation.   00:00 Cold Open 00:28 Podcast Kickoff 01:22 Uncle Bob Clip Reactions 02:16 Kent Beck Tease 03:39 Engineers With Agent Teams 05:19 Prompting vs Building Agents 10:16 Managing Agents Like Juniors 13:08 Handling AI Holdouts 17:20 Why Build Beats Craft 19:26 Software as Puzzle Pieces 21:38 TaskRabbit AI Maturity Plan 23:56 From Organic to Systemic 26:19 Six Week Change Cadence 27:11 Handling Corporate Agenda Fears 29:02 Why AI Becomes Inevitable 33:28 Leading With Growth Mindset 35:29 Imperfect Tools Fair Comparisons 38:54 Innovation Pace And Morale 42:34 Dark Factory And SDLC Evolution 47:12 Outages CD ROMs And Wrap Up 49:25 Closing Credits   Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub interview Scott Hanson, founder and CTO of Ambiq, a company focused on ultra-low-power chips for "intelligence everywhere," with 300M+ units shipped into wearables and other devices. Hansen traces Ambiq's origins with University of Michigan smart-dust research and his PhD work on subthreshold computing—running transistors at extremely low voltages for quadratic energy savings—then explains the challenges of making it manufacturable across temperature and process variation. He discusses university IP spinout mechanics, patent timing vs. publication, and his transition from founder CEO to CTO under a professional CEO. The conversation covers Ambiq's Apollo SoCs and the newer Apollo "Atomic" NPU direction enabling much larger edge AI models, new memory innovations, and future camera and conversational-interface use cases, plus hardware development realities like long feedback loops, simulation/FPGA prototyping, and high mask/tooling costs. 00:00 Cold Open 00:19 Meet Ambiq And The Guest 02:25 Smart Dust Origins At Michigan 03:21 Subthreshold Computing Explained 04:53 From Lab Demo To Manufacturable 06:05 Bio Inspired Power Ideas 08:25 Choosing EE And Finding The Path 10:42 Deciding To Commercialize 13:30 University Spinout And IP Deals 16:35 Papers Versus Patents Strategy 19:06 Founder CEO To CTO Transition 22:30 CTO CEO Partnership 23:49 Ego Shift Support 24:42 Apollo Atomic Overview 27:25 Edge AI Use Cases 29:49 On Device Translation 32:43 Memory Bandwidth Bottlenecks 37:21 Hardware Leadership Tech Debt 40:15 Testing With FPGAs 42:54 Cost Of Chip Tooling 44:33 Wrap Up and Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Scott Hanson: https://www.linkedin.com/in/scott-hanson-82707b7/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #TechInnovation #EnergyEfficient #SiliconChips #SmartWearables #CEOtoCTO #Ambiq #LowPower #EdgeComputing #ElectronicsEngineering #SmartDevices #EdgeAI #SubthresholdComputing #HardwareInnovation #NeuralProcessing #WearTech

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub interview Andy Boettcher, Chief Innovator of DoubleTrack, a boutique data and AI consultancy. Andy recounts his 33 years across systems, development, with 13 years in Salesforce, and how his career shifted into data/AI full-time after ChatGPT's 2022 release. The group compares manufacturing's precise cost estimation to software's people-driven unpredictability, then explores moving beyond AI for cost takeout toward top-line revenue lifts. Andy emphasizes mindset—curiosity, open-ended questions, and "always assuming you're wrong"—and argues resistant engineers will be replaced by those using AI. They discuss using AI as a peer, agentic workflows, real-time CX intelligence for renewals/upsell, ethics, and the need for human-in-the-middle quality gates, scoring rubrics, and trustworthy PR artifacts. 00:00 Cold Open 00:18 Meet the Guest Andy 02:15 Micro Estimating Story 04:17 Why Software Estimates Fail 05:55 DoubleTrack and AI Work 08:15 Revenue vs Cost Takeout 10:39 AI as Peer Partner 13:35 Curiosity New Mindset 17:30 Learning to Prompt Better 20:49 Agents and Orchestration 23:05 Managing Teams of Agents 25:09 Real Time CX Signals 27:09 Scraping The Corners 29:07 Ethics Of Live Upsell 30:17 Async Agents In Practice 34:47 Trust And AI Slop 40:29 Agent Driven Code Reviews 44:52 Rubrics And Quality Gates 48:24 Final Advice And Wrap Up Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Andy Boettcher: https://www.linkedin.com/in/andyboettcher/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #Innovation #Data #RevenueGeneration #MachineLearning #BusinessStrategy #DataAnalytics #BusinessGrowth

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub interview Jack Moldave of Eyebot, a company he co-founded nearly six years ago to make getting glasses as easy as buying shoes by enabling on-demand vision tests and prescriptions in retail settings. Jack explains Eyebot's kiosk experience in Walmart Vision Centers, including intake questions, visual acuity testing, touch-free refraction and glasses scanning, and remote review by licensed optometrists/ophthalmologists with prescriptions returned in under 15 minutes. He discusses navigating FDA regulation as a Class I medical device using risk assessment (FMEA), a quality management system, and traceability, and shares why venture capital helped fund regulated hardware R&D. The conversation also covers Eyebot's doctor portal and network, limits versus comprehensive eye exams, potential future screening as a Class II device, and the challenges and culture required to merge hardware and software development with over-the-air updates and manufacturing partners. 00:00 Podcast Cold Open 00:51 Eyebot Mission 02:04 Founders and Origin 04:43 Access Stories 07:19 FDA Basics 10:30 FMEA Risk Analysis 13:17 Quality Systems 15:43 Funding Realities 16:53 Walmart Kiosk Flow 20:29 Touch Free Design 23:50 Remote Doctor Network 26:57 When to Refer Out 27:48 Minotaur Care Model 28:48 Doctor Shortage Solution 33:38 Hardware Software Moat 35:05 Formlabs Playbook 38:46 Leasing and Upgrades 40:11 First Launch with Walmart 48:35 Suppliers and Scaling 49:52 Culture and Closing 51:53 Outro and Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Jack Moldave: https://www.linkedin.com/in/jackmoldave/ Eyebot: https://www.eyebot.co/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #VisionCare #Innovation #MedicalDevice #Eyebot #EngineeringExcellence #HardwareDevelopment #SoftwareIntegration #DigitalHealth #FutureOfHealth #RegulatoryChallenges #EngineerSpeak #TechSolutions #MedTech #HealthcareInnovation #VisionCareAccess #MedDevice #SoftwareHardwareBlend

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss a leadership conversation where three senior stakeholders wanted different outcomes from engineering: delivering faster, maximizing utilization, or delivering on time—highlighting unclear norms and expectations in the software delivery system. The hosts argue you can't optimize all three at once, note that maximum utilization is a poor goal (systems perform better below 100% utilization), and debate prioritizing speed versus schedule. Scott favors being on time with about 80% accuracy to avoid sandbagging and support business dependencies like launches, while Brad generally prioritizes going fast, especially in early-stage or learning-focused contexts, with "within reason" expectations. They add an unspoken distinction between innovation organizations and manufacturing organizations, and observe that projects often go off schedule due to unclear requirements, shifting scope, or faulty early assumptions. 00:00 Cold Open 01:04 Velocity Tradeoffs Debate 03:07 On Time 80 Percent Rule 03:56 Innovation Versus Manufacturing 05:03 Why Utilization Misleads 06:43 Stage Dependent Speed 09:32 Quality And Launch Systems 11:56 One Project Always Late 12:51 Why Projects Derail 14:41 Front Load The Hard Parts 15:50 Wrap Up And Outro Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #Velocity #Productivity #Utility #ResourceManagement #GoFast #GoFastBreakThings #ProductManagement #SpeedVsAccuracy #InnovationCulture #Innovation #EfficientTeam #Efficiency

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub open with travel and sports talk, including World Cup rules, then pivot to Scott's change-management training on systems thinking and unspoken norms. They explore a meta-question: if non-engineering teams couldn't tell engineering to "go faster," what would they change to increase engineering throughput? Using AI as a lens, they argue the bottlenecks become: deciding what to build, keeping a prioritized "shovel-ready" backlog, and handling downstream constraints like training users, releases, and integrations. They emphasize learning feedback loops, including studying what went right, and discuss long-horizon thinking for durable platforms. The conversation touches on Spain's mail-based customer service requirement, balancing innovation vs basic fixes (TaskRabbit categories), intentional tech debt, and ideas from Eric Ries's book "Incorruptible," plus examples of enduring companies like Costco and century-long businesses. 00:00 Cold Open 00:31 Podcast Kickoff Banter 00:44 Mountain Adventure Recap 01:37 Sports Week Highlights 03:53 Change Management Systems 05:10 Elevator Norms and Rules 07:51 Meta Question On Speeding Up Engineering 09:56 Instant Code Bottlenecks 12:03 Shovel Ready Planning 14:29 Downstream Release Constraints 19:35 Build the Right Stuff 24:59 Learning Loops and Postmortems 28:01 Spain Side Quest 30:23 Stop Forcing Revenue Targets 34:01 Mission Metrics And 3M 39:42 Innovation Versus Basics 42:37 AI Changes Tech Debt Math 49:03 Think In Decades 53:38 Costco Mission And Hotdogs 56:00 Subscribe And Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #EngineeringInnovation #SystemsThinking #R&D #Innovation #ProductManagement #ResearchandDevelopment #BusinessStrategy

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss how CTOs must frame narratives that help teams organize around ideas, inspired by how Scott explained his company's AI work to a non-technical friend. The hosts outline four intertwined AI workstreams: getting AI to handle increasingly complex engineering (from functions to features to systems), moving toward autonomous "dark factory" software development, scaling AI adoption through standards and systems (shifting from organic experimentation to systemic usage, like AI code review and possible security/architect review agents), and managing token spend, including discussion of token-maxing incentives, looping, and interest in local inference and vendor lock-in mitigations such as AWS Bedrock. The episode also includes numerous anecdotes from the hosts engineering teams and time as parents. 00:00 Cold Open 00:45 Recharge Week Catchup 02:02 Sapiens and Storytelling 03:14 Cognitive Revolution Explained 05:11 AI Elevator Pitch At Baseball Game 06:42 Three AI Workstreams 10:35 Complex Engineering with AI 11:30 Building SaaS with Agents 13:05 Dark Factory Automation 14:30 Scaling Standards and Systems 17:41 Organic to Systemic Adoption 19:41 Scouts and Shared Conventions 20:49 Spec Driven Development Debate 21:33 Middle Ground of Feature Brief 23:31 Security and Architect Agents 25:02 Token Spike Story 28:42 The Innovation of Reuse 29:40 Token Management Debate 33:08 Looping Burns Tokens 35:09 Local Inference and Privacy 38:43 Vendor Lock In and Bedrock 41:58 CTO Narrative and Framework 44:32 Wrap Up and Credits   Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AIRevolution #Automation #TokenManagement #AIInnovation #ComplexEngineering #AIAdoption #FutureOfAI #TechEnthusiast #VendorLockIn #EngineeringExcellence #SoftwareStrategies #AIInsights #CTOCommunity #AIStandards #TechPodcast #EngineeringLeadership #OrganizationalChange #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub are honored to interview Robert "Uncle Bob" Martin, who recounts his 60+ year programming journey from a three-bit binary device and years of assembly to C, C++, and Java, to now using AI agents to code. He explains how the Agile movement emerged from the design patterns community, Extreme Programming, and the 2001 Snowbird meeting that produced the Agile Manifesto. He argues Agile arose as a response to failed upfront analysis/design and emphasizes feedback, small iterations, and early discovery of uncertainty, while noting Agile was later overtaken by project managers and certification-driven Scrum. Martin discusses the ongoing tension between business roadmaps and engineering uncertainty, advising ranges over firm dates, and connects Agile lessons to AI coding: neither big upfront specs nor "vibe coding" works without strong engineering disciplines enforced by deterministic tools (tests, static analysis, CRAP metric), enabling developers to step back from reading syntax while still guiding quality. The episode ends with a discussion on the future of training engineers and the possibility of an apprenticeship model of learning. 00:00 Cold Open 00:20 Meet Uncle Bob 01:24 First Computer Memories 03:19 From Assembly to C 05:04 Coding With AI Agents 07:00 How Agile Was Born 12:04 Why Waterfall Failed 19:01 Agile Gets Hijacked 21:23 Roadmaps vs Reality 26:21 Agile Lessons for AI 30:52 Agent Myopia Risks 31:40 Deterministic Tooling 32:48 CRAP Metric Whip 34:29 I Don't Read Code 38:14 Assembly to C Lessons 41:29 Abstraction History Repeats 43:14 AI Broke The Plateau 48:09 Agents In Practice 52:14 Quality Gates For All 56:03 Training New Engineers 58:26 Apprenticeship Model 01:00:38 Closing Thoughts Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Bob Martin: https://x.com/unclebobmartin Bob's book: Clean Agile: Back to Basics  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #Agile #UncleBob #AgileManifesto #AgileDevelopment #AIRevolution #FutureOfTech

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss how Robert "Uncle Bob" Martin—author of Clean Code and Agile Manifesto signer—sparked online controversy by saying he no longer reads the source code produced by his programming agents. They unpack his argument that strong "control systems" like automated unit and end-to-end tests, static analysis, and architecture acceptance criteria can replace line-by-line review, shifting human attention to higher-level architecture and justification. The hosts debate the limits of this approach in legacy systems lacking tests, explore how CTOs create quality through hiring and checks-and-balances, and emphasize spot-checking high-risk work such as one-way-door decisions, infrastructure migrations, data model design, and surprising estimates. They also consider building architecture/security agents and why Uncle Bob's opinions carry influence. 00:00 Podcast Kickoff 00:58 Who Is Uncle Bob 03:01 Agentic Coding Controversy 04:18 Quality Controls Over Reading 06:39 Legacy Code Testing Problem 09:49 Belligerents in the Debate 10:47 What Code Reviews Catch 12:31 Agents for Architecture Security 15:35 Multiple Reviewers Probability 17:41 CTO Checks and Balances 18:48 AWS Region Move Rollout Plan 20:27 Data Center War Stories 22:16 Reviews as Conversations 23:15 Beyond Reading Code 24:11 Presenting Upward Forces Clarity 25:44 CTO as Company Voice 27:49 Spot Checks and Breakpoints 29:11 When to Dive In 30:05 Data Intuition Stories 33:08 Debugging Big Estimates 36:08 Uncle Bob Agents 39:39 Why We Care 42:05 Wrap Up and Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssistedCoding #AIAssistedProgramming #AIProgramming #AICoding #UncleBob #Agile #AgileManifesto #CleanCode #AIAgents #CodingRevolution #AIinTech #LegacySystems #QualityControl #AgenticProgramming #EngineeringExcellence #TechDisruption #ProgrammingWisdom #AgilePrinciples #CodingGiants #TechEvolution #ModernEngineering

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss token spending and the "token maxing" backlash, sparked by a GitHub Copilot budget issue and broader industry moves to optimize tokens. The hosts argues companies should focus on value and learning rather than premature token optimization, while still adding circuit breakers to prevent runaway costs. They explore shifting to local inference and open-weight/open-source models for cost, privacy, and control, citing concerns about vendor policy changes like Fable's retention and classifier behavior. The conversation expands into how AI shifts bottlenecks from coding to product management, experiments pairing product and engineers using SpecKit, and how AI may realize Agile's iterative promise. They close on distribution as a key frontier and the career opportunity of being early in AI, likening it to the early internet era.   00:00 Cold Open 00:27 Podcast Kickoff 00:46 Anniversary Trip in Maui 02:54 Copilot Budget Surprise 05:15 Token Panic Backlash 07:54 Value Over Tokens 13:33 Local Models Rising 15:46 SaaS Apocalypse Talk 17:29 Cycle Time vs Value 20:19 SpecKit Pairing Experiment 22:43 AI Meets Agile Promise 24:50 Spec First Agile Debate 29:40 Builders VS Managers 31:40 Scaffolding Vibe Coders 32:29 Distribution Is Hard 35:51 Snoring App Niche 38:43 Targeted Ads Reality 40:07 Open Source Pushback 42:11 Three Pressures On CTOs 44:56 Privacy And Data Control 53:38 Frontier Models Trust Issues 56:19 Three Truths For Teams 58:09 Early Internet Lessons 59:44 Wrap Up And Credits   Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #Entrepreneurship #TokenMaxxing #LocalInference #AI #AIProgramming #AIAssistedProgramming Agile #Innovation #OpenSource #Privacy #OpenWeight #AIRevolution #Leadership #Innovation #AgileDevelopment

In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss how managing armies of coding agents can be physically draining, likening it to context switching in flat organizations. Scott references Yuval Harari's "Sapiens," connecting the cognitive and agricultural revolutions to modern pressures. The hosts debate whether AI causes coding skills to atrophy and blocks junior engineers from becoming seniors, framing "pulling the slot machine lever" as shipping code you don't understand. Brad shares a pre-AI story about copying Stack Overflow code for a 3D triangle point test, leading to lessons about ambiguity and understanding. They argue this cargo-cult behavior predates AI, though AI makes laziness easier, while curiousity can accelerate learning. They also discuss "taste" as effective engineering opinions, shifting skills toward interrogating LLMs, and a potential K-shaped industry split between WYSIWYG builders and engineers closer to the metal. 00:00 Cold Open 00:21 New Listener Surprise 01:36 Managing AI Agents Burnout 04:26 Sapiens and Cooperation 07:46 AI Complaints Are Engineering 08:49 Slot Machine Coding Metaphor 09:41 Stack Overflow Triangle Story 15:41 Cargo Culting and CopyPasta 16:30 Juniors to Seniors in AI Era 23:42 Curious vs Lazy AI Use 27:08 Models Improve and Safety 28:39 Engineering Is Shaping 29:58 Junior Vs Senior Judgment 31:03 What Is Taste 34:22 Engineering Job Shifts 37:25 Curiosity Still Wins 39:59 Build Stuff To Grow 44:04 Learning Through Debugging 46:25 Managing LLM Atrophy Risk 49:55 Pair Programming And Market Pressure 53:31 K Shaped Future 55:29 Wrap Up And Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #StackOverflow #CargoCulting #JuniorvsSeniorEngineers #JuniorEngineers #SeniorEngineers #AI #AIProgramming #AICoding #AIAssistedCoding #AIAssistedProgramming #SlotMachines #InnovationVsComplacency #ProgrammingLife #CodingChallenges #ArtificialIntelligence #LazyCoding #SoftwareSkills #AIInCoding #EngineeringChallenges #DeveloperJourney #InsideTech