In episode 55 of The Technical Co-Founder Podcast, Lucas and Luna explore how early-stage startups are deploying knowledge graphs to connect siloed internal data without a data warehouse overhaul. They break down the concrete case of a 12-person fintech startup that built a lightweight knowledge graph on top of its existing PostgreSQL database using open-source tools like Neo4j and custom embeddings. The episode covers the specific architecture decisions — why they chose a graph over a traditional relational model, how they modeled entities like customers, transactions, and support tickets as nodes, and the 40 percent reduction in time-to-answer for internal queries. Lucas explains the trade-offs in schema design and query latency, while Luna pushes on the practical question of when a knowledge graph actually makes sense versus a simpler solution. No hype, just the engineering reality of connecting data that already exists.

#KnowledgeGraphs #StartupEngineering #DataArchitecture #Neo4j #PostgreSQL #Embeddings #InternalTools #DataSilos #GraphDatabases #TechStack #FintechEngineering #OpenSourceTools #EngineeringDecisions #BusinessAndTechnology #TheTechnicalCoFounderPodcast #FexingoBusiness #BusinessPodcast #StartupTech

Keep every episode free: buymeacoffee.com/fexingo

Episode 54 of The Technical Co-Founder Podcast explores how a fintech startup called Proton Finance uses AI pair programming tools to onboard junior developers in half the usual time. Lucas and Luna discuss the specific tool they chose — GitHub Copilot with custom context — and how they pair it with structured code review. The episode covers the startup's onboarding metrics before and after, the pitfalls they encountered (like over-reliance on AI suggestions), and the three-rule framework they built to ensure juniors learn fundamentals. Listeners will learn one concrete approach they can adapt for their own teams.

#Startup #Engineering #Onboarding #AIPairProgramming #GitHubCopilot #JuniorDevs #DeveloperExperience #ProtonFinance #CodeReview #TechnicalDebt #Fintech #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #SoftwareEngineering #Mentorship #AIinDev

Keep every episode free: buymeacoffee.com/fexingo

Episode 53 of The Technical Co-Founder Podcast dives into the counter-trend of monolith-first architecture with a case study from a real startup. Lucas and Luna explore how one company reversed its microservices migration after hitting complexity walls, cutting deployment time by 80 percent and reducing infrastructure costs by half. They walk through the specific triggers: a team of eight managing thirty services, each with separate CI pipelines, databases, and deployment scripts. The conversation covers when a monolith makes sense, how to structure it modularly so you don't lose the architecture benefits, and the warning signs that your microservices have become distributed monoliths. A practical look at architectural humility and the trade-offs between scalability and developer velocity.

#Microservices #Monolith #StartupArchitecture #SoftwareEngineering #DevOps #TechDebt #DeploymentVelocity #InfrastructureCosts #ModularMonolith #DistributedSystems #EngineeringExcellence #BusinessTechnology #FexingoBusiness #BusinessPodcast #StartupLessons #CTO #CodeReview #TechnicalCoFounder

Keep every episode free: buymeacoffee.com/fexingo

Episode 52 of The Technical Co-Founder Podcast dives into event sourcing—a data architecture that treats every state change as an immutable event. Lucas and Luna explore how a real startup, order-management platform Riverbend, adopted event sourcing not for auditing but to rebuild a critical feature without a database migration. They walk through the concrete trade-offs: the append-only log that doubles as a source of truth, the replay mechanism that let them add a 'subscription pausing' feature in two weeks instead of two months, and the operational cost of event versioning when schema evolves. Lucas cites Martin Kleppmann's 'Designing Data-Intensive Applications' and contrasts event sourcing with CRUD-based approaches. The conversation also touches on CQRS (Command Query Responsibility Segregation) as a natural companion pattern, and why Riverbend chose not to use an event store like EventStoreDB but built on PostgreSQL. Listeners learn when event sourcing pays off—and when it's overkill.

#EventSourcing #CQRS #SoftwareArchitecture #PostgreSQL #DataPatterns #StartupEngineering #Riverbend #MartinKleppmann #FeatureRebuild #ImmutableLog #TechDebt #EngineeringTradeoffs #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #EngineeringLeadership #DataIntensiveApps

Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Technical Co-Founder Podcast, Lucas and Luna dive into how one startup—a fintech processing millions of transactions—uses TypeScript's type system to catch bugs before they ever reach production. They explore the specific types and patterns that prevent entire categories of runtime errors, from discriminated unions to branded types. The hosts walk through a real example: how a single 'type' declaration eliminated a class of off-by-one errors in their payment reconciliation system. They also discuss the trade-offs of strict typing, including slower compile times and the learning curve for new hires. If you're a founder or CTO deciding how strict your TypeScript config should be, this episode offers a concrete case study of what's possible when you lean into the type system. No hype, just a practical look at one team's approach to shipping fewer bugs.

#TypeScript #TypeSafety #Fintech #BugPrevention #StrictTyping #DiscriminatedUnions #BrandedTypes #EngineeringCulture #StartupEngineering #CodeQuality #TypeSystem #TechnicalDebt #DeveloperExperience #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #EngineeringFounders

Keep every episode free: buymeacoffee.com/fexingo

Episode 50 of The Technical Co-Founder Podcast. Lucas and Luna explore how a growing fintech startup reduced production incidents by 40 percent by modeling their entire microservice architecture as a dependency graph. They walk through the specific tooling — an open-source graph database called DGraph — and the cultural shift of making every team own their upstream and downstream services. They discuss how the graph caught a critical cascade failure during a routine database migration, how the company visualizes blast radius before every deploy, and why the CTO compares it to a city's subway map. If you're an engineering leader wrestling with microservice complexity, this episode gives you one concrete pattern to try next week.

#DependencyGraph #Microservices #OutagePrevention #GraphDatabase #DGraph #BlastRadius #SiteReliability #EngineeringCulture #TechDebt #IncidentResponse #SoftwareArchitecture #CTO #Fintech #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TechnicalCoFounder #EngineeringLeadership

Keep every episode free: buymeacoffee.com/fexingo

Startups often fall into the trap of planning a full system rewrite — a multi-month bet that can sink the company. In this episode, Lucas and Luna examine how one startup avoided that trap by using incremental rewrites, replacing their monolithic e-commerce backend piece by piece over eighteen months without freezing feature development. They break down the strategy: strangler fig pattern, internal API contracts, and feature flags that let the team ship new code in production alongside the legacy system. Lucas cites data from a real case where a mid-stage SaaS company cut its migration risk to near zero by keeping both systems live until each module was proven. Luna pushes on whether every team can afford the complexity of running two systems in parallel, and Lucas explains how small, reversible steps actually reduce total cognitive load. The episode closes with a practical rule of thumb: if a rewrite takes longer than three months, you're probably doing it wrong.

#IncrementalRewrite #StranglerFigPattern #TechnicalDebt #SoftwareEngineering #StartupEngineering #MigrationStrategy #LegacyCode #FeatureFlags #EngineeringVelocity #Refactoring #BusinessAndTechnology #TheTechnicalCoFounder #FexingoBusiness #BusinessPodcast #EngineeringCulture #MonolithToMicroservices #CodeMigration #RiskManagement

Keep every episode free: buymeacoffee.com/fexingo

Episode 48 of The Technical Co-Founder Podcast. Lucas and Luna explore how a startup called Kodex cut new engineer onboarding from six weeks to five days by redesigning their developer experience (DX). They break down the specific changes: a one-command setup script, a self-service sandbox environment, and a living documentation system that stays synced with the codebase. Lucas explains how Kodex measured ramp-up time using DORA metrics and why most startups neglect DX until it's too late. Luna points out the tension between investing in DX and shipping features. The hosts discuss the cost of ignoring onboarding friction — and why treating DX as a product might be the smartest investment an early-stage company can make.

#DeveloperExperience #DX #Onboarding #Startup #Engineering #DORAMetrics #Documentation #Sandbox #Kodex #Productivity #TechnicalDebt #Culture #Business #Technology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo

On this episode, Lucas and Luna explore how a fast-growing SaaS company uses feature flags to decouple deployment from release, enabling daily deploys with zero downtime. They walk through the specific implementation: a phased rollout system with automatic rollback triggers and a kill-switch dashboard. The hosts discuss the engineering trade-offs—flag debt, testing complexity, and team discipline—and share how the company reduced regression bugs by 60 percent in six months. A concrete look at a practice that's quietly reshaping how modern engineering teams ship software.

#FeatureFlags #ContinuousDeployment #DevOps #SoftwareEngineering #StartupEngineering #LaunchDarkly #ReleaseManagement #EngineeringVelocity #TechDebt #DeploymentStrategy #Business #Technology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounder #EngineeringLeadership #ShipFast #ZeroDowntime

Keep every episode free: buymeacoffee.com/fexingo

In Episode 46 of The Technical Co-Founder Podcast, Lucas and Luna dive into how one startup, a mid-stage SaaS company called FormLens, automated its code review process to reduce cycle time from 2.5 days to under 8 hours. They break down the specific tooling choices — GitHub Actions with custom workflows, auto-assigning reviewers based on file ownership, and merging pull requests with passing checks — and the cultural shifts required to trust automation over manual oversight. The hosts debate where automation ends and human judgment begins, and why the startup saw a 3x increase in deploy frequency without sacrificing code quality. Listeners will walk away with a concrete playbook for streamlining their own code review pipeline without burning out senior engineers.

#CodeReview #DeveloperProductivity #StartupEngineering #GitHubActions #DevOps #Automation #EngineeringCulture #PullRequest #ContinuousDelivery #SoftwareDevelopment #TechStartup #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #EngineeringLeadership #CTO #TechnicalCoFounder #ShipFaster

Keep every episode free: buymeacoffee.com/fexingo