Launching AI features is risky — one bad recommendation can erode user trust in minutes. In this episode, Lucas and Luna explore 'shadow mode', a deployment strategy where a new AI model runs in parallel to production, logging its decisions without affecting users. They walk through a concrete example from a mid-size fintech company that tested a fraud-detection upgrade this way, catching a 6% false-positive regression before going live. Along the way, they discuss trade-offs like infrastructure cost, latency simulation, and how to build an evaluation pipeline that gives CTOs confidence to pull the trigger. If you're an engineering leader responsible for AI product decisions, this is a practical look at a technique that sits between A/B testing and canary releases — and often gets overlooked.

#ShadowMode #AIDeployment #CTO #EngineeringLeadership #FraudDetection #Fintech #FeatureValidation #ProductionTesting #MLLogging #FalsePositive #ABTesting #CanaryRelease #EvaluationPipeline #RiskManagement #Infrastructure #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how forward-thinking CTOs design staff-plus engineering career ladders — tracks for senior individual contributors beyond the traditional management path. Drawing on real examples from companies like Spotify and GitHub, they unpack the 'Staff Engineer' archetype, how to define scope levels (from Staff to Principal to Distinguished), and why clear criteria for technical leadership prevent the 'manager-trap' brain drain. Lucas shares a concrete rubric: the four dimensions of impact — technical depth, mentorship, strategic influence, and organizational leverage — and how CTOs calibrate them for their context. They also discuss a common failure mode: the 'fake staff engineer' who holds the title but still operates as a senior IC. Tune in for a practical framework to retain your best builders without forcing them into people management.

#StaffPlusEngineering #CareerLadder #TechnicalLeadership #CTO #EngineeringManager #IndividualContributor #StaffEngineer #PrincipalEngineer #DistinguishedEngineer #TechCareers #RetentionStrategy #Spotify #GitHub #EngineeringCulture #CareerGrowth #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore how feature flags—also known as feature toggles—allow engineering teams to decouple deployment from release, reducing risk and enabling continuous delivery. They dissect a real-world example: how Etsy used feature flags to roll out a complete redesign of their checkout flow without a single production incident, gradually exposing 1% of users, then 5%, then 20%, with instant rollback at each step. The hosts discuss flag debt, the importance of a kill switch, and how to avoid the common pitfall of permanent flags. They also cover tooling like LaunchDarkly and open-source alternatives. A practical episode for any CTO or engineering manager looking to ship faster with confidence.

#FeatureFlags #ContinuousDelivery #EngineeringLeadership #CTO #TechLeadership #DeploymentStrategies #Etsy #LaunchDarkly #FlagDebt #KillSwitch #DevOps #SoftwareEngineering #RiskManagement #ReleaseManagement #Technology #Business #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how Amazon's two-pizza team rule has evolved from a founder's anecdote to a structural principle for managing cognitive load. They break down how CTOs apply the rule today—not just limiting team size, but using it to enforce bounded contexts, reduce coordination overhead, and preserve startup-like velocity inside large organizations. Drawing on examples from companies like Spotify and Microsoft, they discuss when to split teams, how to measure team coupling, and the warning signs that a team has outgrown its 'two-pizza' boundary. If you're an engineering manager or CTO wrestling with team scaling, this episode offers concrete heuristics you can use tomorrow.

#TwoPizzaTeam #Amazon #TeamTopologies #CognitiveLoad #Scaling #CTO #EngineeringManagement #TechLeadership #FexingoBusiness #BusinessPodcast #Podcast #SoftwareEngineering #Agile #DevOps #OrganizationalDesign #JeffBezos #ConwayLaw #BoundedContext

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna examine the Amazon API mandate from the early 2000s — the internal memo that forced all teams to communicate only through service interfaces. They break down how that edict created the conditions for AWS, what it means for a CTO enforcing internal standards today, and why the mandate's hidden cost was slowing down single-team features. Lucas contrasts Amazon's approach with how a modern CTO at a mid-sized SaaS company applied a similar 'API-first' rule to untangle a monolith, including the specific metrics they tracked: deployment frequency went from weekly to multiple times per day, and mean time to recover dropped from four hours to twenty minutes. They also discuss the risk of over-standardization and how one CTO used 'break-glass' exceptions to keep the mandate from stifling innovation. A concrete look at how to make internal APIs more than just a buzzword.

#Amazon #APIMandate #JeffBezos #AWS #InternalAPIs #ServiceOrientedArchitecture #CTO #EngineeringLeadership #TechnicalDebt #MonolithToMicroservices #DeploymentFrequency #MeanTimeToRecover #PlatformTeams #DORA #FexingoBusiness #Technology #BusinessPodcast #TechLeadership

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how architecture decision records (ADRs) help CTOs capture the why behind technical choices, prevent recurring debates, and on-board new engineers faster. Drawing on a real case from a mid-stage fintech that adopted ADRs after a costly API redesign, they walk through a concrete example: choosing between a monolithic payment service and event-driven microservices. Lucas explains how a simple markdown template forces clarity on context, decision, consequences, and status. Luna challenges whether ADRs slow down fast-moving teams, and Lucas counters with data on reduced decision-reversal time. They also touch on how Netflix and ThoughtWorks popularized the pattern. The episode includes a brief listener-support moment and closes with a reflection on how documentation can be a tool for trust, not bureaucracy.

#ArchitectureDecisionRecords #ADR #TechnicalLeadership #CTO #EngineeringManagement #TechDecisions #Documentation #SoftwareArchitecture #Netflix #ThoughtWorks #Fintech #EventDrivenArchitecture #Monolith #Microservices #DeveloperProductivity #TechStrategy #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into how engineering leaders can borrow Incident Command System (ICS) principles from emergency response to handle production outages. They break down the three key roles — Incident Commander, Scribe, and SME — using real examples from a major cloud provider outage. Lucas explains why assigning a dedicated scribe reduces cognitive load on the commander and why shifting from 'fix-it mode' to structured triage cuts resolution time by 35 percent. The episode also covers common pitfalls like role confusion and how to practice ICS through game days. If you've ever watched an outage spiral because too many people shouted suggestions, this episode gives you a repeatable framework to stay calm and effective.

#IncidentCommandSystem #SiteReliabilityEngineering #CrisisManagement #TechLeadership #EngineeringManagement #ProductionOutages #OnCallBestPractices #IncidentResponse #SRE #CTO #TechnicalLeadership #Podcast #FexingoBusiness #BusinessPodcast #Technology #DevOps #SystemsThinking #GameDays

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use the concept of T-shaped skills to build teams that are both deep in expertise and broad enough to collaborate effectively. They discuss the origin of the term from IDEO, how it contrasts with I-shaped and comb-shaped profiles, and a concrete example from a mid-stage SaaS CTO who reorganized squads around T-shaped principles. The hosts also touch on the challenge of evaluating T-shaped candidates in interviews and how this framework reduces handoffs and bottlenecks.

#TShapedSkills #EngineeringTeams #CTO #TechLeadership #TeamBuilding #IDEO #Collabration #Bottlenecks #CrossFunctional #Hiring #SkillsFramework #SaaS #SquadStructure #TechManagement #FexingoBusiness #BusinessPodcast #Technology #Leadership

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a mid-sized SaaS company applied Team Topologies to halve onboarding time and cut incident response times by 40 percent. They break down the four fundamental topologies — stream-aligned, enabling, complicated-subsystem, and platform — and walk through a concrete case: reorganizing a monolithic 60-person engineering org into seven stream-aligned teams with two enabling teams and one platform team. They discuss how this reduced cross-team dependencies, lowered cognitive load for developers, and allowed the company to ship features 2x faster. Lucas explains the 'sense of ownership' problem and how bounded contexts solved it. Luna pushes back on when not to use this model, and they close on the tension between autonomy and alignment. Includes a brief donation segment supporting the show.

#TeamTopologies #CognitiveLoad #EngineeringManagement #CTO #TechLeadership #StreamAligned #PlatformTeams #EnablingTeams #ComplicatedSubsystem #Ownership #OrganizationalDesign #DevOps #SaaS #IncidentResponse #Onboarding #DeveloperProductivity #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into the concept of platform teams — internal product teams that build tools, pipelines, and self-service platforms for other engineering teams. They unpack a case study from a mid-stage SaaS company that reduced new-service setup time from two weeks to 45 minutes by adopting a platform team model. Lucas explains the key principles: treating internal developers as customers, using product management practices inside engineering, and measuring success through adoption and developer satisfaction rather than output. They discuss how to avoid common pitfalls like over-engineering the platform or neglecting evangelism. Luna challenges whether platform teams work for smaller orgs, and Lucas shares a concrete threshold — typically around 50 engineers — where the investment starts to pay off. This episode offers a practical lens for CTOs and engineering leaders wrestling with scaling bottlenecks.

#PlatformTeams #DeveloperProductivity #InternalDeveloperPlatform #CTO #EngineeringLeadership #TechLeadership #ScalingEngineering #DevOps #ProductThinking #SelfService #DeveloperExperience #Technology #Business #Leadership #FexingoBusiness #BusinessPodcast #TechPodcast #EngineeringManagement

Keep every episode free: buymeacoffee.com/fexingo