エピソード

  • Why Your Team Needs a Technical Decision Record

    Why Your Team Needs a Technical Decision Record
    2026/06/09
    Lucas and Luna dissect the Technical Decision Record (TDR) — a lightweight practice that captures the rationale behind tough engineering choices. They walk through a real case where a CTO's team avoided repeating a costly database migration mistake by documenting their reasoning. The episode covers what makes a good TDR (title, context, decision, consequences), how it differs from RFCs and ADRs, and why a two-paragraph TDR can save months of rework. Plus, a practical tip on making TDRs a habit without creating bureaucracy. #TechnicalDecisionRecord #TDR #EngineeringManagement #CTO #TechLeadership #DecisionDebt #Documentation #DatabaseMigration #SoftwareArchitecture #EngineeringCulture #KnowledgeManagement #Business #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo #EngineeringManagers #TechnicalLeadership Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How One CTO Uses Code Reviews to Find Org Design Problems

    How One CTO Uses Code Reviews to Find Org Design Problems
    2026/06/08
    In this episode of Tech Leadership, Lucas and Luna explore a surprising diagnostic tool for organizational design: the code review. Drawing on a real case from a 200-engineer company that was struggling with slow feature velocity, Lucas explains how a new CTO analyzed pull request patterns to uncover hidden team coupling, misaligned incentives, and unclear ownership. They walk through specific signals—like excessive reviewers per PR, recurring nitpick comments, and PRs that sit idle for days—and what each reveals about team structure. Luna pushes back on the idea that code review is a reliable org signal, and Lucas cites data from a 2024 study on PR latency and Conway's Law. The hosts also discuss how the CTO used these findings to merge two teams and redefine ownership boundaries, cutting average PR cycle time from five days to under two. Filled with concrete examples and actionable heuristics, this episode gives engineering leaders a new lens for diagnosing friction without running a single survey. #CodeReview #OrgDesign #EngineeringManagement #CTO #ConwaysLaw #PullRequests #TeamStructure #DeveloperProductivity #TechLeadership #PRLatency #SoftwareEngineering #Coupling #Ownership #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #Leadership Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    9 分
  • How One CTO Cut Cloud Costs by Rethinking Commitments

    How One CTO Cut Cloud Costs by Rethinking Commitments
    2026/06/08
    Episode 38 of Tech Leadership with Fexingo. Lucas and Luna explore how a real CTO saved forty percent on cloud bills by replacing reserved instances with convertible commitments and usage forecasting. They walk through the actual math: moving from a one-year fixed reservation to a dynamic portfolio of convertible RIs and Savings Plans, using a rolling forecast of compute demand. Lucas explains the three levers the CTO pulled: converting underutilized reservations, layering Savings Plans on top, and rightsizing instances based on six months of data. Luna pushes back on whether this works for startups with spiky traffic. They land on a framework: the 'commitment delta' — the gap between what you reserved and what you actually use. If that delta is under ten percent, you're doing well. Over thirty percent, you're losing money. The episode gives listeners a specific, actionable number to audit their own cloud commitments this quarter. No fluff, no theory — just a real decision from a real engineering leader. #CloudCosts #CTO #ReservedInstances #SavingsPlans #CostOptimization #FinOps #AWS #Azure #GCP #EngineeringLeadership #TechLeadership #CloudFinance #Infrastructure #DevOps #FexingoBusiness #BusinessPodcast #Technology #Podcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    6 分
  • How One CTO Turned On-Call Pain Into Developer Leverage

    How One CTO Turned On-Call Pain Into Developer Leverage
    2026/06/07
    In this episode of Tech Leadership with Fexingo, Lucas and Luna explore a radical shift in on-call philosophy. They examine how one CTO at a mid-sized SaaS company transformed on-call from a dreaded rotation into a structured learning and ownership tool. The key insight: rotating developers through a dedicated 'incident triage' role for two-week sprints, paired with a strict no-escalation policy unless the issue meets a severity threshold, actually reduced burnout and improved system understanding. Lucas breaks down the metrics: a 40 percent drop in after-hours pages, a 22 percent increase in code contributions from engineers who'd completed the triage rotation, and a measurable uptick in team confidence during incident response drills. Luna pushes back on the 'no escalation' rule, but the data shows that when engineers own the full lifecycle of minor incidents, they naturally prioritize fixes that prevent recurrence. Listeners will walk away with a concrete model to trial in their own teams — and a sense that on-call doesn't have to be a misery tax. #OnCall #IncidentManagement #DeveloperProductivity #EngineeringLeadership #BurnoutPrevention #SaaS #CTO #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #EngineeringManagement #SRE #DevOps #IncidentResponse #TeamCulture #TechnicalDebt #DeveloperExperience Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分
  • How One CTO Replaced Standups With a Status Board

    How One CTO Replaced Standups With a Status Board
    2026/06/07
    Lucas and Luna dive into a radical shift in team communication: one CTO at a 40-person SaaS company replaced daily standup meetings with an asynchronous status board. They break down the specific problems the old standups caused — context switching, status-as-theatre, and the 15-minute meeting that actually took 45 — and how a simple shared document changed everything. The episode walks through the concrete implementation: what went on the board, how the team handled blockers without a daily huddle, and the surprising effect on junior engineers who suddenly felt more empowered to speak up. They also discuss when this approach fails, and what the CTO learned from the teams that quietly abandoned the board. No hot takes — just a real case with real numbers: the team cut meeting time by 90 minutes per person per week and incident response time actually improved by 15%. For engineering leaders tired of performative standups, this episode offers a specific alternative worth testing. #StandupMeetings #AsyncCommunication #EngineeringManagement #CTO #TeamProductivity #MeetingCulture #StatusBoard #SaaS #TechLeadership #RemoteWork #DeveloperProductivity #Agile #Scrum #EngineeringCulture #MeetingReduction #Blockers #JuniorDevelopers #FexingoBusiness Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How One Team Cut Their Cloud Bill By Changing Nothing

    How One Team Cut Their Cloud Bill By Changing Nothing
    2026/06/06
    Episode 35 of Tech Leadership with Fexingo. Lucas and Luna dive into a counterintuitive cost-saving strategy: instead of optimizing infrastructure, a mid-stage startup eliminated cloud waste by killing zombie workloads and enforcing tagging governance. They walk through how a $400,000 annual savings was found by simply turning off forgotten resources and tagging everything else. Along the way they discuss why most cost optimization efforts focus on the wrong layer and how engineering leaders can build a culture of cost awareness without a dedicated FinOps team. Practical, specific, and grounded in a real case from Q2 2026. #CloudCosts #FinOps #ZombieWorkloads #TaggingGovernance #EngineeringLeadership #CostOptimization #CloudInfrastructure #AWS #Azure #GCP #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #CTO #EngineeringManager #Podcast #CloudWaste Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How One Engineering Manager Cut Cognitive Load by Adopting Async Communication

    How One Engineering Manager Cut Cognitive Load by Adopting Async Communication
    2026/06/06
    In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how asynchronous communication can dramatically reduce cognitive load for engineering teams. They dive into a real-world case from a mid-sized SaaS company that adopted an 'async-first' policy—slashing meeting hours by 40% and boosting deep work time. The hosts dissect the specific tactics used: structured written updates, decision documents replacing hallway chats, and a 'no-meeting Wednesdays' rule that stuck. Lucas argues that async isn't just about efficiency—it's about inclusivity for remote and neurodiverse team members. Luna pushes back on the risks of information silos and delayed feedback loops. Together, they offer a balanced playbook for engineering leaders looking to reclaim focus time without losing alignment. If you've ever felt drained by back-to-back standups and Slack pings, this episode gives you concrete steps to try on Monday. #AsyncCommunication #CognitiveLoad #EngineeringManagement #RemoteWork #DeepWork #MeetingReduction #TeamProductivity #TechLeadership #SoftwareEngineering #WorkplaceCulture #CommunicationStrategy #Neurodiversity #DevEx #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #Leadership Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • Why You Should Write Your RFCs in Public

    Why You Should Write Your RFCs in Public
    2026/06/05
    Most engineering teams write RFCs (Request for Comments) behind closed doors. In this episode, Lucas and Luna explore why publishing RFCs to the entire company — not just the engineering org — can catch architectural blind spots early, reduce rework, and build institutional knowledge. They dig into a case where a database migration proposal caught a critical data compliance issue because someone in legal spotted it during the public comment period. They discuss the trade-offs: more eyes means more noise, but also more signal. Lucas argues that the transparency forces authors to write more clearly, while Luna points out that it also democratizes decision-making beyond the senior engineers. They wrap with practical advice: start with one team, use a weekly digest to avoid notification fatigue, and treat RFCs as living documents, not one-and-done proposals. If you're a CTO or engineering manager looking to cut decision debt, this one's for you. #RFCs #RequestForComments #EngineeringManagement #TechnicalLeadership #CTO #TechDecisions #DecisionDebt #Transparency #EngineeringCulture #DatabaseMigration #Compliance #KnowledgeManagement #InternalCommunications #Architecture #Collaboration #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    9 分