It really depends on how you work. I can think of a couple cases that are pretty slim. 1, ssh + tmux, or something along those lines. If your stuff is all on a

It really depends on how you work. I can think of a couple cases that are pretty slim. 1, ssh + tmux, or something along those lines. If your stuff is all on a remote machine, and you're proficient with the command line tools, you can do a ton of stuff over a very thin pipe. 30k would be more than enough, but latency can be frustrating because the local echo. 2, Local dev with local docs. Something like IntelliJ and all the code lookups pointed at local javadoc. With the right setup your network use is pretty much just git fetches and pushes. When you start pulling down VMs or pushing containers, things kinda fall apart. It's worth thinking about how to slim down that network connection. Being able to work remotely with a real thin connection like that opens up a lot of opportunities. One example might be a funeral. Going home for a couple weeks vs a day or two of bereavement can be, well, nice. Obviously that kind of thing depends on your employer.