In this episode of The Technical Co-Founder Podcast, Lucas and Luna dive into a single, focused engineering decision: how a five-person startup migrated its production database from MongoDB to PostgreSQL in a single weekend — without downtime or data loss. They unpack the specific technical choices behind the migration: why the team chose pgloader for schema conversion, how they handled document embedding versus relational joins, and the one painful bug that nearly rolled back the entire operation. Lucas walks through the migration checklist, the read-replica fallback plan, and the performance metrics that justified the switch. Luna pushes back on the premise — shouldn't a young startup just use MongoDB and move fast? The conversation reveals why schema flexibility sometimes becomes schema chaos, and how a well-planned migration can actually ship faster than living with the wrong database. No abstract theory — just one team's playbook for a risky, high-reward infrastructure bet.

#MongoDB #PostgreSQL #DatabaseMigration #StartupEngineering #BackendInfrastructure #pgloader #DataMigration #NoSQL #SQL #ProductionDeployments #EngineeringDecisions #TechnicalDebt #StartupScaling #DevOps #DatabaseDesign #BusinessAndTechnology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

What happens when your startup's shared monorepo becomes a bottleneck? Lucas and Luna examine the story of a 12-engineer startup that deleted 50,000 lines of shared code — not because the code was bad, but because the coupling was slowing every team's deployment velocity. They walk through the three-month transition: how the engineering lead mapped dependency graphs, why they chose a domain-based monorepo slice over microservices, and the surprising result that deployment frequency doubled while bugs dropped by 30 percent. The episode also covers the tooling bet they made (custom Bazel rules), the one service they kept as a monorepo, and what the CTO now tells other founders about code organization before Series A. A concrete story for every technical founder and CTO wrestling with shared code that no longer serves the team.

#Monorepo #CodeOrganization #StartupEngineering #DeploymentVelocity #Bazel #DependencyGraph #TechDebt #EngineeringCulture #DevEx #Microservices #DomainDrivenDesign #Refactoring #BuildTooling #BusinessTechnology #SoftwareEngineering #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Technical Co-Founder Podcast, Lucas and Luna explore how early-stage startups can adopt RFCs (Request for Comments) to make better engineering decisions. They dive into a specific case: a seed-stage startup that avoided a costly six-month rewrite by writing a one-page RFC first. They discuss the minimal format that works for a three-person team, when to escalate an RFC to the whole company, and why the discipline of writing before coding saves time in the long run. If you're a technical founder or CTO debating how much process is too much process, this episode offers a concrete framework you can implement tomorrow.

#RFCs #RequestForComments #EngineeringProcess #StartupEngineering #TechnicalCoFounder #CTO #DecisionMaking #CodeReview #EngineeringCulture #TechnicalDebt #StartupScaling #SoftwareArchitecture #Documentation #Collaboration #FexingoBusiness #BusinessPodcast #Technology #EngineeringLeadership

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how Amazon's long-internal practice of writing proposals-as-documents — the 'narrative memo' — has been adapted by high-performing startups as a lightweight RFC (Request for Comments) process. They walk through a specific case: a 20-person fintech startup that used RFCs to avoid a costly six-month architecture rebuild, saving an estimated $300k in wasted engineering time. Lucas explains the mechanics — how to structure a one-page RFC, who reviews it, and the decision rule that separates a good RFC from a time-sink. Luna pushes back on when RFCs become bureaucracy, and they land on the concrete threshold: any project longer than two weeks of engineering effort should get a one-page RFC first. Listeners learn a repeatable process that costs one hour of writing and prevents weeks of misaligned work.

#StartupEngineering #RFCDocument #AmazonNarrativeMemo #TechnicalCoFounder #EngineeringManagement #CodeReview #SoftwareArchitecture #TechLeadership #ProcessDesign #FintechStartup #EngineeringCost #DecisionMaking #BuildVersusBuy #Collaboration #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounder

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into the practice of writing Request for Comments (RFC) documents as a decision-making tool for engineering teams. They explore how a five-person startup used lightweight RFCs to align on architectural choices, reduce bikeshedding, and speed up delivery — without the overhead of big-company processes. The episode walks through a concrete example: a team deciding between a monolithic deploy and a microservices split, and how the RFC format surfaced tradeoffs that a Slack thread never would. Lucas shares stats from a 2025 internal survey showing teams that use RFCs ship 30% fewer rework cycles. Luna challenges the formality ceiling — at what point does writing become bureaucracy? They agree on a sweet spot: one-page RFCs, 48-hour comment windows, and a clear decision owner. This is a practical episode for any technical co-founder or engineering leader looking to improve communication and decision velocity.

#RFCs #RequestForComments #EngineeringDecisions #StartupProcess #TechnicalCoFounder #DecisionMaking #Bikeshedding #Microservices #Monolith #Architecture #EngineeringCulture #Process #Communication #Lucas #Luna #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

When your startup's biggest rival goes under, do you buy the wreckage? This episode walks through the story of a small B2B SaaS company that acquired a bankrupt competitor and had to merge two completely different codebases without losing customers or engineering momentum. Lucas and Luna break down the acquisition price, the six-week integration timeline, the decision to keep both authentication systems, and the one database migration that nearly killed the deal. They also discuss when it makes sense to buy a competitor's intellectual property versus just letting them fade away. Specific numbers, real trade-offs, and the engineering strategy that turned a distressed asset into a growth engine.

#StartupAcquisition #CodebaseMerge #B2BSaaS #TechMerger #EngineeringStrategy #DistressedAsset #DatabaseMigration #IntellectualProperty #CompetitorBuyout #PostMergerIntegration #StartupGrowth #EngineeringDecisions #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TechnicalCoFounder #PodcastEpisode #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo

Most engineers think open source is about code. But according to Sarah Chen, a former CTO who has hired at three Y Combinator startups, the first open source library you publish is actually a job interview — and most technical founders get it wrong. In this episode, Lucas and Luna break down Sarah's framework: how a well-crafted library signals communication skills, taste, and resilience to senior engineers. They walk through a real example — a JSON parsing library that landed its author a CTO role — and discuss the three specific signals recruiters are looking for. If you're a builder wondering whether to share your side project, this episode gives you a concrete reason to push it live.

#OpenSource #Hiring #Engineering #Startup #CTO #TechnicalCoFounder #JobInterview #SarahChen #YCombinator #DeveloperRelations #SignalTheory #CareerAdvice #CodeQuality #Portfolio #Business #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 18 of The Technical Co-Founder Podcast with Fexingo dives into bug bounty programs and vulnerability disclosure. Lucas and Luna explore why even early-stage startups should set up a structured way for security researchers to report flaws, using the case of a fintech startup that avoided a major breach by listening to a white-hat hacker. They discuss the difference between bug bounties and simple disclosure, how to budget for a program when you're pre-revenue, and the cultural shift from seeing security as an afterthought to building it into your engineering DNA. Specific numbers: a typical bounty range of $500 to $5,000 for critical findings, and how one Y Combinator startup patched a server-side request forgery vulnerability within 24 hours of receiving a report. The hosts also touch on the ethical concerns around bug bounty platforms vs. running your own program, and why paying researchers is cheaper than a data breach lawsuit. If you're building from code, this episode will make you rethink how you handle the inevitable bugs.

#BugBounty #VulnerabilityDisclosure #Security #Startup #TechnicalCoFounder #Fexingo #Business #Technology #Engineering #CTO #Hacking #InfoSec #Fintech #YC #CyberSecurity #DevOps #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

When you're raising money, investors often ask for a code review — but what if your code is a mess? In this episode, Lucas and Luna unpack the story of a startup that literally hid its GitHub repository from VCs during Series A diligence. They explore the ethical tightrope between 'we're building fast' and 'we're hiding our technical debt,' and how the founding engineer managed the anxiety of showing the real codebase after the round closed. With specific tactics like gating access via read-only links, delaying the review until after a term sheet, and finally refactoring the critical path before the money hit the bank, this episode offers a rare behind-the-scenes look at startup transparency in practice. Plus, a candid moment on why the hosts keep this podcast ad-free and listener-supported.

#CodeReview #DueDiligence #SeriesA #TechnicalDebt #StartupSecrets #GitHub #VCFunding #EngineeringCulture #InvestorRelations #FounderStories #Transparency #BusinessTechnology #TheTechnicalCoFounder #FexingoBusiness #BusinessPodcast #EngineeringFounders #StartupLife #RaisingCapital

Keep every episode free: buymeacoffee.com/fexingo

In episode 16 of The Technical Co-Founder Podcast, Lucas and Luna explore how a startup called Atmo — a weather intelligence platform — adopted an internal open-source model to speed up development without sacrificing quality. When co-founder and CTO Jenna Kline realized her six-person engineering team was duplicating work across microservices, she introduced internal open-source repositories with shared linting, CI/CD templates, and documentation standards. The result: onboarding time dropped from three weeks to four days, and feature delivery velocity improved by 60 percent. Lucas breaks down the specific practices Atmo used, including how they handled code reviews and avoided the 'tragedy of the commons' within a small team. Luna pushes back on whether this approach scales beyond 10 engineers, and they discuss when internal open source starts to create more overhead than it saves. If you're a technical founder or CTO wrestling with how to standardize without slowing your team down, this episode offers a concrete playbook from a startup that made it work.

#InternalOpenSource #StartupEngineering #CTO #TechnicalCoFounder #SoftwareDevelopment #DevOps #CodeQuality #EngineeringVelocity #DeveloperProductivity #StartupScaling #CodeReviews #CI/CD #Documentation #Onboarding #Atmo #JennaKline #BusinessAndTechnology #FexingoBusiness

Keep every episode free: buymeacoffee.com/fexingo