This stuff is always so fascinating to me. I remember I was on a plane once and I had done a code deploy before getting on the flight, then remembered I forgot

This stuff is always so fascinating to me. I remember I was on a plane once and I had done a code deploy before getting on the flight, then remembered I forgot to upload the necessary files to the k8s cluster. There's no way I had enough bandwidth on a plane to get the files on the cluster. So I tried ssh-ing to my home machine and doing it from there -- nope, SSH is blocked on the stupid in-flight Wifi. So I went on DigitalOcean, got a $4 instance, and used the web interface to SSH into my home machine, and then from the home machine uploaded the files to the cluster. The latency was hilariously slow, I think over 1 second, but it worked! I was thinking about the route those packets were taking - from my computer to the plane router, up to a satellite, down to the DO data center in NY, from there to my home in NJ, then to the K8s cluster in NY, and then all the way back around. When you put it that way, one second per character isn't that bad.