
Ask Us Anything!
Explicit content warning
01/29/20 • 41 min
A while ago, we put out a call to Twitter to invite listeners to send us their questions and we would answer them. We received 4 really good questions, covering topics like supporting content negotiation, how to craft and and define an SLA for your API, why companies seem to disregard standards when it comes to their API SDKs and should you version hypermedia.
Sponsors:
Stoplight makes it possible for us to bring you this podcast while we nerd out about APIs. Check them out for their tooling around documentation with Studio, an app that makes API documentation an absolute joy to work with.
A while ago, we put out a call to Twitter to invite listeners to send us their questions and we would answer them. We received 4 really good questions, covering topics like supporting content negotiation, how to craft and and define an SLA for your API, why companies seem to disregard standards when it comes to their API SDKs and should you version hypermedia.
Sponsors:
Stoplight makes it possible for us to bring you this podcast while we nerd out about APIs. Check them out for their tooling around documentation with Studio, an app that makes API documentation an absolute joy to work with.
Previous Episode

GraphQL Monitoring and how to travel via Train
In this episode, Phil talks about how his trip across the United States via train went. We also talk about how to monitor APIs and what is the best APM solution for monitoring GraphQL endpoints. We also talk about the progress being made by the Stoplight team with both their tooling around Async APIs and also work being done on Studio.
Sponsors:
Stoplight makes it possible for us to bring you this podcast while we nerd out about APIs. Check them out for their tooling around documentation with Studio, an app that makes API documentation an absolute joy to work with.
Links:
Article: GraphQL Performance Monitoring Is Hard
Why GraphQL Performance Monitoring is hard
Phil's repo of companies working to help save the earth
Awesome Earth --- Support this podcast:
Next Episode

200 OK Boomer
Phil, Mike and Matt talk about Matt's adventures with APIs returning 200 OK while having an error message in the body, causing extra work and frustration. We look at why this is a common thing in API development and what we can do to help people utilize the codes that are there instead of relying on 200 OK.
Mike brings up Microsoft and what they are doing with their push to not only go Carbon Neutral but also Carbon Negative to make up for their past. We wonder what that will look like, and also bring up what an individual person with a developers salary can do to start helping out more since we (developers) can generally afford it over a lot of other people.
Keeping on the environment, we also take look at some things a developer can do with code to help the environment, particularly around caching and responses.
Sponsors:
Stoplight makes it possible for us to bring you this podcast while we nerd out about APIs. Check them out for their tooling around documentation with Studio, an app that makes API documentation an absolute joy to work with.
Cheers!
If you like this episode you’ll love
Episode Comments
Generate a badge
Get a badge for your website that links back to this episode
<a href="https://goodpods.com/podcasts/apis-you-wont-hate-110400/ask-us-anything-11254644"> <img src="https://storage.googleapis.com/goodpods-images-bucket/badges/generic-badge-1.svg" alt="listen to ask us anything! on goodpods" style="width: 225px" /> </a>
Copy