『The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org』のカバーアート

The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org

The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org

著者： Fexingo
無料で聴く

Lucas and Luna sit down in front of a whiteboard to dissect the decisions that shape technical organizations. Each episode of The CTO Podcast with Fexingo examines a specific engineering leadership challenge — from scaling a microservices architecture without creating a distributed monolith, to managing the cognitive load of a 200-engineer org, to choosing between a monorepo and polyrepo strategy based on team topology. The conversations are grounded in real-world cases: how Etsy restructured its data pipeline after a 2019 outage, why Stripe’s API versioning policy reduces breaking changes, or what Basecamp’s choice of SQLite over PostgreSQL says about product philosophy. Lucas brings the journalistic rigor — citing commit histories, RFCs, and postmortems — while Luna pushes back with the pragmatics of org dynamics, hiring constraints, and technical debt. There are no hot takes, no vendor pitches, no ‘best practices’ without trade-offs. Each episode ends with a specific tension left unresolved: the optimal number of direct reports for a VP of Engineering, the point at which a monolith should be broken apart, or whether a platform team should own the CI/CD pipeline. The listener is a senior engineer, a staff+ IC, or a new CTO who wants to learn from the decisions others have made — without the hype. After an episode, you’ll have a framework, not a checklist, and a clear sense of the questions you should be asking your own team. #CTOPodcast #TechnicalLeadership #EngineeringOrg #SoftwareArchitecture #SystemDesign #EngineeringManagement #Microservices #Monorepo #PlatformEngineering #Scalability #TechDebt #DevOps #Infrastructure #SiteReliability #DistributedSystems #Business #FexingoBusiness #Technology Keep every episode free: buymeacoffee.com/fexingo© 2026 Fexingo. All rights reserved. 経済学
エピソード
  • How Datadog Prevented AI Hallucinations in Production

    How Datadog Prevented AI Hallucinations in Production
    2026/09/10
    Datadog faces a unique challenge as AI models generate code and configurations at scale. How does the observability giant prevent its own tools from hallucinating critical infrastructure changes? We explore their shift from static validation to continuous runtime monitoring, the specific cost of false positives, and why human-in-the-loop reviews remain non-negotiable for safety-critical AI decisions. #Datadog #AIHallucination #LLMSafety #Observability #TechLeadership #EnterpriseAI #ModelOps #RuntimeSecurity #DevOpsCulture #EngineeringExcellence #FexingoBusiness #BusinessPodcast #TechnologyTrends #AIGovernance #CloudInfrastructure #SoftwareArchitecture #ProductSafety #DataPrivacy Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    12 分
  • How Netflix Solved The Last Mile Delivery Crisis

    How Netflix Solved The Last Mile Delivery Crisis
    2026/09/09
    In 2026, the biggest threat to digital platforms isn't algorithmic bias or server downtime—it is physical logistics. This episode examines how Netflix pivoted from pure streaming to a hybrid model involving physical merchandise and interactive experiences, forcing them to solve the last mile delivery problem for millions of subscribers. We explore the engineering challenges of integrating inventory management with real-time user data, the supply chain decisions that saved margins, and what other tech leaders can learn about bridging the gap between code and cardboard. #Netflix #Logistics #SupplyChain #LastMileDelivery #TechLeadership #BusinessStrategy #EngineeringOps #InventoryManagement #FexingoBusiness #BusinessPodcast #CTOPodcast #PhysicalDigital #ECommerceTech #OperationalExcellence #RetailInnovation #TechInfrastructure #MarketPivot #CustomerExperience Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    11 分
  • How GitHub Solved the Merge Conflict Crisis

    How GitHub Solved the Merge Conflict Crisis
    2026/09/08
    We drill into a specific, often-overlooked friction point in modern engineering: merge conflicts. While many teams focus on CI/CD pipelines or code review tools, few address the human and architectural reality of simultaneous changes. We examine how GitHub engineered their own workflow to reduce merge-related delays by forty-five percent using a combination of trunk-based development practices and automated conflict resolution scripts. Lucas breaks down the technical mechanics of how they decoupled feature branches from long-lived integration branches. Luna explores the cultural shift required to make this work, asking why most companies fail to adopt these patterns despite knowing the costs. We look at the specific metrics GitHub tracked, including developer cycle time and rollback frequency, to prove that reducing merge friction directly impacts shipping velocity. This is not just about better tools; it is about rethinking how we define 'done' in a collaborative environment. #GitHub #MergeConflicts #TrunkBasedDevelopment #EngineeringLeadership #DevOps #SoftwareArchitecture #CodeReview #CI-CD #FexingoBusiness #BusinessPodcast #TechLeadership #AgileMethodology #DeveloperExperience #VersionControl #GitWorkflow #ProductivityHacks #CTOPodcast #SystemDesign Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    9 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません