エピソード

  • How One Startup Prioritizes Its Tech Debt Roadmap

    How One Startup Prioritizes Its Tech Debt Roadmap
    2026/06/08
    Episode 39 of The Technical Co-Founder Podcast digs into how a growing startup decides which tech debt to fix and which to leave alone. Lucas and Luna walk through the story of a 50-person SaaS company that used a weighted scoring system — balancing customer impact, developer velocity, and maintenance cost — to build a tech debt backlog that actually got done. They break down the specific criteria the team used: how many support tickets a piece of debt generated, how many engineers it blocked, and how long a fix would take. Plus, they talk about why the CEO had to approve every item on the list, and how the company avoided the trap of trying to refactor everything at once. If you've ever looked at your codebase and felt the weight of deferred maintenance, this episode gives you a practical framework for making the hard calls. #TechnicalCoFounderPodcast #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #TechDebt #EngineeringLeadership #StartupEngineering #CodeQuality #Refactoring #BacklogManagement #EngineeringStrategy #DeveloperProductivity #SaaS #StartupLessons #EngineeringManager #Prioritization #TechnicalDebt Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How One Startup Uses Internal APIs to Ship Faster

    How One Startup Uses Internal APIs to Ship Faster
    2026/06/08
    Most startups build monolithic codebases. Then they hit the wall at around ten engineers. In this episode, Lucas and Luna look at how a real startup — a B2B SaaS company called Station — broke its backend into internal APIs before it hit twenty employees. They walk through how Station defined API contracts upfront, used those contracts to parallelize work between frontend and backend teams, and cut feature delivery time by nearly forty percent. They also discuss the hidden cost: the overhead of maintaining a service catalog and the documentation burden. If you are building a product team or thinking about when to decouple your code, this episode gives you a concrete before-and-after to evaluate. #InternalAPIs #Microservices #StartupEngineering #APIFirst #Technology #Business #SoftwareArchitecture #Station #B2BSaaS #ShipFaster #APIContracts #EngineeringProductivity #FexingoBusiness #BusinessPodcast #TechnicalCoFounder #MonolithVsMicroservices #BackendArchitecture #FrontendBackend Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分
  • How One Startup Debugged Its Way to a Technical Interview Framework

    How One Startup Debugged Its Way to a Technical Interview Framework
    2026/06/07
    In this episode of The Technical Co-Founder Podcast, Lucas and Luna explore how a five-person startup turned its own debugging logs into a structured technical interview process. They break down the specific case of CargoVerify, a logistics API company that recorded every blocker its engineers hit during onboarding and then reverse-engineered those logs into a repeatable interview rubric. Lucas explains why most startup interview loops are broken — they test for textbook knowledge instead of real debugging behavior — and walks through the exact three-phase framework CargoVerify built: the log review, the paired debug session, and the post-mortem write-up. Luna pushes back on whether this approach scales past five people, and Lucas shares data showing that CargoVerify's first six hires all shipped code within their first week. The episode closes with a reflection on whether startups should stop imitating Big Tech interviews altogether. No fluff, just a concrete system you could adapt tomorrow. #TechnicalInterviews #StartupHiring #Debugging #EngineeringCulture #CargoVerify #Onboarding #Logs #PairProgramming #HiringFramework #TechnicalCoFounder #FexingoBusiness #BusinessPodcast #StartupEngineering #HiringData #CodeReview #PostMortem #Scaling #TechHiring Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分
  • Why Your Startup Should Use RFCs Before Writing Code

    Why Your Startup Should Use RFCs Before Writing Code
    2026/06/07
    Episode 36 of The Technical Co-Founder Podcast dives into the practice of writing Request for Comments (RFCs) before writing code. Lucas and Luna explore how this approach fosters alignment, catches design flaws early, and scales decision-making across engineering teams. They discuss a real-world example from a startup that decreased rework by 30% after adopting RFCs, and contrast it with the 'just ship it' culture. The episode also covers how RFCs differ from traditional documentation, how to structure one, and when the process might slow things down. If you're a technical leader looking to improve your team's decision-making, this episode is for you. #RFC #EngineeringCulture #StartupEngineering #TechnicalDecisionMaking #CodeReview #SoftwareArchitecture #TechLeadership #EngineeringProcess #StartupLessons #Documentation #ScalingEngineering #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TechnicalCoFounder #EngineeringManagement #AgileDevelopment #Collaboration Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    12 分
  • How One Startup Cut Cloud Costs by 70 Percent with Spot Instances

    How One Startup Cut Cloud Costs by 70 Percent with Spot Instances
    2026/06/06
    Episode 35 of The Technical Co-Founder Podcast. Lucas and Luna dive into the story of a bootstrapped B2B SaaS startup called StitchFlow that slashed its AWS bill by 70 percent using spot instances and a custom spot-termination handler. They walk through the architecture: a Kubernetes cluster with priority classes, a Python script that listens for the two-minute AWS termination notice and gracefully drains pods, and the trade-off between cost savings and operational complexity. They discuss when spot instances make sense, how to handle interruptions, and why this approach saved the startup from running out of runway before reaching product-market fit. Along the way, they touch on why many startups avoid spot instances due to fear of instability, and how a well-designed fallback system can turn that fear into a competitive advantage. If you are an engineering founder or CTO trying to stretch every dollar, this episode offers a concrete playbook for cutting infrastructure costs without sacrificing reliability. #CloudCosts #AWS #SpotInstances #Kubernetes #StitchFlow #BootstrappedStartup #B2BSaaS #TechInfrastructure #EngineeringFounder #CTO #CostOptimization #DevOps #CloudArchitecture #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TechnicalCoFounder #StartupStrategy Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How One Startup Uses Chaos Engineering to Build Resilient Systems

    How One Startup Uses Chaos Engineering to Build Resilient Systems
    2026/06/06
    In this episode of The Technical Co-Founder Podcast, Lucas and Luna explore the practice of chaos engineering — deliberately injecting failures into production systems to uncover weaknesses before they cause outages. They look at how one startup, a real-time payments platform, used controlled experiments like shutting down servers and corrupting data to test its infrastructure. Lucas breaks down the Netflix Chaos Monkey origin story and how smaller companies can adopt the same principles without a full SRE team. Luna asks the hard questions: how do you convince a skeptical CTO to break things on purpose? And what happens when chaos engineering reveals a critical flaw mid-deployment? The hosts also touch on the cultural shift needed — moving from blame-free postmortems to proactive failure testing. By the end, listeners will understand how to run their first chaos experiment, what tools to use (including open-source options like Chaos Toolkit and Litmus), and why the practice is essential for any startup building toward reliability at scale. #ChaosEngineering #ResilientSystems #NetflixChaosMonkey #SiteReliabilityEngineering #ProductionTesting #InfrastructureAsCode #DevOps #StartupEngineering #FailureTesting #BusinessAndTechnology #TechnicalCoFounder #FexingoBusiness #BusinessPodcast #SystemsThinking #BlameFreeCulture #Observability #IncidentResponse #SoftwareArchitecture Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How a Startup Used Property-Based Testing to Find Bugs Before Production

    How a Startup Used Property-Based Testing to Find Bugs Before Production
    2026/06/05
    Episode 33 of The Technical Co-Founder Podcast dives into property-based testing, a technique that flips traditional unit testing on its head. Lucas and Luna explore how one startup—a fintech handling real-time transaction reconciliation—used property-based testing to uncover edge cases their hand-written tests missed. They break down the difference between example-based and property-based approaches, explain the 'for all' mindset, and discuss the tradeoffs in learning curve and tooling. With examples from Python's Hypothesis library and QuickCheck for Erlang, they make a concrete case for when this technique pays off and when it's overkill. #PropertyBasedTesting #HypothesisLibrary #QuickCheck #SoftwareTesting #EdgeCases #Fintech #StartupEngineering #CodeQuality #Python #Erlang #UnitTesting #FormalMethods #TestingStrategy #BugBounty #ContinuousIntegration #BusinessAndTechnology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How One Startup Uses Formal Methods to Ship Bug-Free Code

    How One Startup Uses Formal Methods to Ship Bug-Free Code
    2026/06/05
    In episode 32, Lucas and Luna explore how a small infrastructure startup called Formal Inc. uses formal methods—mathematical proofs embedded in the development process—to guarantee their core networking library has zero runtime errors. They walk through the specific tool (Dafny), the trade-offs in developer velocity, and why the startup believes the upfront cost saves millions in post-deployment debugging. The conversation also touches on how formal verification is moving beyond aerospace and into commercial SaaS, and why one engineer described it as 'writing tests that the computer can't ignore.' If you've ever wondered whether provably correct code is practical outside of NASA, this episode is for you. #FormalMethods #Dafny #BugFreeCode #SoftwareEngineering #FormalVerification #StartupEngineering #Infrastructure #CorrectByConstruction #ProgrammingLanguages #StaticAnalysis #ReliabilityEngineering #BusinessAndTechnology #EngineeringPodcast #FexingoBusiness #BusinessPodcast #TechLeadership #CTO #CodeQuality Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分