Episode 30 of Tech Leadership with Fexingo dives into the hardest infrastructure decision a CTO can face: when to migrate off a database that's been running in production for years. Lucas and Luna unpack the story of a mid-stage SaaS company that switched from MongoDB to PostgreSQL after three years of accumulating workarounds, query timeouts, and data inconsistency bugs. They walk through the technical triggers — specifically a cascading replica failure during a routine backup — that forced the engineering team to admit their document store was the wrong fit for their relational domain. The episode covers how the team sized the migration, why they chose a strangler fig pattern over a big-bang cutover, and the one metric that told them the migration had succeeded: p99 query latency dropped from 1.2 seconds to 40 milliseconds. No hype, no vendor pitches — just a real engineering leadership story about admitting a mistake and executing a fix at scale.

#DatabaseMigration #MongoDBtoPostgreSQL #StranglerFigPattern #EngineeringLeadership #CTODecisions #Infrastructure #TechDebt #DataConsistency #QueryLatency #PostgreSQL #MongoDB #MigrationStrategy #ProductionIncident #SaaS #TechnicalLeadership #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Many engineering teams build internal developer platforms that nobody adopts. In this episode, Lucas and Luna unpack why — and what one team did differently. They walk through a real case: a mid-size SaaS company whose API platform team spent eight months building a developer portal with every feature the team could imagine, only to find that six months after launch, fewer than 20 percent of services were using it. The hosts trace the root cause: the platform team built for their own ideal developer, not the actual developer — cargo-culting patterns from big tech without understanding their own engineers' pain points. Lucas explains the specific missteps: too many abstractions, a mandatory migration deadline that scared teams, and a lack of dogfooding. Luna pushes back on whether those mistakes are avoidable when you're a small team. The conversation drills into the one metric that matters for platform adoption — time to first deploy — and how one CTO cut it from four days to two hours by letting teams opt in gradually. No hot takes, just a concrete playbook for anyone building a platform their colleagues won't ignore.

#InternalDeveloperPlatform #PlatformEngineering #DeveloperExperience #APIManagement #EngineeringLeadership #TechDebt #DeveloperProductivity #CTO #VPE #EngineeringManager #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #Kubernetes #Microservices #DeveloperPortal #Backstage

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna discuss how an internal developer platform (IDP) can dramatically reduce deployment times and cognitive load for engineering teams. Lucas shares a specific case study from a mid-stage startup that built a lightweight IDP using backstage and custom scaffolder templates, cutting average deploy time from 45 minutes to 8 minutes and reducing onboarding from two weeks to two days. They explore the trade-offs between buying versus building, the role of platform teams, and why a good IDP isn't just about tooling — it's about treating developers as customers. If you're an engineering leader wondering whether an IDP is worth the investment, this episode gives you a concrete model to evaluate.

#InternalDeveloperPlatform #PlatformEngineering #DevOps #Backstage #DeployTimes #DeveloperExperience #EngineeringProductivity #CTO #TechLeadership #EngineeringManager #SiteReliabilityEngineering #InfrastructureAsCode #SoftwareDelivery #DeveloperTools #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a real-world case study of how a mid-sized SaaS team reduced their AWS bill by 40% over six months — without sacrificing latency or developer velocity. They unpack the specific tactics that worked: from right-sizing instances and committing to reserved capacity, to implementing a 'cost per feature' tracking process that made engineers think twice before provisioning resources. Lucas explains why most cost-cutting advice fails because it treats cloud spend as a finance problem instead of an engineering culture problem. Luna brings data on how the team used a simple tagging policy linked to their OKRs to create accountability. They also discuss the trade-offs of using spot instances for production workloads and why one engineer's script to auto-shutdown staging environments on weekends became the team's highest-ROI project. By the end, you'll have a concrete framework for starting your own cloud cost optimization initiative — one that doesn't slow down your teams or require a dedicated FinOps hire. Ideal for CTOs, engineering managers, and senior engineers who want to align cloud spend with business value.

#CloudCosts #FinOps #AWSCosts #EngineeringManagement #TechLeadership #CostOptimization #SaaS #DeveloperProductivity #ReservedInstances #SpotInstances #RightSizing #TaggingPolicy #OKRs #DevOps #CloudInfrastructure #TechPodcast #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna break down how a CTO at a mid-stage SaaS company used lightweight Request for Comments (RFCs) to eliminate decision debt. They walk through a real example from a team that was paralyzed by recurring architecture debates until they enforced a written proposal process. The hosts discuss why RFCs force clarity, how to keep them short (under 500 words), and why the best RFCs include a concrete 'no' section. They also share a simple rule: any decision involving more than two engineers requires an RFC. No consultants, no tools — just a habit that saved one engineering org roughly 200 hours of meeting time per quarter.

#RFC #DecisionDebt #EngineeringManagement #TechnicalLeadership #CTO #ArchitectureDecisions #WrittenProposals #MeetingEfficiency #TeamHabits #TechDebt #EngineeringCulture #Scalability #Leadership #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #DecisionFatigue

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a case study of a mid-stage SaaS company that slashed its mean time to acknowledge (MTTA) from 12 minutes to under 4 minutes — a 70% improvement — without adding headcount or buying expensive tools. They break down the three specific changes the team made: redesigning the on-call rotation to use a 'follow-the-sun' model, implementing a tiered escalation protocol that routes alerts based on severity, and introducing a 'swarming' practice where the first responder owns the incident until resolution. Lucas shares why most incident response improvements fail because teams optimize for alert volume instead of alert quality, and Luna pushes back on whether these practices scale beyond small teams. They also discuss how the team used a simple pre-mortem exercise to identify their biggest bottlenecks before making changes. This episode is packed with actionable advice for engineering leaders looking to reduce burnout and improve reliability.

#IncidentResponse #OnCall #EngineeringLeadership #SiteReliabilityEngineering #DevOps #IncidentManagement #FollowTheSun #Swarming #AlertFatigue #MeanTimeToAcknowledge #MTTA #PreMortem #BurnoutPrevention #Observability #TechLeadershipWithFexingo #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna break down why traditional on-call rotations damage engineering culture and what to do instead. Using concrete examples from a mid-sized SaaS company that cut burnout by 40 percent and increased incident response speed by 30 percent by switching to a dedicated response team model. They discuss the hidden costs of interrupt-driven work, the myth of equal rotation, and how to build an on-call system that respects engineering time without sacrificing reliability. Practical takeaways for CTOs and engineering managers.

#OnCall #EngineeringCulture #Burnout #IncidentResponse #TechLeadership #SRE #DevOps #EngineeringManagement #CTO #Reliability #TeamMorale #InterruptDriven #DedicatedResponseTeam #SaaS #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 23 of Tech Leadership with Fexingo dives into the surprisingly high-stakes world of API style guides. Lucas and Luna discuss why a well-crafted guide is more than just naming conventions — it's a tool for reducing cognitive load, speeding up onboarding, and preventing production incidents. They break down specific examples: the difference between RESTful and RPC-style endpoints, the hidden cost of inconsistent error responses, and how one team at a mid-size fintech cut integration time by 40% after adopting a shared guide. The conversation also touches on the tension between strict rules and developer autonomy, and why a style guide should be a living document, not a PDF that collects dust. Whether you're a CTO, an engineering manager, or a senior IC trying to persuade your team to standardize, this episode offers concrete arguments and practical starting points.

#API #StyleGuide #EngineeringLeadership #TechnicalDebt #DeveloperExperience #REST #RPC #Consistency #Onboarding #IncidentPrevention #LivingDocument #Versioning #ErrorHandling #URLDesign #CamelCase #SnakeCase #Fintech #PlatformEngineering

Keep every episode free: buymeacoffee.com/fexingo

Episode 22 of Tech Leadership with Fexingo explores the concept of a congestion budget for engineering teams — a powerful tool to prevent bottlenecks before they form. Lucas and Luna unpack a real case: a mid-stage fintech company that used congestion budgets to cut deployment wait times by 60 percent and unblock feature velocity. They discuss how to measure congestion using cycle time, work-in-progress limits, and queue depth, and why this approach beats traditional capacity planning. The episode dives into implementation tactics: setting budget thresholds, making trade-offs visible, and creating a culture where teams own their flow. If your engineers are waiting more than they're shipping, this episode offers a concrete framework to reclaim throughput.

#CongestionBudget #EngineeringManagement #TechLeadership #Bottlenecks #CycleTime #QueueTheory #WIPLimits #FlowEfficiency #DevOps #SoftwareEngineering #TeamThroughput #CapacityPlanning #FeatureVelocity #FexingoBusiness #BusinessPodcast #Technology #EngineeringCulture #LeanSoftware

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore the concept of a congestion budget for engineering teams—inspired by traffic flow theory. They discuss how a $12 million Series A startup used a congestion budget to slash deployment time from 45 minutes to 12 and reduce rollbacks by 60 percent. The conversation covers the three metrics of a congestion budget: WIP limits, queue depth, and batch size. Lucas shares a real example from a client who mapped their CI/CD pipeline as a network of queues, while Luna challenges whether this works for teams with unpredictable workloads. They also touch on how the principle maps to other systems like code review and on-call rotations.

#CongestionBudget #EngineeringManagement #QueueingTheory #WIPLimits #BatchSize #QueueDepth #CICDPipeline #DeploymentOptimization #LeanEngineering #FlowEfficiency #TechLeadership #EngineeringTeams #StartupEngineering #DevOps #SiteReliabilityEngineering #SoftwareDelivery #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo