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 doe
Pitch Analysis
Required Pod Score for this show. PitchCentric checks your profile against host openness, topical fit, and audience signals before you generate a pitch.
Contact path
Verified email
Booking probability
35%
Guest openness
Selective
Verified email on file
80/100
Required Score
Sign up to generate a grounded pitch for The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers.
What is The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers?
The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers is a business podcast hosted by Fexingo, with 155 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.
About the host
Fexingo hosts The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers, a business show with 155 episodes published.
Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.
Episode #159
Why Your API Should Use Monetary Amounts as Integers
Aug 18, 202610 minS4
In this episode of The Developer Tools Podcast, Lucas and Luna explore why APIs should represent monetary amounts as integers rather than floats. They walk through real-world examples—like Stripe and Square—where cents-based integers prevent rounding errors that can cost companies millions. The hosts discuss the technical pitfalls of floating-point arithmetic, the business implications of rounding errors, and practical strategies for designing money-safe APIs, including using minor units, decimal libraries, and clear documentation. They also touch on the importance of consistent precision across integrations and how this choice impacts everything from pricing pages to accounting systems. Whether you're building a payments API or just handling prices in a side project, this episode gives you concrete reasons to ditch floats for integers and the best practices to do it right. #MonetaryIntegers #APIDesign #FloatingPointMath #PaymentsAPI #Stripe #Square #DeveloperTools #BusinessTechnology #SoftwareEngineering #Precision #RoundingErrors #DecimalHandling #MinorUnits #Cents #APIBestPractices #FexingoBusiness #BusinessPodcast #TechPodcast Keep every episode free: buymeacoffee.com/fexingo
In this episode of The Developer Tools Podcast, Lucas and Luna take a close look at conditional requests — the HTTP mechanism that lets clients ask a server 'has anything changed?' before pulling the full payload. They break down how ETags and If-None-Match headers work, walk through a real-world example from a large video-streaming platform that cut its API payloads by 38 percent, and discuss when conditional requests are a win for both the client and the server. They also weigh the trade-offs, like the extra complexity for API providers and the risk of stale data if you get the validation logic wrong. If you build or consume APIs, this episode gives you a concrete tool to reduce bandwidth, lower latency, and improve cache efficiency — and it's a conversation that bridges the gap between infrastructure and business value. #ConditionalRequests #ETags #HTTP #API #WebDevelopment #PerformanceOptimization #DeveloperTools #TechPodcast #BusinessAndTechnology #Engineering #Streaming #CacheEfficiency #LatencyReduction #BandwidthSavings #LucasAndLuna #FexingoBusiness #BusinessPodcast #TechInsights Keep every episode free: buymeacoffee.com/fexingo
Why Your API Should Use a Publish-Subscribe Pattern
Aug 16, 20269 minS4
In this episode of The Developer Tools Podcast, Lucas and Luna explore why publish-subscribe architecture is becoming essential for modern APIs. They break down how it differs from request-response, when it makes sense to use it, and how companies like Slack have leveraged it for real-time communication. You'll learn about the trade-offs between latency, consistency, and complexity, and why a pub-sub model can help you build more resilient systems. If you're an engineer or product manager evaluating event-driven design, this episode gives you a practical framework to decide if it's the right call for your next project. #PublishSubscribe #EventDriven #APIDesign #RealTimeCommunication #Slack #TechInfrastructure #DeveloperTools #TechBusiness #Engineering #SoftwareArchitecture #SystemDesign #TechLeadership #FexingoBusiness #BusinessPodcast #TechPodcast #APIs #EventStreaming #EngineeringCulture Keep every episode free: buymeacoffee.com/fexingo
How to Design an API Error Model Developers Actually Love
Aug 15, 20269 minS4
Most developers don't read API docs until something breaks. That's why the error model is the first thing they see. In this episode, Lucas and Luna dig into what makes an API error response genuinely useful, from structured machine-readable codes to human-readable messages that don't sound like they were written by a lawyer. They walk through Stripe's approach to error codes, the HTTP status code debates that never seem to end, and why the GitHub API's rate-limit error message is a masterclass in clarity. Along the way, they touch on the business case: every confusing error costs support tickets and developer trust. If you're building an API that other engineers depend on, this conversation will make you rethink your error responses — and probably your documentation strategy too. #APIErrors #DevTools #DeveloperExperience #StripeAPI #GitHubAPI #HTTPStatusCodes #ErrorHandling #APIDesign #RESTAPI #DeveloperRelations #BusinessAndTechnology #EngineeringLeadership #APIDocumentation #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering #APIBestPractices Keep every episode free: buymeacoffee.com/fexingo
In this episode of The Developer Tools Podcast, Lucas and Luna dive into event sourcing as a backend pattern that's gaining traction beyond fintech. They explain why companies like Stripe have adopted it for critical systems, how it differs from traditional CRUD, and the real trade-offs: storage costs, read model complexity, and event versioning. Using a concrete example of a payment system, they show how event sourcing lets you replay history, rebuild state, and audit everything. They also discuss when it's overkill and how to get started with tools like EventStoreDB and PostgreSQL. If you're building systems that need immutable logs, this episode is for you. #EventSourcing #BackendDevelopment #APIDesign #SoftwareArchitecture #Stripe #EventStoreDB #PostgreSQL #CQRS #PaymentSystems #TechPodcast #DeveloperTools #Infrastructure #Business #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering #SystemDesign Keep every episode free: buymeacoffee.com/fexingo
Every question we get asked before someone starts their trial.
If you have a concern about deliverability, AI quality, data privacy, or whether this will actually work for your specific situation, it's probably answered below.
What is the difference between Founder Solo and Founder Pro?
Founder Solo gives you 50 AI pitches per month using the credit model (Standard pitches cost 1 credit, Enriched pitches cost 2). Founder Pro raises that to 200 credits per month and adds full Booking Probability access, unlimited Magic Match, Apollo enrichment credits, and data export capabilities. Both plans use the same credit system, so you can stretch your monthly budget further by using Standard-mode drafting.
How do agency tiers work?
Agency tiers have no base fee. You pay per managed client and per talent profile. Agency Standard is $199 per client per month; Agency Pro is $399 per client per month. Both add $39 per talent profile per month. Your own team's user seats are always free.
What is a talent profile?
A talent profile represents one person (founder, executive, or spokesperson) you are booking onto podcasts. It includes their bio, topics, headshots, and outreach history. Team plans include 5 profiles; agency plans are pay-as-you-go.
Can I switch plans later?
Yes, at any time. Upgrades take effect immediately; downgrades apply at the end of the current billing period. Contact support if you need help migrating between plan families.
Do you offer a free trial?
Every paid plan includes a 15-day free trial. Your card is saved at signup but you will not be charged until day 16. Cancel any time from your dashboard.
What happens if I cancel?
You keep access until the end of your current billing period. No charges after that. Your data is retained for 30 days in case you reactivate.
Is the 20% annual discount automatic?
Yes. Select Annual on the pricing toggle and the discounted price is applied automatically at checkout. The annual price shown is the full year cost.
What if I have more than 50 profiles or 20 clients?
That is our Enterprise tier. Contact our sales team and we will build a custom plan with volume pricing, a dedicated account manager, and SLA guarantees.
