『The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers』のカバーアート

The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers

The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers

著者： Fexingo
無料で聴く

Lucas and Luna examine the developer tools landscape — APIs, infrastructure, and software designed for engineers — through the lens of business viability and technical merit. Each episode picks a specific tool or platform: how it was built, what problem it solves, who pays for it, and whether its architecture gives it a durable advantage. They compare pricing models, study public SDKs and changelogs, and trace the decisions that turn an open-source side project into a billion-dollar company. No demos, no tutorials — just two co-hosts reading documentation, running benchmarks, and asking whether a tool's design actually makes engineers more productive or just more dependent. Past topics: the economics of API gateways, why gRPC is replacing REST in microservices, the rise of WebAssembly beyond the browser, and the hidden costs of managed Kubernetes. Listeners walk away with a concrete framework for evaluating developer tools — not as a user, but as a buyer, builder, or investor. What does it take for infrastructure software to earn the trust of engineers who have seen too many promises break in production? #DeveloperTools #APIs #Infrastructure #SoftwareEngineering #CloudComputing #OpenSourceBusiness #GRPC #WebAssembly #Kubernetes #SDKs #DevOps #PlatformEngineering #Technology #FexingoBusiness #BusinessPodcast #Business #EngineeringPodcast #TechBusiness Keep every episode free: buymeacoffee.com/fexingo© 2026 Fexingo. All rights reserved. 経済学
エピソード
  • How API Spec Languages Reduce Integration Errors

    How API Spec Languages Reduce Integration Errors
    2026/06/08
    Lucas and Luna dive into how OpenAPI, AsyncAPI, and gRPC's protobuf specs can catch integration errors before they hit production. They examine a case where a fintech startup's manual documentation led to a $2 million settlement loss, and how adopting a machine-readable spec language could have prevented it. They also discuss the trade-offs between spec-first and code-first approaches, and why even mature teams sometimes skip specs under deadline pressure. No abstract theory—just concrete examples of spec languages reducing bugs, improving developer experience, and saving money. If you've ever argued about whether to document your API before writing code, this episode is for you. #OpenAPI #AsyncAPI #gRPC #Protobuf #APISpec #IntegrationErrors #DeveloperExperience #Fintech #SettlementLoss #SpecFirst #CodeFirst #APIDocumentation #Business #Technology #FexingoBusiness #BusinessPodcast #DeveloperToolsPodcast #APIs Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    11 分
  • Why Your API Retry Logic Is Making Outages Worse

    Why Your API Retry Logic Is Making Outages Worse
    2026/06/08
    Episode 38 of The Developer Tools Podcast dives into a counterintuitive failure pattern: retry storms. Lucas and Luna walk through a real incident at a major payments API where naive retry logic turned a 50-millisecond database blip into a 47-minute cascading outage affecting thousands of merchants. They explain exponential backoff with jitter, how Stripe and AWS handle retries differently, and why idempotency keys alone won't save you. If you build or operate APIs, this episode will change how you think about reliability — and maybe save you from waking up to a PagerDuty alert at 3 AM. #RetryStorms #ExponentialBackoff #APIReliability #ResiliencePatterns #Idempotency #CircuitBreakers #DistributedSystems #CascadingFailures #DeveloperTools #BackendEngineering #SiteReliability #StripeAPI #AWSSDK #DatabaseBlips #Jitter #FexingoBusiness #BusinessPodcast #TechPodcast Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    14 分
  • How API Error Messages Cause Confusion and Wasted Time

    How API Error Messages Cause Confusion and Wasted Time
    2026/06/07
    In this episode, Lucas and Luna explore how poorly written API error messages can lead to hours of wasted debugging and even security vulnerabilities. They use the example of a major cloud provider's ambiguous 403 error that misled developers into thinking they had an authentication problem when the real issue was a missing resource permission. They discuss design principles for error messages that actually help developers, including including correlation IDs, actionable next steps, and avoiding jargon. The hosts also touch on the balance between verbose and concise responses, and share real-world stories of error messages that caused production incidents. This episode is essential listening for any engineer designing or consuming APIs. #API #ErrorMessages #DeveloperExperience #Debugging #APIDesign #ErrorHandling #DeveloperTools #RESTAPI #HTTPStatusCodes #403Error #CloudComputing #SoftwareEngineering #APIDevelopment #BestPractices #TechPodcast #FexingoBusiness #BusinessPodcast #BusinessAndTechnology Keep every episode free: buymeacoffee.com/fexingo
    続きを読む 一部表示
    13 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません