Pioneer or Perish: How and When to Evolve Your Engineering Org Toward the AI Development Life Cycle

Pioneer or Perish: How and When to Evolve Your Engineering Org Toward the AI Development Life Cycle

In this episode of "How Many CTOs Does It Take?" [https://howmanyctospod.com/] podcast, hosts Scott Porad [https://www.linkedin.com/in/scottporad/] and Brad Hefta-Gaub [https://www.linkedin.com/in/bradheftagaub/] discuss a high-performing engineering team that has effectively cleared its product backlog while using AI heavily, including a senior engineer who surprised Brad by running agents overnight to automatically perform fast, high-quality GitHub PR code reviews via a webhook-driven harness. The engineer built an opinionated, RAG-backed "world-class code review" skill set that pulls new PRs from selected repos, reviews them with defined criteria, and posts comments, highlighting the need to articulate engineering judgment rather than relying on gut feel. They explore how models and agent frameworks are becoming commoditized, making the key differentiator the ability to assemble components and codify professional, reusable skills. The conversation turns to how teams should integrate AI into the SDLC, balancing experimentation with a shared, periodically updated "long-term support" approach and quality gates, plus examples like agents generating test coverage and proposing fixes for failing tests. 00:00 Cold OPen 00:25 Podcast Intro And Banter 01:09 Mind Blown By AI Team 03:25 Overnight Agent Code Reviews 06:02 Make Your Opinions Clear 09:05 Models Vs Frameworks 12:32 Standardizing Team AI Use 14:43 LTS For Agent Workflows 15:51 Automate Repeated Tasks 21:52 SDLC First AI Second 25:04 Quality Gates And Automation 28:27 Agents For Tests And Bugs 30:55 Future Of Engineering Taste 32:40 Wrap Up And Credits Resources: * How Many CTOs Pod: https://howmanyctospod.com [https://howmanyctospod.com] * Scott Porad: https://www.linkedin.com/in/scottporad/ [https://www.linkedin.com/in/scottporad/] * Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/ [https://www.linkedin.com/in/bradheftagaub/] #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #EngineeringExcellence #AIInnovation #TechInnovation #FutureOfWork #AIDriven #AIAssistedProgramming #AIAssistedCoding #AIProgramming #AICoding #SDLC #ADLC

Navigating the Future: Gas Town and Bespoke AI Agents

In this episode of "How Many CTOs Does It Take?" [https://howmanyctospod.com/] podcast, hosts Scott Porad [https://www.linkedin.com/in/scottporad/] and Brad Hefta-Gaub [https://www.linkedin.com/in/bradheftagaub/] discuss Brad's viral LinkedIn post arguing that AI has collapsed the economics that drove generalized SaaS, enabling more bespoke software for underserved SMBs and vertical niches. They debate practical examples like a plumber-specific CRM versus highly custom workflows for a regional law firm, including concerns about long-term maintenance, fragmentation, and risk. Brad contrasts "overnight magic" agent claims with what he sees in fractional CTO work: teams using AI within disciplined engineering practices and quality gates to deliver far more output, though not fully autonomous "dark factories" yet. They explore Scott's hands-on Gas Town workshop experience building a fantasy football app with multiple agents, noting orchestration value, tooling immaturity, resource constraints, and confusing nomenclature. The episode ends with why experienced operators still dismiss AI for production code and whether agent frameworks will be custom-built or marketplace-driven. 00:00 Cold Open 00:14 Show Intro and Hosts 00:58 Viral LinkedIn Post Read 03:28 "Agree... Sort Of" Nuance 04:40 Plumber CRM Example 08:36 Law Firm Workflow Doubts 11:37 Engineering Reality Check 14:29 Gas Town Workshop Demo 17:34 Factory Setup and Risks 20:28 Why Leaders Still Doubt AI 22:26 AI Naysayers 24:10 Massive PRs 27:42 Monorepo Momentum 29:07 Engineering Joy 31:10 AI Mistakes 33:19 Agent Personas 37:04 Agent Marketplace 38:54 K Shaped Future 41:15 Trust But Verify 42:30 Wrap Up Resources: * How Many CTOs Pod: https://howmanyctospod.com [https://howmanyctospod.com] * Scott Porad: https://www.linkedin.com/in/scottporad/ [https://www.linkedin.com/in/scottporad/] * Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/ [https://www.linkedin.com/in/bradheftagaub/] #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIRevolution #AIAgents #AIAssistedCoding #AIAssisstedProgramming #BespokeSoftware #GasTown #TechInnovation #FutureTech #DigitalTransformation #TechLeadership #CTOInsights #TechTrends

Uncovering Hidden Ambiguities: Why Product Managers Need to Adapt to AI Tooling

In this episode of "How Many CTOs Does It Take?" [https://howmanyctospod.com/] podcast, hosts Scott Porad [https://www.linkedin.com/in/scottporad/] and Brad Hefta-Gaub [https://www.linkedin.com/in/bradheftagaub/] discuss spec-driven development and SpecKit, starting with Brad's story of a product owner resisted SpecKit because it produced "too many words," alongside Scott's example of accepting a 60,000-line pull request by reviewing the spec instead of the code. They reflect on how product owners often can't define what they want until they see it, and how software work is usually clarified through ongoing back-and-forth dialogue. SpecKit surfaces hidden ambiguity by generating questions product owners hadn't considered, changing what used to become ad hoc decisions, bugs, or debt. They argue speed enables tighter iteration, but also pressures product to "know what they want," raising job-impact fears for engineers and possibly product managers too. Their conversation prompts ideas for training, collaborative workflows, and even self-design—tempered by the continued need for standardization and cross-functional expertise. The episode ends with the hosts reflecting on buisness ideas that never came to pass, and affirming that now value comes down to how well the problem can be described. 00:00 Cold Open 01:18 Product Is The Hard Part 02:26 Fast Teams Meet Specs 04:34 Too Many Words Pushback 05:10 Review The Spec Not Code 08:00 Coder To Reviewer Shift 10:20 Why POs Avoid Specificity 13:01 Surfacing Ambiguity Shock 17:43 Two Hour Sprint Loop 19:35 Jobs Changing Anxiety 23:39 Problem Versus Solution Trap 25:56 Vibe Tools And Self Design 26:49 Real Estate CRM Anecdote 28:28 AI Rewrites Software Economics 29:31 Self Design Simple Specs 31:00 When Standards Matter 32:23 Training Product Owners 36:05 Jobs Converge Under AI 37:49 Three Pane Spec IDE 40:40 AI Comes For PMs 44:29 Founder Moats And Copies 46:24 Missed Spotify Moment 48:19 RealNetworks Almost Made YouTube 51:36 Wrap Up And Credits Resources: * How Many CTOs Pod: https://howmanyctospod.com [https://howmanyctospod.com] * Scott Porad: https://www.linkedin.com/in/scottporad/ [https://www.linkedin.com/in/scottporad/] * Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/ [https://www.linkedin.com/in/bradheftagaub/] #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #SpecKit #SpecDrivenDevelopment #ProductManagement #AI #ProductOwners #CodeReview #QualityGates #IterativeProcess #UserStories #AIAssistedCoding #Spec

A Fundamental Shift: Change Management, Psychological Safety, and AI's Impact on Engineering Leadership with Dr. Adam Link

In this episode of "How Many CTOs Does It Take?" [https://howmanyctospod.com/] podcast, host Brad Hefta-Gaub [https://www.linkedin.com/in/bradheftagaub/] is joined by Dr. Adam Link, former senior engineering manager at Coinbase, who shares his background leading global teams through highly technical transformations in fintech and crypto, including major infrastructure migrations. They discuss whether different kinds of change require different leadership approaches, emphasizing that change management is fundamentally about people. They discuss how fear makes change harder, so leaders must create psychological safety by providing "air cover" and managing messaging up and down. Adam notes that good managers must handle hard conversations like layoffs and performance issues with empathy while recognizing these outcomes aren't always personal decisions. He offers advice for engineers moving into management, including a tongue-in-cheek analogy that managers "test in production," and describes a challenging EC2-to-Kubernetes migration where success required strong technical credibility, hands-on help, and attention to team psychology. Adam and Brad compare blameless vs egoless retrospectives, discuss leaders defending engineers behind the scenes, and highlight the need for real remediation like error budgets or vendor changes. The conversation closes on AI as a fundamental industry shift, debate over the loss of hand-crafted coding vs enduring need for problem understanding, concerns about the junior-to-senior pipeline if entry roles disappear, decision fatigue from AI agents, and optimism about smaller teams producing better products with fewer bugs. 00:00 Cold Open 00:31 Podcast Intro Guest 02:24 Change Management Basics 03:49 Defining "Air Cover" 06:50 Hard People Decisions 10:19 Managers Test In Prod 13:38 Big Cloud Migration 17:34 Hands On Migration Help 21:04 Failure Friendly Culture 23:41 Blameless vs Egoless Retros Debate 28:56 Managing Up After Outages 30:19 Accountability And Error Budgets 31:38 Vendor Failures And Remediation 33:53 AI Adoption And Resistance 34:44 Craft Versus Assembly Line 37:52 AI As Mid Level Engineer 41:17 Business Value For Juniors 45:11 Pipeline And Decision Fatigue 47:15 Specs Waterfall Meets Agile 49:07 Summary And Closing Thoughts Resources: * How Many CTOs Pod: https://howmanyctospod.com [https://howmanyctospod.com] * Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/https://www.linkedin.com/in/bradheftagaub/ [https://www.linkedin.com/in/bradheftagaub/] * Dr. Adam Link: https://www.linkedin.com/in/adamlink/ [https://www.linkedin.com/in/adamlink/] #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AIRevolution #EngineeringCulture #ChangeManagement #LeadershipSkills #AIAssistedProgramming #AI #FinTech #Crypto #

An Ideal Partnership: How and When to Split CTO and VP of Engineering Duties

In this episode of "How Many CTOs Does It Take?" [https://howmanyctospod.com/] podcast, hosts Scott Porad [https://www.linkedin.com/in/scottporad/] and Brad Hefta-Gaub [https://www.linkedin.com/in/bradheftagaub/] discuss the recurring question: when it's appropriate to hire a VP of Engineering and how to divide responsibilities so the CTO can better align product, business, and technology strategy. They define CTO vs VP of Engineering work, review Gemini's matrix (strategy/vision vs execution/people/process, external vs internal, success metrics, and typical direct reports), and add nuance about internal stakeholders within and outside the company. They discuss cases where leaders can't do both jobs and why founders shouldn't give the CTO title too early. They emphasize CTO/VPE as a yin-yang partnership with clear decision rights and KPIs. Brad shares experiences with split dev/ops teams and argues for engineers having operational skin in the game, while Scott outlines his org functions and defines ops as what's required to keep systems running. They propose carving up responsibilities by strategy vs building (and operating), debate punting corporate IT to the CFO versus keeping it tied to security, and consider using Gemini to suggest how to split roles. The episode closes on letting go of ego through clear expectations, Scott's recommendation of the book "First, Break All the Rules," how skill or interest gaps can force a split despite hierarchical titles, and a pro tip to align on expectations with your CEO so teams can measure progress and celebrate wins like uptime and cycle-time improvements. 00:00 Cold Open 00:27 Podcast Intro Banter 00:49 Small Business AI Win 02:09 Team Size Context 03:52 When to Add VPE 05:40 CTO vs VPE Roles 07:11 Gemini Comparison Matrix 10:54 Startup Hiring Patterns 13:39 Titles and Founder Pitfalls 15:18 Yin and Yang Partnership 18:09 Carving the Org Pie 20:31 Corporate IT and Security 24:20 Strategy Versus Execution 25:28 Reliability And SRE Ownership 27:24 Defining Operations Teams 30:04 On Call And Skin In Game 31:18 Using Gemini To Split Roles 33:08 Letting Go And Ego 34:33 KPIs Enable Delegation 37:28 Manager Clarity Framework 38:57 When Skill Gaps Force Split 41:55 Set Your Scorecard 44:16 Celebrate KPI Wins 45:51 Wrap Up And Credits Resources: * How Many CTOs Pod: https://howmanyctospod.com [https://howmanyctospod.com] * Scott Porad: https://www.linkedin.com/in/scottporad/ [https://www.linkedin.com/in/scottporad/] * Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/ [https://www.linkedin.com/in/bradheftagaub/] #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #VPofEngineering #Gemini #CTOvsVPE #VPE #SecurityMindset #AI #DevOps #GrowthMindset #TeamCollaboration #CorporateCulture #BusinessGrowth #AIIntegration #Operations #StrategicVision #ManagementStyles #RoleDivision #ExecutiveDecisions