Jeremy Jung

host on and @seradio

[Jeremy Jung @jertype]

I talked to @theprincessxena about @flydotio!

We discussed building globally distributed applications with the help of Anycast, Wireguard, and Firecracker VMs.

https://t.co/ScFq1jsl7T

[Jeremy Jung @jertype]

My last interview @rubyconf is with @mayralunavarro!

She shares her story of getting to this year's conference with the community's help.

https://t.co/zg16J4QPBr

[Jeremy Jung @jertype]

Next is @getajobmike!

We talked about the @rubyconf keynote, running a solo business, and funding open source.

https://t.co/AWp5NcI4Nt

[Jeremy Jung @jertype]

Next @rubyconf I met @thoughtbot team lead Sara Jackson!

We discussed being a professor in Japan, giant LAN parties @RITtigers, and joining the Ruby community.

https://t.co/ti58wR7TVW

[Jeremy Jung @jertype]

Another interview from @rubyconf💎

@davetron5000 discusses engineering at Stitch Fix, making technical decisions, outgrowing Heroku, and the role of technical books.

https://t.co/26mliWjwJP

[Jeremy Jung @jertype]

@ChaelCodes @rubyconf @OneDreamerGame Thanks and likewise! You're a pro. You made it easy for me 😄

[Jeremy Jung @jertype]

I met @ChaelCodes while @rubyconf!

We talked about her love of programming games and how streaming games and open source on twitch led her to a voice acting role in @OneDreamerGame

https://t.co/ghsnaOlth2

[Jeremy Jung @jertype]

I talked to @lcasdev about @deno_land!

We discussed why it's hard to ship features in Node and the benefits of web standards for server-side JavaScript

https://t.co/XUDMDNtzFr

[Jeremy Jung @jertype]

I spoke to @RheingoldRiver about running the @TheLeaguepedia eSports wiki.

She explains why providing a good experience for editors matters more than the cleanliness of the code base.

https://t.co/lkUWvfBZfd

[Jeremy Jung @jertype]

I spoke to @vadosware about his preferred stack, learning and choosing technology, and why good project pages have comparisons to other projects

https://t.co/1JPrjHFFHr

[Jeremy Jung @jertype]

@theprincessxena @transgingerjess @Esper_Lily The ffmpeg output is fine but you have to use the native Safari HLS support instead of HLS.js.

Take a look at the "else if" section here: https://t.co/VRMEu4uk4V

[Jeremy Jung @jertype]

A slightly extended episode and transcript are here if you prefer reading:
https://t.co/aDr6OZ6lAV

We talked a bit about Xe's blog towards the end.

[Jeremy Jung @jertype]

It's hard to imagine loving a corporate VPN but @theprincessxena makes a pretty good case for why @tailscale isn't a Virtual Pain Network!

https://t.co/KlPaQ6gLng

[Jeremy Jung @jertype]

@DesignUXUI likewise!

[Jeremy Jung @jertype]

Can poorly designed software be life threatening?

@designuxui explains how bad UX in critical markets like the medical industry can be fatal

https://t.co/SqMsP8uBDS

[Jeremy Jung @jertype]

I talked with @randyshoup about the evolution of eBay's architecture.

https://t.co/1YlDJzp10H

It used to be 3.4 million lines of C++ in a class so big that they hit compiler limits on the number of methods per class 😱

[Jeremy Jung @jertype]

I learned about building @supabase with CTO @AntWilson.

https://t.co/e1iyPY3Ndj

It surprised me that they spin up a full EC2 instance for each database you create!

[Jeremy Jung @jertype]

I spoke to @JasonSwett about testing applications.

What stood out to me?

He wrote a book on rails testing but couldn't remember the difference between stubs and mocks because he rarely uses them!

https://t.co/Tf5GGoj5Gi

[Jeremy Jung @jertype]

@umachingunde Thanks Uma!

[Jeremy Jung @jertype]

A public PaaS can't debug customer source code and needs robust abstractions.

Internal compute teams build a "good enough" solution but get stuck debugging their user's code.

@umachingunde thinks internal compute should be treated as a public product.

[Render @render]

Render's @umachingunde joined @jertype on @seradio 📻 to compare building a PaaS with her previous experience running the Stripe Compute team. https://t.co/YFEjHJu0uZ