エピソード

  • 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 分
  • How Slack Survived the API Crisis

    How Slack Survived the API Crisis
    2026/09/07
    In 2017, Slack faced an existential threat when its third-party app ecosystem collapsed under its own weight. Apps were breaking constantly, permissions were a nightmare, and developers were fleeing to competitors like Microsoft Teams. We explore how Slack Engineering and Product teams pivoted from a chaotic, open-access model to a rigorous, curated platform strategy. This shift wasn't just about code; it was a fundamental rethinking of trust, security, and developer experience that saved the company's growth trajectory and set the standard for modern API governance. #Slack #APIEcosystem #PlatformStrategy #TechLeadership #DeveloperExperience #EngineeringCulture #BusinessResilience #SoftwareArchitecture #DigitalTransformation #SaaS #EnterpriseSoftware #ProductManagement #FexingoBusiness #BusinessPodcast #CTOPodcast #TechHistory #APIGovernance #StartupLessons Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How Datadog Scaled Engineering Without Burning Out

    How Datadog Scaled Engineering Without Burning Out
    2026/09/06
    Datadog’s rise to a fifty billion dollar valuation wasn’t just about product-market fit. It was about surviving hyper-growth without collapsing under its own weight. In this episode, we look at how their engineering leadership tackled the invisible crisis of developer burnout and architectural drift during their fastest expansion phase. We break down the specific structural changes they made to their CI/CD pipelines and team topology, moving from chaotic scaling to disciplined autonomy. The numbers are stark: doubling headcount while keeping deployment frequency stable requires more than just hiring faster. It demands a fundamental rethinking of how code moves through an organization. We examine the trade-offs between speed and stability that define modern technical leadership. #Datadog #EngineeringLeadership #TechDebt #DeveloperExperience #ScaleUp #CISOps #FexingoBusiness #BusinessPodcast #CTOPodcast #TechStrategy #DevOpsCulture #SystemDesign #OrganizationalScaling #CodeQuality #PlatformEngineering #GrowthStage #TechManagement #FutureOfWork Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    9 分
  • How Slack Scaled Engineering Without Adding Headcount

    How Slack Scaled Engineering Without Adding Headcount
    2026/09/05
    In this episode of The CTO Podcast, Lucas and Luna dissect how Slack managed to double its active user base while keeping its engineering team size remarkably flat. We explore the specific architectural decisions around serverless adoption, automated testing pipelines, and the controversial but effective 'you build it, you run it' culture shift that allowed them to maintain velocity without burning out their staff. This isn't just a story about hiring faster; it's a deep dive into the operational leverage required to scale technical output when human capital is the bottleneck. #SlackEngineering #ServerlessArchitecture #DevOpsCulture #TechnicalLeadership #ScaleUpStrategy #FexingoBusiness #BusinessPodcast #CTOPodcast #EngineeringManagement #AutomationFirst #CloudMigration #OperationalLeverage #TechDebtReduction #SaaSScaling #ProductivityMetrics #SoftwareArchitecture #TeamVelocity #CostEfficiency Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How Atlassian Tamed Technical Debt With Architecture Contracts

    How Atlassian Tamed Technical Debt With Architecture Contracts
    2026/09/04
    Atlassian shifted from reactive firefighting to proactive governance by introducing architecture contracts — lightweight, enforceable agreements between product teams and platform engineers. This episode explores how the company standardized API boundaries, reduced cross-team friction, and cut integration errors by half over eighteen months. We break down the mechanics of these contracts, why they work where strict mandates fail, and what other engineering leaders can learn from their approach to balancing autonomy with consistency in large-scale organizations. #TechnicalLeadership #EngineeringCulture #ArchitectureContracts #PlatformEngineering #DeveloperExperience #Atlassian #SystemDesign #APIGovernance #DevOps #TechDebt #SoftwareArchitecture #TeamAutonomy #EnterpriseSoftware #FexingoBusiness #BusinessPodcast #CTOPodcast #TechManagement #ScaleUp Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How Atlassian Tamed Technical Debt With Architecture Contracts

    How Atlassian Tamed Technical Debt With Architecture Contracts
    2026/09/03
    Technical debt isn't just bad code, it's a coordination failure. We examine how Atlassian built an internal platform called the Architecture Contract to enforce consistency across thousands of engineers. This system shifted the burden from individual teams to centralized governance, reducing cross-service latency and deployment failures by over thirty percent in two years. The approach raises questions about whether strict contracts stifle innovation or enable scale. We look at the tradeoffs between autonomy and standardization in large engineering organizations, using real data from their internal metrics and post-mortems. #FexingoBusiness #BusinessPodcast #TechLeadership #EngineeringOps #TechnicalDebt #ArchitectureContracts #Atlassian #PlatformEngineering #DevEx #SystemDesign #Scalability #Microservices #Governance #CodeQuality #EngineeringCulture #SoftwareArchitecture #TeamAutonomy #DeveloperExperience Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分