Skip to content

Commit

Permalink
Update podcast files
Browse files Browse the repository at this point in the history
  • Loading branch information
SmartLogic Podcasts committed Oct 26, 2023
1 parent ef5d516 commit cd93120
Show file tree
Hide file tree
Showing 5 changed files with 496 additions and 1 deletion.
164 changes: 164 additions & 0 deletions _data/elixir_wizards_episodes.yml
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,170 @@
some of the topics we’ll be covering.</p>\n\n<p>Learn more about how SmartLogic
uses <a href=\"https://smr.tl/2Hyslu8\" rel=\"nofollow\">Phoenix and Elixir.</a></p>\n
\ "
- title: HTTP Requests in Elixir vs. JavaScript with Yordis Prieto & Stephen Chudleigh
slug: s11-e02-http-requests-elixir-javascript
link: https://smartlogic.io/podcast/elixir-wizards/s11-e02-http-requests-elixir-javascript
guid: 737a8ab1-50ff-4583-a522-5fb800630190
pubDate: Thu, 26 Oct 2023 07:00:00 -0400
pubDateFriendly: October 26, 2023
description: "In today’s episode, Sundi and Owen are joined by Yordis Prieto and
Stephen Chudleigh to compare notes on HTTP requests in Elixir vs. Ruby, JavaScript,
Go, and Rust. They cover common pain points when working with APIs, best practices,
and lessons that can be learned from other programming languages.\nYordis maintains
Elixir's popular Tesla HTTP client library and shares insights from building APIs
and maintaining open-source projects. Stephen has experience with Rails and JavaScript,
and now works primarily in Elixir. They offer perspectives on testing HTTP requests
and working with different libraries.\nWhile Elixir has matured, there is room
for improvement - especially around richer struct parsing from HTTP responses.
The discussion highlights ongoing efforts to improve the developer experience
for HTTP clients in Elixir and other ecosystems. \nTopics Discussed in this Episode\nHTTP
is a protocol - but each language has different implementation methods\nTesla
represents requests as middleware that can be modified before sending\nTesting
HTTP requests can be a challenge due to dependence on outside systems\nGraphQL,
OpenAPI, and JSON API provide clear request/response formats\nElixir could improve
richer parsing from HTTP into structs\nFocus on contribution ergonomics lowers
barriers for new participants\nMaintainers emphasize making contributions easy
via templates and clear documentation\nAPIs drive adoption of standards for client/server
contracts\nThey discuss GraphQL, JSON API, OpenAPI schemas, and other standards
that provide clear request/response formats\nTypeScript brings types to APIs and
helps to validate responses\nYordis notes that Go and Rust make requests simple
via tags for mapping JSON to structs\nLanguage collaboration shares strengths
from different ecosystems and inspires new libraries and tools for improving the
programming experience\nLinks Mentioned\nElixir-Tesla Library: https://github.com/elixir-tesla/tesla\nYordis
on Github: https://github.com/yordis\nYordis on Twitter: https://twitter.com/alchemist_ubi\nYordis
on LinkedIn: https://www.linkedin.com/in/yordisprieto/\nYordis on YouTube: https://www.youtube.com/@alchemistubi\nStephen
on Twitter: https://twitter.com/stepchud \nStephen's projects on consciousness:
https://harmonicdevelopment.us\nOwen suggests: Http.cat\nHTTParty: https://github.com/jnunemaker/httparty\nGuardian
Library: https://github.com/ueberauth/guardian\nAxios: https://axios-http.com/\nStraw
Hat Fetcher: https://github.com/straw-hat-team/nodejs-monorepo/tree/master/packages/%40straw-hat/fetcher\nElixir
Tesla Wiki: https://github.com/elixir-tesla/tesla/wiki\nHTTPoison: https://github.com/edgurgel/httpoison\nTesla
Testing: https://hexdocs.pm/tesla/readme.html#testing\nTesla Mock: https://hexdocs.pm/tesla/Tesla.Mock.html\nFinch:
https://hex.pm/packages/finch\nMojito: https://github.com/appcues/mojito\nErlang
Libraries and Frameworks Working Group: https://github.com/erlef/libs-and-frameworks/
and https://erlef.org/wg/libs-and-frameworks\n Special Guests: Stephen Chudleigh
and Yordis Prieto.\n"
author: SmartLogic LLC
embedUrl: https://fireside.fm/player/v2/IAs5ixts+IG633dii
enclosure:
url: https://aphid.fireside.fm/d/1437767933/03a50f66-dc5e-4da4-ab6e-31895b6d4c9e/737a8ab1-50ff-4583-a522-5fb800630190.mp3
length: '97605763'
type: audio/mpeg
itunes:
episodeType: full
season: '11'
author: SmartLogic LLC
subtitle: In today’s episode, Sundi and Owen are joined by Yordis Prieto and Stephen
Chudleigh to compare notes on HTTP requests in Elixir vs. Ruby, JavaScript,
Go, and Rust. They cover common pain points when working with APIs, best practices,
and lessons that can be learned from other programming languages.
duration: '50:29'
explicit: 'no'
keywords: " Elixir, Phoenix, LiveView, Tailwind CSS, React, JavaScript, Axios,
HTTP requests, web app development, web dev, Rails, programming, software dev,
development, app development, C sharp, data processing, software development,
computer science, engineering, algorithms, data structures, databases, distributed
systems, cloud computing, APIs, microservices, web development, full stack development,
front end development, back end development, mobile development,UX design, testing,
QA, object oriented programming, functional programming, Erlang,Ruby, Node.js,
React, TypeScript, Go, Rust, opensource, contributing, collaboration, maintenance"
image: https://assets.fireside.fm/file/fireside-images/podcasts/images/0/03a50f66-dc5e-4da4-ab6e-31895b6d4c9e/episodes/7/737a8ab1-50ff-4583-a522-5fb800630190/cover.jpg
summary: "\n <p>In today’s episode, Sundi and Owen are joined by Yordis
Prieto and Stephen Chudleigh to compare notes on HTTP requests in Elixir vs.
Ruby, JavaScript, Go, and Rust. They cover common pain points when working with
APIs, best practices, and lessons that can be learned from other programming
languages.</p>\n\n<p>Yordis maintains Elixir&#39;s popular Tesla HTTP client
library and shares insights from building APIs and maintaining open-source projects.
Stephen has experience with Rails and JavaScript, and now works primarily in
Elixir. They offer perspectives on testing HTTP requests and working with different
libraries.</p>\n\n<p>While Elixir has matured, there is room for improvement
- especially around richer struct parsing from HTTP responses. The discussion
highlights ongoing efforts to improve the developer experience for HTTP clients
in Elixir and other ecosystems. </p>\n\n<h3>Topics Discussed in this Episode</h3>\n\n<ul>\n<li>HTTP
is a protocol - but each language has different implementation methods</li>\n<li>Tesla
represents requests as middleware that can be modified before sending</li>\n<li>Testing
HTTP requests can be a challenge due to dependence on outside systems</li>\n<li>GraphQL,
OpenAPI, and JSON API provide clear request/response formats</li>\n<li>Elixir
could improve richer parsing from HTTP into structs</li>\n<li>Focus on contribution
ergonomics lowers barriers for new participants</li>\n<li>Maintainers emphasize
making contributions easy via templates and clear documentation</li>\n<li>APIs
drive adoption of standards for client/server contracts</li>\n<li>They discuss
GraphQL, JSON API, OpenAPI schemas, and other standards that provide clear request/response
formats</li>\n<li>TypeScript brings types to APIs and helps to validate responses</li>\n<li>Yordis
notes that Go and Rust make requests simple via tags for mapping JSON to structs</li>\n<li>Language
collaboration shares strengths from different ecosystems and inspires new libraries
and tools for improving the programming experience</li>\n</ul>\n\n<h3>Links
Mentioned</h3>\n\n<p>Elixir-Tesla Library: <a href=\"https://github.com/elixir-tesla/tesla\"
rel=\"nofollow\">https://github.com/elixir-tesla/tesla</a><br>\nYordis on Github:
<a href=\"https://github.com/yordis\" rel=\"nofollow\">https://github.com/yordis</a><br>\nYordis
on Twitter: <a href=\"https://twitter.com/alchemist_ubi\" rel=\"nofollow\">https://twitter.com/alchemist_ubi</a><br>\nYordis
on LinkedIn: <a href=\"https://www.linkedin.com/in/yordisprieto/\" rel=\"nofollow\">https://www.linkedin.com/in/yordisprieto/</a><br>\nYordis
on YouTube: <a href=\"https://www.youtube.com/@alchemistubi\" rel=\"nofollow\">https://www.youtube.com/@alchemistubi</a><br>\nStephen
on Twitter: <a href=\"https://twitter.com/stepchud\" rel=\"nofollow\">https://twitter.com/stepchud</a>
<br>\nStephen&#39;s projects on consciousness: <a href=\"https://harmonicdevelopment.us\"
rel=\"nofollow\">https://harmonicdevelopment.us</a><br>\nOwen suggests: Http.cat<br>\nHTTParty:
<a href=\"https://github.com/jnunemaker/httparty\" rel=\"nofollow\">https://github.com/jnunemaker/httparty</a><br>\nGuardian
Library: <a href=\"https://github.com/ueberauth/guardian\" rel=\"nofollow\">https://github.com/ueberauth/guardian</a><br>\nAxios:
<a href=\"https://axios-http.com/\" rel=\"nofollow\">https://axios-http.com/</a><br>\nStraw
Hat Fetcher: <a href=\"https://github.com/straw-hat-team/nodejs-monorepo/tree/master/packages/%40straw-hat/fetcher\"
rel=\"nofollow\">https://github.com/straw-hat-team/nodejs-monorepo/tree/master/packages/%40straw-hat/fetcher</a><br>\nElixir
Tesla Wiki: <a href=\"https://github.com/elixir-tesla/tesla/wiki\" rel=\"nofollow\">https://github.com/elixir-tesla/tesla/wiki</a><br>\nHTTPoison:
<a href=\"https://github.com/edgurgel/httpoison\" rel=\"nofollow\">https://github.com/edgurgel/httpoison</a><br>\nTesla
Testing: <a href=\"https://hexdocs.pm/tesla/readme.html#testing\" rel=\"nofollow\">https://hexdocs.pm/tesla/readme.html#testing</a><br>\nTesla
Mock: <a href=\"https://hexdocs.pm/tesla/Tesla.Mock.html\" rel=\"nofollow\">https://hexdocs.pm/tesla/Tesla.Mock.html</a><br>\nFinch:
<a href=\"https://hex.pm/packages/finch\" rel=\"nofollow\">https://hex.pm/packages/finch</a><br>\nMojito:
<a href=\"https://github.com/appcues/mojito\" rel=\"nofollow\">https://github.com/appcues/mojito</a><br>\nErlang
Libraries and Frameworks Working Group: <a href=\"https://github.com/erlef/libs-and-frameworks/\"
rel=\"nofollow\">https://github.com/erlef/libs-and-frameworks/</a> and <a href=\"https://erlef.org/wg/libs-and-frameworks\"
rel=\"nofollow\">https://erlef.org/wg/libs-and-frameworks</a></p><p>Special
Guests: Stephen Chudleigh and Yordis Prieto.</p>\n "
contentEncoded: "\n <p>In today’s episode, Sundi and Owen are joined by Yordis
Prieto and Stephen Chudleigh to compare notes on HTTP requests in Elixir vs. Ruby,
JavaScript, Go, and Rust. They cover common pain points when working with APIs,
best practices, and lessons that can be learned from other programming languages.</p>\n\n<p>Yordis
maintains Elixir&#39;s popular Tesla HTTP client library and shares insights from
building APIs and maintaining open-source projects. Stephen has experience with
Rails and JavaScript, and now works primarily in Elixir. They offer perspectives
on testing HTTP requests and working with different libraries.</p>\n\n<p>While
Elixir has matured, there is room for improvement - especially around richer struct
parsing from HTTP responses. The discussion highlights ongoing efforts to improve
the developer experience for HTTP clients in Elixir and other ecosystems. </p>\n\n<h3>Topics
Discussed in this Episode</h3>\n\n<ul>\n<li>HTTP is a protocol - but each language
has different implementation methods</li>\n<li>Tesla represents requests as middleware
that can be modified before sending</li>\n<li>Testing HTTP requests can be a challenge
due to dependence on outside systems</li>\n<li>GraphQL, OpenAPI, and JSON API
provide clear request/response formats</li>\n<li>Elixir could improve richer parsing
from HTTP into structs</li>\n<li>Focus on contribution ergonomics lowers barriers
for new participants</li>\n<li>Maintainers emphasize making contributions easy
via templates and clear documentation</li>\n<li>APIs drive adoption of standards
for client/server contracts</li>\n<li>They discuss GraphQL, JSON API, OpenAPI
schemas, and other standards that provide clear request/response formats</li>\n<li>TypeScript
brings types to APIs and helps to validate responses</li>\n<li>Yordis notes that
Go and Rust make requests simple via tags for mapping JSON to structs</li>\n<li>Language
collaboration shares strengths from different ecosystems and inspires new libraries
and tools for improving the programming experience</li>\n</ul>\n\n<h3>Links Mentioned</h3>\n\n<p>Elixir-Tesla
Library: <a href=\"https://github.com/elixir-tesla/tesla\" rel=\"nofollow\">https://github.com/elixir-tesla/tesla</a><br>\nYordis
on Github: <a href=\"https://github.com/yordis\" rel=\"nofollow\">https://github.com/yordis</a><br>\nYordis
on Twitter: <a href=\"https://twitter.com/alchemist_ubi\" rel=\"nofollow\">https://twitter.com/alchemist_ubi</a><br>\nYordis
on LinkedIn: <a href=\"https://www.linkedin.com/in/yordisprieto/\" rel=\"nofollow\">https://www.linkedin.com/in/yordisprieto/</a><br>\nYordis
on YouTube: <a href=\"https://www.youtube.com/@alchemistubi\" rel=\"nofollow\">https://www.youtube.com/@alchemistubi</a><br>\nStephen
on Twitter: <a href=\"https://twitter.com/stepchud\" rel=\"nofollow\">https://twitter.com/stepchud</a>
<br>\nStephen&#39;s projects on consciousness: <a href=\"https://harmonicdevelopment.us\"
rel=\"nofollow\">https://harmonicdevelopment.us</a><br>\nOwen suggests: Http.cat<br>\nHTTParty:
<a href=\"https://github.com/jnunemaker/httparty\" rel=\"nofollow\">https://github.com/jnunemaker/httparty</a><br>\nGuardian
Library: <a href=\"https://github.com/ueberauth/guardian\" rel=\"nofollow\">https://github.com/ueberauth/guardian</a><br>\nAxios:
<a href=\"https://axios-http.com/\" rel=\"nofollow\">https://axios-http.com/</a><br>\nStraw
Hat Fetcher: <a href=\"https://github.com/straw-hat-team/nodejs-monorepo/tree/master/packages/%40straw-hat/fetcher\"
rel=\"nofollow\">https://github.com/straw-hat-team/nodejs-monorepo/tree/master/packages/%40straw-hat/fetcher</a><br>\nElixir
Tesla Wiki: <a href=\"https://github.com/elixir-tesla/tesla/wiki\" rel=\"nofollow\">https://github.com/elixir-tesla/tesla/wiki</a><br>\nHTTPoison:
<a href=\"https://github.com/edgurgel/httpoison\" rel=\"nofollow\">https://github.com/edgurgel/httpoison</a><br>\nTesla
Testing: <a href=\"https://hexdocs.pm/tesla/readme.html#testing\" rel=\"nofollow\">https://hexdocs.pm/tesla/readme.html#testing</a><br>\nTesla
Mock: <a href=\"https://hexdocs.pm/tesla/Tesla.Mock.html\" rel=\"nofollow\">https://hexdocs.pm/tesla/Tesla.Mock.html</a><br>\nFinch:
<a href=\"https://hex.pm/packages/finch\" rel=\"nofollow\">https://hex.pm/packages/finch</a><br>\nMojito:
<a href=\"https://github.com/appcues/mojito\" rel=\"nofollow\">https://github.com/appcues/mojito</a><br>\nErlang
Libraries and Frameworks Working Group: <a href=\"https://github.com/erlef/libs-and-frameworks/\"
rel=\"nofollow\">https://github.com/erlef/libs-and-frameworks/</a> and <a href=\"https://erlef.org/wg/libs-and-frameworks\"
rel=\"nofollow\">https://erlef.org/wg/libs-and-frameworks</a></p><p>Special Guests:
Stephen Chudleigh and Yordis Prieto.</p>\n "
- title: 'Season 11 Kickoff: The Hosts Discuss Branching Out from Elixir to Compare
Notes'
slug: s11-e01-all-hosts-branching-out-from-elixir
Expand Down
Loading

0 comments on commit cd93120

Please sign in to comment.