The Developer Tools Podcast with Fexingo · 2026-07-17 · 7 min
Lucas and Luna debate whether strict semantic versioning for APIs actually protects consumers or just creates technical debt. They use the real example of Stripe's API versioning model - explicit date-based versions rather than semver - and contrast it with the pain of maintaining major.minor.patch for REST endpoints. Lucas explains why many API teams are moving to a 'breaking changes only' approach, and why the right versioning strategy depends on whether you control your clients. Along the way, they discuss how to communicate breaking changes in changelogs, when to use URL vs header versioning, and why deprecation windows matter more than version numbers. A practical episode for anyone who's ever argued about v2 vs v3 in a code review. #API #Versioning #SemVer #BreakingChanges #Stripe #REST #BackwardCompatibility #DeveloperExperience #Changelogs #Deprecation #URLVersioning #HeaderVersioning #APIDesign #TechnicalDebt #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #DevTools Keep every episode free: buymeacoffee.com/fexingo
Why API Webhook Payloads Should Be Signed Not Verified90 / 100Why API Rate Limit Headers Confuse Every Developer90 / 100Why API Response Envelopes Waste Bandwidth82 / 100How Idempotency-Key Design Prevents Payment Disasters98 / 100Why API Error Budgets Should Be Debugging Budgets92 / 100