Episodes
How CTOs Measure Engineering Culture Health
Engineering culture is often treated as a soft metric, but at companies like HashiCorp and Datadog, leaders are measuring it with the same rigor as uptime. This episode explores how technical leaders use pulse surveys, retention cohort analysis, and internal mobility data to quantify team health before burnout strikes. We look at the specific frameworks used to turn subjective feelings of engagement into actionable operational KPIs, helping you build resilient teams that innovate without…
Why Engineering Leaders Are Killing Legacy Code
Most engineering leaders treat legacy code as a necessary evil, but that mindset is quietly killing innovation velocity. In this episode of Tech Leadership with Fexingo, Lucas and Luna examine the specific case of how one mid-sized fintech firm replaced their ten-year-old monolithic core in eighteen months without a single day of downtime. We break down the strangler fig pattern, the hidden costs of technical debt interest, and why smart CTOs are now prioritizing refactoring sprints over new…
How CTOs Master The Art Of Strategic Code Ownership
Most engineering leaders treat code ownership as a binary choice: either everyone touches everything or only one person owns a module. In this episode, Lucas and Luna explore the middle ground—strategic code ownership—and why it is becoming the critical differentiator for high-performing platforms. We look at how top CTOs balance developer autonomy with systemic risk by assigning 'primary owners' to critical paths while keeping documentation and interfaces open. Using concrete examples from…
Why CTOs Are Abandoning Code Reviews
We examine the controversial shift away from traditional peer code reviews in high-velocity engineering teams. Lucas and Luna analyze why some organizations are replacing manual review gates with automated policy-as-code and AI-assisted linting, and what this means for developer autonomy and error detection in modern software delivery. #SoftwareEngineering #CTOInsights #CodeReviewAlternatives #DevEx #PlatformEngineering #AutomationFirst #TechLeadership #DeveloperProductivity #PolicyAsCode…
How CTOs Manage Shadow AI Usage
Most CTOs are losing the battle against shadow AI. Employees are using personal accounts for work tasks, bypassing security protocols and risking data leaks. This episode examines why blanket bans fail and how leaders at companies like Microsoft and Adobe are shifting from policing to provisioning. We explore the specific strategy of creating approved internal sandboxes that mirror public tools, reducing friction while maintaining governance. The conversation digs into the metrics that actually…
Why CTOs Are Betting on AI Agents Over Chatbots
Most tech leaders are still treating artificial intelligence like a smarter search bar. In this episode, Lucas and Luna dig into why that approach is hitting a ceiling. They look at the operational shift from prompt-based chatbots to autonomous agents that can plan, execute, and verify their own work. We break down a specific case study where an engineering team moved from handling ten thousand support tickets with human-in-the-loop validation to deploying fully autonomous agents for routine…
How CTOs Build Invisible Infrastructure Teams
Most engineering leaders focus on what users see, but the real bottleneck is often internal friction. We examine how top technology organizations are shifting from feature factories to platform teams by building invisible infrastructure. Using concrete examples of developer portal adoption and API-first strategies, we explore why reducing cognitive load for engineers directly correlates with faster delivery cycles. This episode breaks down the specific metrics that matter when measuring…
Why CTOs Are Ditching Feature Teams for Platform Teams
The shift from feature teams to platform engineering is often sold as a productivity hack, but the real story lies in the hidden costs of internal friction. We look at how leading organizations are restructuring their engineering groups to treat internal developers as customers, using metrics like developer experience scores and lead time reductions to justify the change. This episode explores the specific organizational mechanics behind this transition, why it fails when treated as a pure tech…
Why CTOs Are Killing the Monolith
In this episode of Tech Leadership with Fexingo, we tackle a critical strategic pivot for engineering leaders: the transition from monolithic architectures to event-driven microservices. Lucas and Luna explore why major tech firms are moving away from tightly coupled codebases, using real-world examples like Netflix’s early decoupling efforts and modern API gateways. They discuss the hidden costs of integration complexity, the importance of domain-driven design, and how to measure success…
Why CTOs Are Ditching Agile for Flow
Agile promised flexibility but delivered fragmentation. In this episode, Lucas and Luna explore how leading engineering teams are abandoning sprints in favor of continuous flow systems. We break down the specific mechanics of Kanban-style delivery at scale, using real examples from mid-market tech firms that cut cycle time by thirty percent. The conversation dives into WIP limits, bottleneck theory, and why waiting for the 'next sprint' is actually killing innovation velocity. If you manage…
How CTOs Build Engineering Teams That Scale Without Breaking
Most engineering leaders hire for individual brilliance, which creates a fragile organization. This episode examines why high-performing teams require structural cohesion over raw talent. We look at how leading technology firms use psychological safety and clear role definitions to prevent burnout during rapid growth. The conversation explores the difference between hiring for code quality and hiring for team durability. Listeners will learn a specific framework for evaluating candidate fit…
Why CTOs Are Betting on AI Agents Over Chatbots
The shift from generative text to autonomous action is reshaping enterprise technology. We examine how leading engineering teams are moving beyond simple chat interfaces to deploy AI agents that can execute multi-step workflows, interact with legacy databases, and resolve operational issues without human intervention. This episode breaks down the architectural differences between a conversational interface and an agentic system, using specific examples from recent deployments in customer…
Why CTOs Are Killing the Monolith
Most tech leaders know they should break up their monolithic applications, but few actually do it successfully. In this episode, we examine why the traditional 'big bang' migration strategy fails more often than not and introduce a specific, tactical approach called Strangler Fig decomposition that has become the standard for modern engineering teams. We look at how companies like Netflix and Amazon didn't just rewrite code overnight but instead incrementally replaced functionality by routing…
Why CTOs Fail at AI Adoption
Most companies fail to adopt artificial intelligence not because of bad code, but because of bad organizational design. In this episode, we examine the 'AI Integration Gap' — the disconnect between pilot projects and production scale. We look at how leading tech firms structure their data teams versus their product teams, and why siloed governance kills innovation faster than any technical debt. Lucas and Luna break down specific structural failures and offer a concrete framework for aligning…
How CTOs Master Technical Decision Autonomy
Most tech leaders default to committee-driven design reviews, but the most effective CTOs practice technical decision autonomy. This episode examines how granting individual engineers ownership over specific architectural choices accelerates delivery while maintaining system integrity. We explore the trade-offs between centralized governance and distributed authority, using real-world examples from high-velocity engineering organizations. Lucas and Luna break down the frameworks used to define…
How CTOs Use Timeboxing to Kill Meeting Bloat
Most engineering teams bleed hours every week in meetings that never end. In this episode, we look at how top CTOs are using strict timeboxing not just as a scheduling tactic, but as a cultural lever to protect deep work. We examine the specific mechanics of why twenty-five minute meetings often outperform one-hour ones, and how removing buffer time forces clearer agendas. From Microsoft's internal experiments with meeting-free days to the rise of async-first standups, we explore the data on…
How CTOs Master Async Decision Making
In this episode of Tech Leadership with Fexingo, we explore how modern engineering leaders are replacing synchronous meetings with asynchronous decision-making frameworks. We look at the specific case of a mid-sized fintech company that reduced its weekly meeting hours by forty percent after implementing a structured RFC process. Lucas and Luna discuss the psychological friction of async work, the importance of written documentation as a memory system, and how to maintain team alignment without…
How CTOs Master the Art of Technical Debt Management
Most CTOs treat technical debt like a financial liability, but that analogy fails when you consider that some debt is actually strategic leverage. In this episode, we explore the concept of 'good' versus 'bad' technical debt through the lens of how high-growth startups balance speed against stability. We look at specific examples where teams intentionally took on architectural shortcuts to hit market windows, only to face massive refactoring costs later. Lucas and Luna discuss the decision…
How CTOs Manage Technical Debt Without Stalling Innovation
Most engineering leaders treat technical debt like a financial liability to be minimized, but that mindset often stalls product velocity. In this episode of Tech Leadership with Fexingo, Lucas and Luna explore the concept of 'good' versus 'bad' debt in software architecture. We look at how top-performing teams at companies like Netflix and Amazon intentionally incur short-term technical debt to ship features faster, while simultaneously maintaining rigorous processes to repay it later. We…
How CTOs Use the DORA Metrics to Improve Delivery Performance
In this episode of Tech Leadership, Lucas and Luna dive into the world of DORA metrics—the four key measures that Google's DevOps Research and Assessment team identified as predictors of high-performing software delivery. They explore how CTOs use these metrics to benchmark their teams, drive improvements, and avoid common pitfalls like vanity metrics and Goodhart's Law. From real-world examples at companies like Etsy and Netflix to practical advice on starting small, the hosts discuss how to…
How CTOs Use the Platform Engineering Maturity Model
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use the Platform Engineering Maturity Model to transform their engineering organizations. Through the lens of a mid-sized fintech's journey from ad-hoc scripts to a self-service internal developer platform, they unpack the five maturity levels, the critical role of cognitive load, and the tough funding decisions that come with platform teams. Expect real talk on measuring success beyond adoption metrics, the danger…
How CTOs Use Chaos Engineering to Build Resilient Systems
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use chaos engineering to build systems that fail gracefully. They discuss the origins of the practice at Netflix, the difference between chaos engineering and traditional testing, and how teams can start small with game days and fault injection. The conversation highlights the importance of blameless postmortems and the cultural shift required to make resilience a shared responsibility. Lucas shares a concrete…
How CTOs Use the Last Responsible Moment to Delay Decisions
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use the concept of the last responsible moment to make better timing decisions. They dive into a real-world example from a fintech company that delayed its cloud migration choice until the last possible quarter, saving months of rework. The hosts discuss how to identify critical decision points, the difference between reversible and irreversible decisions, and how to communicate the strategy to stakeholders. They…
How CTOs Use the Last Responsible Moment to Delay Decisions
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore the Last Responsible Moment principle—delaying decisions until the cost of delay equals the cost of change. Through the lens of a real-world example, they discuss how a CTO of a fintech startup used this approach to avoid premature commitment to a database technology, saving millions in rework. They contrast it with decision paralysis, explain how to set decision deadlines using real options, and share practical heuristics…
How CTOs Use Backstage Plugins to Build Developer Portals
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs are moving beyond the Backstage core to build powerful developer portals through custom plugins. They break down a real-world case: a mid-sized fintech that cut developer onboarding time by 40 percent using a custom plugin that automates access to staging environments. The hosts discuss the plugin architecture, the importance of treating plugins as products, and how to avoid common pitfalls like plugin sprawl. They…
How CTOs Use the Backstage Platform to Build Developer Portals
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs are using Backstage, the open-source developer portal originally built at Spotify, to create a single, standardized interface for everything from service catalogs to CI/CD pipelines. They walk through a real-world example: a mid-sized fintech that cut its onboarding time for new engineers from two weeks to two days by centralizing documentation and service ownership. They discuss the concept of 'paved roads'…
How CTOs Use the Dependency Inversion Principle to Escape Vendor Lock-In
In this episode of Tech Leadership, Lucas and Luna explore how CTOs use the Dependency Inversion Principle—a core SOLID design pattern—to escape vendor lock-in and build systems that can evolve. They anchor the discussion with the story of a mid-sized fintech that swapped its core payments provider in six weeks by inverting dependencies at the architecture level. Lucas breaks down the difference between depending on abstractions versus concrete implementations, and shares practical signals that…
How CTOs Use the Strangler Fig Pattern to Modernize Legacy Systems
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore the strangler fig pattern—a software modernization strategy that gradually replaces legacy systems without the risk of a big-bang rewrite. They open with a concrete example from a regional bank that used the pattern to migrate a core banking platform over 18 months, then break down the technical and organizational mechanics: how to identify strangler points, manage dependencies, and keep teams motivated during a long…
How CTOs Use the Strangler Fig Pattern to Modernize Legacy Systems
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use the strangler fig pattern to incrementally modernize legacy systems without risky big-bang rewrites. They trace the metaphor back to its rainforest origins, then dive into a real-world example: how a major financial services firm replaced a core policy administration system over three years using a strangler approach, cutting outage risk while keeping the old system running. They discuss the practical…
How CTOs Use Shift-Left Security to Prevent Breaches
In this episode of Tech Leadership, Lucas and Luna explore how engineering leaders use shift-left security to catch vulnerabilities early in the development lifecycle. They discuss the concrete example of a large payment processor that cut late-stage security findings by 40 percent by embedding security review into pull requests. The hosts break down the specific practices — threat modeling at design time, IDE plugins that flag risky APIs, and security champions within teams — and how CTOs…
How CTOs Use Ops Reviews to Prevent Incident Fatigue
In episode 160 of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs and engineering leaders can prevent incident fatigue by restructuring their operations reviews. Using the example of a payments platform that reduced its weekly incident review from two hours to twenty minutes, they discuss the shift from blame-oriented post-mortems to forward-looking action tracking, the role of blameless culture, and how to measure the effectiveness of ops reviews. They also touch on the balance…
How CTOs Use the Incremental Commitment Model to Manage Risk
Episode 159 of Fexingo Tech Leadership dives into the Incremental Commitment Model (ICM) with hosts Lucas and Luna. They explore how CTOs can use this risk-driven framework to steer complex technology projects, contrasting it with traditional waterfall and pure agile methods. The conversation anchors on a real-world case: a fintech company migrating a core payments platform to microservices. Lucas and Luna break down the ICM's four phases — definition, design, implementation, and operations…
How CTOs Use Versioned APIs to Retire Legacy Systems
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use versioned APIs as a strategic tool for retiring legacy systems without the chaos of a big-bang rewrite. They break down the real-world case of a major bank that successfully migrated from a decades-old mainframe system by exposing a modern API layer, incrementally moving consumers over, and shutting down the old system piece by piece. Along the way, they discuss the difference between breaking and non-breaking…
How CTOs Use the Spotify Model to Scale Agile
In this episode of Tech Leadership, Lucas and Luna explore how CTOs apply the Spotify Model to scale agile practices across growing engineering organizations. They break down the model's core components—squads, tribes, chapters, and guilds—and discuss real-world adaptations beyond music streaming. The conversation digs into the trade-offs of autonomous squads versus alignment, how to avoid the 'copy-paste' trap, and why the model isn't a one-size-fits-all blueprint. They also share practical…
How CTOs Use the Concept of Cognitive Load to Structure Teams
In this episode, Lucas and Luna explore how CTOs use cognitive load theory to design engineering teams and systems. They start with a concrete example: a team at a mid-sized SaaS company that was drowning in context-switching because they owned a sprawling monolith. The discussion covers the difference between intrinsic, extraneous, and germane load, and how a CTO might measure team overload. They cite research on the limits of working memory and contrast it with team-level capacity. The…
How CTOs Use the AWS Lambda Cold Start Problem as a Design Catalyst
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how the AWS Lambda cold start problem—the latency spike when a serverless function spins up from scratch—has become a powerful design constraint for CTOs. They break down why cold starts happen, how teams like iRobot and Capital One have turned this limitation into a driver for architectural innovation, and the concrete strategies CTOs use: from VPC tweaks and provisioned concurrency to rethinking function granularity and…
How CTOs Use the Wardley Map to Spot Strategic Gaps
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use Wardley Maps to identify strategic gaps before they become crises. They walk through a real example: a mid-sized SaaS company whose customer support team was drowning in tickets because their product had grown overly complex. Using a Wardley Map, the CTO spotted that the support process was highly evolved but the underlying data pipeline was still in the 'genesis' phase — a mismatch that explained the…
How CTOs Use the Wardley Map to Spot Strategic Gaps
In this episode of Tech Leadership, Lucas and Luna explore how CTOs use Wardley Mapping to visualize technical strategy. They discuss the basics of the framework—value chain, evolution axis, and the concept of 'climatic patterns'—and then apply it to a real-world scenario: a fintech startup facing a competitive threat. Lucas explains how mapping the company's value chain reveals a critical gap: their payment processing is a commodity that a competitor has turned into a utility, changing the…
How CTOs Use the Power of Constraints to Spark Innovation
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how top CTOs intentionally impose artificial limits on their teams to unlock creativity and speed up delivery. Drawing on examples like the early days of the iPhone and the Apollo program, they discuss the difference between helpful constraints and harmful bottlenecks, and how a simple rule like 'two services per team' can dramatically simplify architecture. They also share practical advice for engineering leaders on how to…
How CTOs Use the Amazon Working Backwards Process
In this episode of Tech Leadership, Lucas and Luna dive into Amazon's 'working backwards' process — a method that starts with a press release and FAQ before any code is written. They explore how this customer-obsessed approach can transform product development in any engineering organization, using examples like the Kindle and Amazon Prime to illustrate its power. The hosts discuss the structure of a press release, how to run a working backwards meeting, and the common pitfalls teams face when…
How CTOs Use the Wardley Map to Spot Strategic Gaps
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use Wardley Mapping to visualize technical strategy and spot strategic gaps before they become crises. They break down the core components of a Wardley Map—value chain, evolution axis, and the anchor—and walk through a real-world example of a fintech startup that used the map to decide whether to build or buy its payment processing. Lucas explains how to run a mapping session in under two hours and how to avoid…
How CTOs Use the Two-Pizza Team Rule
In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into the two-pizza team rule—Amazon's famous principle that a team should be small enough to be fed with two pizzas. They explore why this rule still matters in 2026, how it maps to cognitive load and team topology, and the trade-offs when teams grow or shrink. Using real-world examples from Amazon, Spotify's squad model, and a case of a misapplied two-pizza rule at a mid-size fintech, they unpack the practical nuances: when…
How CTOs Use Chaos Engineering to Build Resilient Systems
In this episode, Lucas and Luna explore how CTOs use chaos engineering to build systems that fail gracefully. They break down the practice with a concrete example: the 2021 Facebook outage, which took down Instagram and WhatsApp for hours, and show how a structured game day could have limited the blast radius. Lucas explains the difference between chaos engineering and simple testing, highlights the role of blast radius and rollback plans, and shares how even a small startup can adopt a…
How CTOs Use Platform Engineering to Cut Developer Toil
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs are using platform engineering to reduce developer toil and speed up delivery. They break down the difference between a platform team and a platform product, using the example of a fictional fintech that cut its onboarding time from two weeks to two days. You'll learn why internal developer platforms are the new 'product' inside engineering orgs, how to measure their success with adoption and time-to-first-commit…
How CTOs Use Platform Teams to Cut Duplication
In this episode of Tech Leadership, Lucas and Luna drill into a persistent engineering problem: how to stop multiple teams from building the same internal tool. They trace the shift from a duplication-heavy world where every squad rolls its own authentication and data-pipeline glue, to the rise of internal platforms as products. The conversation centers on one concrete case—how a mid-size fintech cut its internal tool count by roughly forty percent in eighteen months by standing up a platform…
How CTOs Use the Reverse Conway Maneuver to Reshape Teams
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore the Reverse Conway Maneuver—a strategy where CTOs deliberately restructure engineering teams to influence the architecture they want, rather than letting the current team structure dictate code. They dissect a real-world example: how a mid-sized fintech used the maneuver to break a monolith into microservices, detailing the specific team boundary changes, the friction encountered, and the measurable impact on deployment…
How CTOs Use Renormalization to Cut Complexity
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs can apply the concept of renormalization—borrowed from physics—to simplify complex systems. They discuss how Netflix applies renormalization to its recommendation algorithms, how a CTO might use it to rationalize a microservices architecture, and why the process of 'coarse-graining' can help engineering teams focus on what matters. The hosts also share practical steps for applying renormalization in your own…
How CTOs Use Throwing Away Code to Learn Faster
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore a counterintuitive CTO practice: deliberately building and then discarding software to learn faster. They look at how a major fintech used a throwaway prototype to validate a risky migration strategy, saving months of rework. The discussion covers the difference between throwaway code and technical debt, how to time-box experiments, and when a 'spike' is the right call. Lucas breaks down the economics of sunk costs and why…
How CTOs Use the Concept of Technical Debt to Make Tradeoffs
In this episode of Tech Leadership with Fexingo, Lucas and Luna dive deep into the concept of technical debt — not as a metaphor to fear, but as a strategic tool CTOs use to make deliberate tradeoffs. They discuss the difference between reckless and prudent debt, how to measure it beyond code smells, and why the best engineering leaders treat it like a financial instrument with interest rates. Using examples like the Apache Web Server's early decisions and a hypothetical startup's API rewrite…
How CTOs Use the Dreyfus Model to Develop Engineers
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs apply the Dreyfus Model of skill acquisition to tailor engineering development programs. Using real-world examples like a platform team's onboarding journey and a staff engineer's transition to a new domain, they discuss the five stages from novice to expert and how managers can adjust their coaching, delegation, and feedback at each level. The episode also covers common pitfalls like the 'expert blind spot' and…
Showing the latest 50 episodes. The full archive of 190 is on Apple Podcasts, Spotify and every major podcast app — or via the RSS feed above.