Artwork

Content provided by Jake Hopking. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jake Hopking or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

How do we unbundle the Jamstack, thoughts on meta-frameworks, Toast and Party Corgi with Chris Biscardi

1:40:43
 
Share
 

Manage episode 267918407 series 2761562
Content provided by Jake Hopking. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jake Hopking or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

UIT 6: In this week’s episode I talk with Chris Biscardi about the Jamstack, gatsbyJS and his own meta-framework called Toast, amongst many other interesting digressions :)
Overview

  • Introduction
  • JamStack
  • Toast
  • Party Corgi
  • MDX Conf
  • Wrap Questions

Introduction
Got into the industry via ActionScript, then moved over JS when Adobe killed it off. Worked at Docker, Dropbox and recently finished a contract with GatsbyJS.

Talk a bit about the Party Corgi Podcast, and the rainbow corgi logo (which is cute). Chris shares that he has nerves with his podcast too (after I apologies for a few nervous erm/ahhs etc). I’ve left these in unedited because the conversation took a nice direction.
What is the Jamstack
Jamstack and serverless are pretty much the same thing, and are both associated with Build vs Buy Paradigm i.e. if the technology is your core competency then build it, else buy it.

It’s basically the reduction in complexity associated with large devops pipelines i.e. you’re not running a kubernetes or large distributed infrastructure. Instead you’re basically shipping a zip file that’s then deployed on to Amazon S3 or a CDN, and you’re serving a bunch or static files. All the compute necessary to generate your site is done at build time.

A reasonable understanding of where the reduction in complexity ends up; is instead with the developer. One may have removed the need for a server to host a dynamic site with databases etc, but the same functionality has to be achieved at build time in a way that shouldn’t be too complex for the developer.
Full show notes available at https://uitherapy.fm/episodes/6

Full show notes available at https://uitherapy.fm/episodes/6

Support the show
  continue reading

8 episodes

Artwork
iconShare
 
Manage episode 267918407 series 2761562
Content provided by Jake Hopking. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Jake Hopking or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

UIT 6: In this week’s episode I talk with Chris Biscardi about the Jamstack, gatsbyJS and his own meta-framework called Toast, amongst many other interesting digressions :)
Overview

  • Introduction
  • JamStack
  • Toast
  • Party Corgi
  • MDX Conf
  • Wrap Questions

Introduction
Got into the industry via ActionScript, then moved over JS when Adobe killed it off. Worked at Docker, Dropbox and recently finished a contract with GatsbyJS.

Talk a bit about the Party Corgi Podcast, and the rainbow corgi logo (which is cute). Chris shares that he has nerves with his podcast too (after I apologies for a few nervous erm/ahhs etc). I’ve left these in unedited because the conversation took a nice direction.
What is the Jamstack
Jamstack and serverless are pretty much the same thing, and are both associated with Build vs Buy Paradigm i.e. if the technology is your core competency then build it, else buy it.

It’s basically the reduction in complexity associated with large devops pipelines i.e. you’re not running a kubernetes or large distributed infrastructure. Instead you’re basically shipping a zip file that’s then deployed on to Amazon S3 or a CDN, and you’re serving a bunch or static files. All the compute necessary to generate your site is done at build time.

A reasonable understanding of where the reduction in complexity ends up; is instead with the developer. One may have removed the need for a server to host a dynamic site with databases etc, but the same functionality has to be achieved at build time in a way that shouldn’t be too complex for the developer.
Full show notes available at https://uitherapy.fm/episodes/6

Full show notes available at https://uitherapy.fm/episodes/6

Support the show
  continue reading

8 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide