140: Developer Burnout and Infrastructure as Code with Ronak Rahman

Burnout in the tech industry is a very prominent concern among both leaders and developers alike. Ronak Rahman, Developer Relations Manager at Quali, joins Patrick and I in this episode to share his experience, and why having the right infrastructure in place can prevent work-life erosion (plus sticker shock with cloud service bills)!

 

00:00:57 Introductions

00:01:51 How Ronak got started in programming

00:06:03 The first encounter with burnout

00:11:49 Double-edged benefits

00:17:23 Spoon theory

00:19:07 Why relationship clarity matters

00:25:11 A cold room story

00:30:59 Context switching’s relevance

00:35:45 QTorque’s solution to monitor cloud automation costs

00:39:19 Setting up lifetimes

00:42:17 Bom lists

00:49:19 How Quali helps with the challenges

00:54:40 What to do to actualize your true self

00:58:00 Farewells

Resources mentioned in this episode:

 

Ronak Rahman:

• Twitter: https://twitter.com/ofronak

 

Quali:

•       Website: https://www.quali.com/
•       Linkedin: https://www.linkedin.com/company/qualisystems/
•       QTorque Free Tier: https://www.qtorque.io/pricing/
•       Join QTorque: https://portal.qtorque.io/join

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/

 

Reach out to us via email: programmingthrowdown@gmail.com

 

You can also follow Programming Throwdown on 

Facebook | Apple Podcasts | Spotify | Player.FM 

 

Join the discussion on our Discord

Help support Programming Throwdown through our Patreon

139: Scientific Python with Guido Imperiale

Coming off the heels of the scientific python conference, we are delighted to have Guido Imperiale, OSS Engineer at Coiled, to talk with us about this exciting space, including his own work on Dask, remote work benefits, and how distributed computing with the latest Python tools has allowed him to manage large data science projects with ease. 

00:00:45 Introductions

00:02:22 The sluggish Python-based system that Guido revitalized

00:06:03 Meeting the challenge of adding necessary complexity to a project

00:11:59 Excel in banking

00:18:15 Guido’s shift into Coil

00:19:29 Scooby-Doo pajamas

00:20:21 What motivates people to come in to the office today

00:24:09 Pandas

00:35:35 Why human error can doom an Excel setup

00:39:29 BLAS

00:46:20 A million lines of data

00:51:43 How does Dask interact with Gambit

00:54:40 Where does Coil come in

00:59:34 The six-o-clock question

01:03:53 Dealing with matters of difficult decomposition

01:12:07 The Coil work experience

01:15:37 Why contributing is impressive

01:20:20 Coil’s product offering

01:21:19 Farewells

Resources mentioned in this episode:

Guido Imperiale:

• Github: https://github.com/crusaderky

Coiled:

• Website: https://coiled.io

• Careers: https://coiled.io/careers/
  
  
  

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/

Reach out to us via email: programmingthrowdown@gmail.com

You can also follow Programming Throwdown on 

Facebook | Apple Podcasts | Spotify | Player.FM 

Join the discussion on our Discord

Help support Programming Throwdown through our Patreon

138: Fixing the Internet with John Day

In the second part of a two-episode special, Professor John Day continues to share his stories from the early days of the internet. From the debate surrounding IPv6, different methodology around network design, and John’s own career advice, there’s tons of wisdom and practical experience to be gained here!

 

00:00:24 Introductions

00:00:49 IP v6

00:04:50 OSI

00:12:53 The IP v7 debate

00:20:18 The definition of an address’s scope

00:21:38 Why John feels DNS was a mistake

00:26:40 How IP mobility works

00:32:13 Bluetooth 

00:41:41 Where will Internet architecture go from here

00:49:49 Understanding the problem space

00:59:04 The angels in the details

01:00:53 Scientific thinking vs engineering thinking

01:04:01 Victorian architecture

01:06:11 John’s career advice

01:11:18 Garbage Can Model

01:14:38 How to make the most out of college today

01:27:05 Farewells

Resources mentioned in this episode:

 

Professor John D. Day:

• Wikipedia: https://en.wikipedia.org/wiki/John_Day_(computer_scientist)
• Website: https://www.bu.edu/met/profile/john-day/
• Book: https://www.oreilly.com/library/view/patterns-in-network/9780132252423/

Terminologies:

• CIDR: https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
• OSI: https://en.wikipedia.org/wiki/OSI_model
• Connectionless Network Protocol: https://en.wikipedia.org/wiki/Connectionless-mode_Network_Service
• SIP (Session Initiation Protocol): https://en.wikipedia.org/wiki/Session_Initiation_Protocol
• Garbage can model: https://en.wikipedia.org/wiki/Garbage_can_model

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/

 

Reach out to us via email: programmingthrowdown@gmail.com

 

You can also follow Programming Throwdown on 

Facebook | Apple Podcasts | Spotify | Player.FM 

 

Join the discussion on our Discord

Help support Programming Throwdown through our Patreon

137: The Origins of the Internet with John Day

Computing has certainly come a long way from punch cards and literal system bugs – yet there is so much more to learn. Professor John Day shares his stories from the heyday of the computer revolution, the challenges that they faced, and what he’s been up to lately, among others. This first part of a two-episode special is a rare treat with a pioneer, and one that people in the tech industry shouldn’t miss.

 

00:01:01 Introduction

00:01:28 COVID and the challenge of teaching

00:04:11 John’s academic and career path

00:08:14 LSI technology

00:12:13 Collaborative software development in the day

00:15:24 ARPANET’s early use

00:20:08 Atom bomb and weather simulations

00:26:55 The message-switching network 

00:34:57 Pouzin

00:38:00 Every register had a purpose

00:45:15 The Air Force in 1972

00:52:10 Low memory

00:59:14 Early problems with TCP

01:11:51 The separation of mechanism and policy

01:23:25 Farewells

Resources mentioned in this episode:

Professor John D. Day:

• Wikipedia: https://en.wikipedia.org/wiki/John_Day_(computer_scientist)
• Website: https://www.bu.edu/met/profile/john-day/
• Book: https://www.oreilly.com/library/view/patterns-in-network/9780132252423/

 Pouzin Society:

•  Website: https://pouzinsociety.org/
•  Twitter: https://twitter.com/pouzinsociety

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/

 

Reach out to us via email: programmingthrowdown@gmail.com

 

You can also follow Programming Throwdown on 

Facebook | Apple Podcasts | Spotify | Player.FM 

 

Join the discussion on our Discord

Help support Programming Throwdown through our Patreon

136: Metaverse with Daniel Liebeskind

Decentralizing the future can often lead to missing out on genuine human communication. Daniel Liebeskind, Cofounder and CEO of Topia, talks about how they’re working to avoid that pitfall while building the foundation of a better online experience. Whether its his lessons from Burning Man, keeping the human spirit alive in today’s technological frontier, or how Topia fits in the future, Daniel has something for listeners.

00:01:34 Introduction

00:02:15 Daniel and early programming experience

00:07:51 How coding felt like sorcery

00:09:35 Skill trees

00:16:10 Second Life

00:19:56 Enhancing versus replacing real life experiences

00:26:28 A decentralized Metaverse

00:29:54 Web 2 versus Web 3 

00:34:15 /r/place

00:44:16 Why boom cycles are important for tech

00:46:03 Topia for consumers

00:52:47 Topia as a company

00:55:50 Opportunities at Topia

00:58:00 Topia.io

01:03:50 Farewells

Resources mentioned in this episode:

Daniel Liebeskind, Cofounder and CEO of Topia:

• LinkedIn: https://www.linkedin.com/in/dliebeskind/
• Website: https://medium.com/@dliebeskind
• Twitter: https://twitter.com/dliebeskind

Topia:

• Website: https://topia.io/topia/careers
• LinkedIn:  https://www.linkedin.com/company/topia-io/

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/

Reach out to us via email: programmingthrowdown@gmail.com

You can also follow Programming Throwdown on 

Facebook | Apple Podcasts | Spotify | Player.FM 

Join the discussion on our Discord

Help support Programming Throwdown through our Patreon

135: Kubernetes with Aran Khanna

Not sure how to take the website or service you built on your machine and put it in the cloud? Kubernetes is by far the most popular system for deploying applications, but it is also pretty intimidating for new developers. In this episode, we are joined by Aran Khanna from Archera to explain how Kubernetes works and how you can go from n00b to expert in Kubernetes in less time than it takes to say "works on my machine"!

00:00:15 Introduction

00:01:03 Aran Khanna and his background

00:05:12 The Marauder’s Map that Facebook hated(Chrome Extension)

00:20:11 Why Google made Kubernetes

00:31:14 Horizontal and Vertical Auto-Scaling

00:35:54 Zencastr

00:39:53 How machines talk to each other

00:46:32 Sidecars

00:48:25 Resources to learn Kubernetes

00:52:59 Archera

00:59:31 Opportunities at Archera

01:01:08 Archera for End Users

01:02:30 Archera as a Company

01:05:46 Farewells

 

 

 

134: Ephemeral Environments with Benjie De Groot

Download

How do you test changes to your web backend or database?  Many people have a "production" and one "development" database, but the development database can easily become broken by one engineer and thus unusable for the rest of the team.  Also, how would two engineers make changes in parallel to the development environment?  What if you could spin up hundreds or thousands of development databases as you need them? Today we have Benjie De Groot, Co-Founder and CEO of Shipyard to explain ephemeral environments and how virtual machines and containers have made massive improvements in devops!

 

00:00:15 Introduction

00:00:24 Introducing Benjie De Groot

00:01:26 Benjie’s Programming Background

00:06:34 How Shipyard started

00:09:17 Working in Startups vs. Tech Giants

00:19:28 The difference between Virtual Machines and Containers

00:26:17 Local Development Environment

00:40:27 What is a DevOps engineer and what does it entail?

00:45:42 Zencastr

00:50:12 Shipyard as a company

00:55:29 How Shipyard gets clients

01:06:48 Farewells

 

Resources mentioned in this episode:



Benjie De Groot, Co-Founder & CEO at Shipyard:

• LinkedIn: https://www.linkedin.com/in/bueller/
• Podcast: https://www.heavybit.com/library/podcasts/the-kubelist-podcast/

Shipyard:

• Website: https://shipyard.build/
• Careers: https://shipyard.build/careers/
• LinkedIn: https://www.linkedin.com/company/shipyardbuild/
• Twitter: https://twitter.com/shipyardbuild
• Community Website: https://ephemeralenvironments.io/
• GitHub: https://github.com/shipyard

Heavybit:

• Website: https://www.heavybit.com/
• LinkedIn: https://www.linkedin.com/company/heavybit/
• Twitter: https://twitter.com/heavybit

If you’ve enjoyed this episode, you can listen to more on Programming Throwdown’s website: https://www.programmingthrowdown.com/



Reach out to us via email: programmingthrowdown@gmail.com



You can also follow Programming Throwdown on

Facebook | Apple Podcasts | Spotify | Player.FM



Join the discussion on our Discord

Help support Programming Throwdown through our Patreon