In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub welcome guest John Helm to discuss the complexities and ramifications of technical debt within software projects. The conversation explores various analogies, including financial bonds and naked calls, to explain the impact of technical debt on project timelines and functionality. John offers insights on measuring technical debt, its human aspects, and strategies for managing complexity in software systems. The episode highlights the importance of defining technical debt, communicating its impact to business stakeholders, and finding a balance in software development to avoid costly delays and incomplete features.
Resources:
#TechPodcast #EngineeringPodcast #PodcastForDevs #HowManyCtos #Podcast
#Ctos #TechnicalDebt #TechDebt #MeasuringTechDebt #SoftwareArchitecture
#EngineeringLeadership #CtoPodcast #PlatformEngineering #SoftwareMaintenance
#Refactoring #LegacyCode #HumanFactors #BehavioralEconomics #DecisionMaking
#StakeholderCommunication #RiskManagement #OriginalMistakes #SecondSystemEffect
#BondModel #NakedCalls #TechnicalBankruptcy #EngineeringProductivity
#TeamHealth #SpaceMetrics #DoraMetrics #ContinuousImprovement #DeferredMaintenance