『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 a Single Feature Flag Prevented a Five-Hour Outage

    How a Single Feature Flag Prevented a Five-Hour Outage
    2026/06/08
    In this episode, Lucas and Luna dive into the story of a fintech startup that avoided a catastrophic outage during a critical payment system migration — thanks to a single feature flag. They break down how the engineering team used a kill switch to gradually roll out a new database schema, caught a silent data corruption bug in the canary phase, and toggled back to the old system in under 90 seconds. The episode explores the architecture behind feature flags, the difference between a flag and a config, and why one senior engineer insisted on a global off-switch that saved the company from a five-hour incident. Lucas draws parallels to how companies like Netflix and Etsy use similar patterns for safe deployments. Listeners learn one concrete takeaway: every high-risk migration should start with a feature flag, not a flip. #FeatureFlags #SoftwareEngineering #IncidentResponse #Fintech #DeploymentStrategy #KillSwitch #DatabaseMigration #CanaryRelease #TechEngineering #SystemReliability #FexingoBusiness #BusinessPodcast #Technology #EngineeringBestPractices #ResilienceEngineering #SiteReliability #ProductionSafety #MigrationStrategy Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    14 分
  • How One Engineer Automated Code Review with a Custom Static Analysis Tool

    How One Engineer Automated Code Review with a Custom Static Analysis Tool
    2026/06/08
    In this episode, Lucas and Luna explore how a single engineer at a mid-size SaaS company built a custom static analysis tool that automated 80% of code review comments. They break down the specific rules the tool enforced, how it was integrated into the CI pipeline, and the surprising cultural pushback the engineer faced. The episode includes a real-world example: a rule that caught unnecessary database queries in pull requests, saving hours of manual review per week. Lucas and Luna also discuss the trade-offs between custom tools and off-the-shelf linters like ESLint and SonarQube. Perfect for senior engineers and tech leads looking to reduce review bottlenecks without sacrificing code quality. #StaticAnalysis #CodeReview #Automation #EngineeringProductivity #CustomTools #CI_Pipeline #Linter #DeveloperExperience #TechLead #SaaS #PullRequest #DatabaseQueries #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast #CodeQuality #TechPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    7 分
  • How One Engineer Cut Incident Response from Hours to Seconds with a Runbook

    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 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません