Hosted by Unknown Host · EN · 5 episodes
Established thought leaders with verified media credentials.
Lucas and Luna sit down at side-by-side laptops to talk about the craft of building software. Each episode picks a single engineering challenge — optimizing a database query for latency, designing a fault-tolerant microservice boundary, refactoring a legacy monolith without breaking production — and walks through the trade-offs with real code examples and benchmark numbers. They debate testing strategies (integration vs. end-to-end, when to mock), revisit classic papers on distributed systems and data structures, and trace how architectural decisions cascade into operational costs. The show serves senior developers, staff engineers, and technical leads who want to hear reasoned, specific conversations about trade-offs and rigor — not hype about the latest framework. Lucas brings the journalist's habit of asking why a team chose one pattern over another; Luna pushes back with real-world failure stories from her own career. Together, they treat software engineering as a discipline of explicit decisions and measurable outcomes. No hot takes, no 'best practices' without context. Just two engineers thinking out loud about how to build systems that last. What does it actually cost to ship a feature with 99.99% uptime — and when is that the wrong target?
Unknown Host hosts The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices, a general show with 5 episodes published.
Episode 33 of The Software Engineering Podcast with Fexingo. Lucas and Luna dive into the story of a senior engineer who inherited a monolithic ten-year-old codebase with zero tests and a single deployment causing multi-
In this episode, Lucas and Luna dive into a near-disaster at a mid-sized SaaS company where a single engineer prevented a cascading data loss by implementing a soft delete pattern. They walk through the specific scenario
In this episode of The Software Engineering Podcast, Lucas and Luna dive into a real-world case of consistent hashing preventing a production cascade failure. They break down how one engineer at a major streaming platfor
In this episode of The Software Engineering Podcast, Lucas and Luna dive into the practical world of FinOps — cloud financial operations. They explore how a mid-size SaaS company called DataNest slashed its AWS bill by 6
In this episode, Lucas and Luna explore how a single engineer at a mid-sized fintech company slashed their AWS bill by 70 percent—over $2 million annually—by migrating stateless workloads to spot instances. They break do
In this episode, Lucas and Luna dissect a real-world data breach that stemmed from a simple two-character typo in an access control file. They walk through how a missing 'not' in an AWS S3 bucket policy left 50 million u
Flaky tests are the bane of every CI pipeline — they waste developer time, erode trust in test suites, and can hide real regressions. In this episode, Lucas and Luna dive into the story of one engineer at a mid-size fint
In this episode, Lucas and Luna unpack a real-world story from a payments startup where one obscure test case — a $0 transaction — exposed a rounding error that would have lost the company over a million dollars annually
In this episode, Lucas and Luna explore how one engineer at a mid-size SaaS company used regression testing to prevent a catastrophic production outage. The engineer, Sarah Chen, implemented a focused automated regressio
In this episode, Lucas and Luna explore a specific case where a single engineer reduced database query volume by 95 percent by implementing a carefully designed caching layer. They walk through the before-and-after: a Sa
Episode 23 of The Software Engineering Podcast. Lucas and Luna explore the underrated skill of saying 'no' in engineering culture. Drawing on a real case from a mid-size SaaS company where a lead engineer saved 400 engin
In this episode, Lucas and Luna explore how a single engineer at a mid-sized fintech company built a ChatOps bot that cut average incident response time from 45 minutes to under 8. They walk through the specific architec
In this episode, Lucas and Luna unpack a specific production incident: a PostgreSQL deadlock that brought down a mid-sized SaaS platform every night at 3 AM for three weeks. They trace the root cause—an overlooked index
In this episode, Lucas and Luna explore how one frontend engineer at a mid-size e-commerce company shrank their CSS bundle from 2.4 megabytes to under 500 kilobytes — without losing any design fidelity. They walk through
In this episode of The Software Engineering Podcast, Lucas and Luna explore how one senior engineer at a mid-size fintech company slashed new-hire onboarding time from three weeks to three days. They break down the speci
Episode 18 of The Software Engineering Podcast with Fexingo dives into the surprising power of a single linter rule. Lucas and Luna examine how a seemingly trivial ESLint configuration — no floating promises — caught a c
In this episode of The Software Engineering Podcast, Lucas and Luna dive into a notorious class of production bugs: concurrency issues that only surface under load. They explore a real-world case where a seemingly innoce
Lucas and Luna dig into a real-world case where a single engineer at a mid-size fintech company reduced their daily logging volume from 200 gigabytes to 20 gigabytes — slashing cloud storage costs by over 90% and cutting
When Spotify's engineering team hit a wall with their monolithic backend in 2014, they didn't just split it into microservices — they invented a new organizational model called squads, tribes, chapters, and guilds. In th
On-call burnout is a hidden crisis in software engineering. In this episode, Lucas and Luna explore how a senior engineer at a mid-sized SaaS company systematically reduced their team's on-call fatigue by 60 percent — wi
Sponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchShows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices has a verified contact on file. Create a free PitchCentric account to access it and generate a personalised pitch in seconds. Research at least 3 recent episodes first and lead with a specific angle that serves their general audience.
The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices is hosted by Unknown Host. The show is categorised under General and has published 5 episodes.
The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices has published 5 episodes.
The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices is accessible for guests with genuine general expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices average 9 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices's guest bar at 80/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 9 days ago.
