『The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices』のカバーアート

The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices

The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices

著者: Fexingo
無料で聴く

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? #SoftwareEngineering #SystemArchitecture #CodeQuality #DistributedSystems #DatabaseOptimization #Refactoring #TestingStrategy #Microservices #Monolith #PerformanceEngineering #CleanCode #TechDebt #EngineeringCulture #PairProgramming #FexingoBusiness #BusinessPodcast #Technology #EngineeringBestPractices Keep every episode free: buymeacoffee.com/fexingo© 2026 Fexingo. All rights reserved. 経済学
エピソード
  • How One Engineer Cut Incident Response from Hours to Seconds with a Runbook
    2026/06/07
    Episode 37 of The Software Engineering Podcast with Fexingo dives into a specific operational win: how a senior engineer at a mid-size fintech company automated incident response runbooks, slashing mean time to resolution from over two hours to under thirty seconds. Lucas and Luna walk through the before-and-after — the chaotic Slack threads, the manual playbook that lived in a Google Doc, and the gradual shift to code-driven remediation. They discuss why a runbook-as-code approach reduced human error, how the team tested incident flows in staging, and the one misstep that nearly caused a false positive cascade. The episode also touches on the broader movement toward 'incident response as software' and what it means for on-call culture. No hot takes, no buzzwords — just a concrete story of making systems more resilient by writing better automation scripts. #IncidentResponse #RunbookAutomation #SiteReliabilityEngineering #DevOps #OnCall #IncidentManagement #SoftwareEngineering #Automation #RunbookAsCode #Fintech #EngineeringCulture #MTTR #ReliabilityEngineering #Observability #Postmortem #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How a Single Bit Flip Brought Down an Entire Data Center
    2026/06/07
    In episode 36 of The Software Engineering Podcast with Fexingo, Lucas and Luna dive into one of the most infamous hardware-induced software bugs in recent memory: the 2021 Facebook outage caused by a single bit flip. Lucas explains how a routine configuration change triggered a cascading failure that took down Facebook, Instagram, and WhatsApp for over six hours. He walks through the exact sequence — a BGP withdrawal, DNS failures, and a data center network meltdown — and why a single incorrect bit in a router's memory was the root cause. Luna challenges the conventional wisdom about redundancy and asks whether engineers can realistically guard against single-bit errors at scale. They discuss cosmic rays, memory error-correcting codes, and the trade-offs between software abstraction and hardware reality. Along the way, they share practical lessons for engineers designing resilient systems: from careful change management to the dangers of assuming hardware is perfect. #SoftwareEngineering #Technology #FacebookOutage #BitFlip #BGP #DNS #DataCenter #Resilience #Infrastructure #Networking #CosmicRays #ECC #ErrorCorrection #ChangeManagement #CascadingFailure #EngineeringLessons #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    6 分
  • How One Engineer Slashed Build Times from 40 Minutes to 90 Seconds
    2026/06/06
    In this episode of The Software Engineering Podcast, Lucas and Luna dive into the story of a senior engineer at a mid-size SaaS company who cut their CI build pipeline from 40 minutes to 90 seconds. They walk through the specific bottlenecks: a monolithic Gradle build with unnecessary task dependencies, Docker layers being rebuilt on every commit, and a test suite that ran sequentially. The fix was a combination of incremental compilation, parallel test execution, and a custom caching layer using BuildKit. They also discuss the cultural resistance to changing a 'working' build system and how the engineer used data to win buy-in. By the end, listeners get a concrete playbook for auditing their own CI pipelines and a reminder that build speed is often the cheapest performance optimization you can make. #SoftwareEngineering #BuildOptimization #CI #Gradle #Docker #BuildKit #IncrementalCompilation #ParallelTesting #DevEx #DeveloperProductivity #CacheStrategy #BuildPipeline #Tech #EngineeringBestPractices #FexingoBusiness #BusinessPodcast #TheSoftwareEngineeringPodcast #Fexingo Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません