Lucas and Luna sit down in front of a whiteboard to dissect the decisions that shape technical organizations. Each episode of The CTO Podcast with Fexingo examines a specific engineering leadership challenge — from scaling a microservices architecture without creating a distributed monolith, to managing the cognitive load of a 200-engineer org, to choosing between a monorepo and polyrepo strategy based on team topology. The conversations are grounded in real-world cases: how Etsy restructured its data pipeline after a 2019 outage, why Stripe’s API versioning policy reduces breaking changes, or what Basecamp’s choice of SQLite over PostgreSQL says about product philosophy. Lucas brings the journalistic rigor — citing commit histories, RFCs, and postmortems — while Luna pushes back with the pragmatics of org dynamics, hiring constraints, and technical debt. There are no hot takes, no vendor pitches, no ‘best practices’ without trade-offs. Each episode ends with a specific tension left unresolved: the optimal number of direct reports for a VP of Engineering, the point at which a monolith should be broken apart, or whether a platform team should own the CI/CD pipeline. The listener is a senior engineer, a staff+ IC, or a new CTO who wants to learn from the decisions others have made — without the hype. After an episode, you’ll have a framework, not a checklist, and a clear sense of the questions you should be asking your own team.

Support FexingoRSS Feed