APIs You Won't Hate

{{ show.title }}Trailer Bonus Episode {{ selectedEpisode.number }}
{{ selectedEpisode.title }}
|
{{ displaySpeed }}x
{{ selectedEpisode.title }}
By {{ selectedEpisode.author }}
Broadcast by

Summary

Why are HTTP status codes so hard, and also we look at what Microsofts push to go carbon neutral really means and how individual people can implement small changes to have an impact on the environment.

Show Notes

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.

Huge thank you to Stoplight.io for sponsoring our podcast! Check them out if you are doing any kind of API development, the tools that the Stoplight developers create kick ass. 

Cheers!

★ Support this podcast on Patreon ★

What is APIs You Won't Hate?

A no-nonsense podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes.