『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 Stripe Solved Distributed Tracing Overhead

    How Stripe Solved Distributed Tracing Overhead
    2026/09/10
    Stripe engineers faced a brutal trade-off: full distributed tracing offered perfect observability but crushed latency and bloat the network. In this episode, Lucas and Luna dissect how one team replaced heavy JSON payloads with a binary protocol that cut trace overhead by half while preserving context. We look at the specific engineering decision to switch from text-based serialization to a compact binary format, the impact on tail latencies, and why most teams still cling to verbose logging despite the performance cost. #DistributedTracing #Observability #EngineeringCulture #SystemDesign #PerformanceOptimization #BinaryProtocols #LatencyReduction #Microservices #TechDebt #Infrastructure #CodeQuality #SoftwareArchitecture #FexingoBusiness #BusinessPodcast #TechTrends #DevOps #CloudComputing #EngineeringEfficiency Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
  • How GitHub Copilot Changes Code Review

    How GitHub Copilot Changes Code Review
    2026/09/09
    We dig into the counterintuitive reality of AI-assisted development: when code generation speeds up writing, it often slows down reviewing. We examine how one major platform team flipped their process by treating generated code as first-class contributors rather than disposable drafts. You will learn why strict review discipline is now more valuable than raw output volume, and how to audit AI-generated commits for security and style drift without drowning in noise. #FexingoBusiness #BusinessPodcast #SoftwareEngineering #CodeReview #AIAssistedDevelopment #DeveloperProductivity #TechLeadership #GitWorkflow #SecurityAudit #TechnicalDebt #TeamCollaboration #CodeQuality #EngineeringCulture #AutomationTools #ProgrammingBestPractices #SoftwareArchitecture #DevOps #ModernWorkforce Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    8 分
  • How Stripe Built a Universal Error Format

    How Stripe Built a Universal Error Format
    2026/09/08
    Stripe transformed developer experience by standardizing error responses across its entire API suite. In this episode, we explore how the company moved from chaotic, inconsistent error codes to a unified structure that reduced support tickets and accelerated integration times. Lucas and Luna break down the engineering decisions behind the move, the specific data structures involved, and why treating errors as first-class citizens in API design matters for every software team building public interfaces. #FexingoBusiness #BusinessPodcast #SoftwareEngineering #APIDesign #Stripe #DeveloperExperience #ErrorHandling #RESTAPI #TechLeadership #CodingBestPractices #SystemArchitecture #EngineeringCulture #ProductManagement #WebDevelopment #BackendEngineering #Standardization #TechnicalDebt #Scalability Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    10 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません