Discover
How Many CTOs
How Many CTOs
Author: Brad Hefta-Gaub & Scott Porad
Subscribed: 5Played: 22Subscribe
Share
© 2025
Description
Welcome to the "How Many CTOs?" Podcast, hosted by Brad and Scott, where we dive deep into the intricate world of Chief Technology Officers. Each episode features candid conversations with guest CTOs who share their real-world experiences and insights on a wide range of topics. From building and upleveling high-performing engineering teams to managing and communicating the impact of tech debt, we cover it all. Discover strategies for measuring engineering productivity, refining processes, and balancing innovation with structured methodologies. Learn from experts about decomposing monolithic systems and keeping up with the latest technology trends. Whether you're a current or aspiring CTO, our podcast offers practical solutions and valuable advice to navigate the ever-evolving landscape of technology leadership. Tune in and join the discussion on overcoming the common challenges faced by CTOs today. Don't forget to subscribe, rate, and review! #TechLeadership #CTO #techpodcast
95 Episodes
Reverse
In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub start the episode discussing "Reverse Engineer Anything," noting mixed results: an engineer got a good-looking clone of apps like Strava, but teardowns (including one of an alleged Adobe Suite copy) suggest it's closer to a clean-room spec-and-implementation that misses deeper functionality, serving mainly as a proof point that systems can write lots of code. They then shift to "software factories," describing internal agent-driven SDLCs and dashboards that resemble Kanban boards, tracking ticket status, assigned agents, token usage, and cost. They debate whether teams should build or buy such factory UIs, why no clear market leader has emerged, and whether chat-based interfaces or Kanban-style visuals are the right control plane—especially as agent scale may break familiar tools like Git and traditional roll-up reporting. 00:00 Cold Open Preview 00:18 Podcast Intro 01:06 Reverse Engineering Examples 05:53 Clean Room Explained 07:48 Why It Matters 08:23 Software Factory Dashboards 10:27 Build Or Buy Debate 17:05 Viral Factory Rig 20:00 Personalized IDE Analogy 22:10 When Git Stops Scaling 26:13 CTO View Across Teams 28:11 Work Units And Abstraction 30:03 Chief Of Staff Agents 32:43 Chat As The Dashboard 35:34 Visual Learners Want Diagrams 39:05 Listener Shoutouts And Wrap 40:28 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 continue to recap Gergely Orosz's "State of the Tech Industry" talk and focus on what "broke" and "what's next." They argue that machine-generated code is overwhelming pull requests and code review, exposing that many organizations' quality gates were implicitly built around human speed, and they discuss how 98% uptime is becoming an unacceptable norm. They connect this to the need for an "AI coding safety layer" of guardrails, static analysis, verification, and testing, while noting the challenge of convincing stakeholders to invest in quality. They explore workforce morale and fatigue driven by rapid change, heightened expectations, more incidents, job instability, and a less gratifying shift from hands-on coding to supervising agents and systems. They conclude that computer science and cross-disciplinary learning remain valuable and that turmoil creates opportunity, especially for younger engineers. 00:00 Cold Open 01:22 Ski Talk Banter 02:57 Recap Pragmatic Engineer 05:10 Guardrails Are The New Craft 09:45 Selling Quality Investment 14:43 Morale Fatigue Causes 17:14 Incidents And Reliability 18:47 Job Aesthetics Changing 19:23 From Coding to Orchestration 21:26 Chihuly Visionary Analogy 23:41 Will Education Adapt 28:06 Liberal Arts and Curiosity 30:05 Bootcamps vs Core Skills 32:58 Systems Research Path 35:21 Opportunity in Turmoil 35:52 Credits 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 #IndustryChange #IndustryTrends #IndustryEvolution #WorkforceTrends #LeadershipInTech #FutureOfWork
In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss a Pragmatic Engineer talk on the state of the tech industry in 2026, focusing on what changed and what hasn't. They argue this is a "golden age" of building software due to AI, while acknowledging current "creative destruction" that may ultimately make the industry leaner. Key changes include agentic software factories where people increasingly don't read code, and a shift toward open-weight models for cost and data-sovereignty reasons, including local/on-prem inference. They note core software fundamentals (system design, resilience, security, validation) and organizational friction (alignment, clear requirements) remain unchanged. They also explore remote work's evolution, speculate about smaller squads and team structures, and end by deferring "what broke" and "what's next" to a future episode. 00:00 Episode Teaser 00:26 Show Intro and Banter 01:28 Time Travel and Quantum Aside 02:49 Was Tech Better Five Years Ago 04:47 AI Tools Golden Age 06:53 Creative Destruction Now 07:59 Reverse Engineer Anything Debate 11:03 Remote Work Then And Now 13:31 Pragmatic Engineer Summary Setup 14:50 Agentic Factories and Open Models 17:47 Open Weights Local Inference 24:14 What Has Not Changed 26:19 Org Structure And Smaller Teams 31:47 Wrap Up and Next Episode Preview 32:24 Credits 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 #TechIndustry #AgenticSoftware #QuantumMechanics #RemoteWork #SystemDesign #OrganizationalFriction #CreativeDestruction #FutureOfTech
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



