I talked to @theprincessxena about @flydotio! We discussed building globally distributed applications with the help of Anycast, Wireguard, and Firecracker VMs.

My last interview @rubyconf is with @mayralunavarro! She shares her story of getting to this year's conference with the community's help.

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

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.

Another interview from @rubyconf💎 @davetron5000 discusses engineering at Stitch Fix, making technical decisions, outgrowing Heroku, and the role of technical books.

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

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

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.

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

@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:

A slightly extended episode and transcript are here if you prefer reading: We talked a bit about Xe's blog towards the end.

@DesignUXUI likewise!

I talked with @randyshoup about the evolution of eBay's architecture. 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 😱

I learned about building @supabase with CTO @AntWilson. It surprised me that they spin up a full EC2 instance for each database you create!

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!

@umachingunde Thanks Uma!

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.