Most remote dev machine setups I've seen involve some combination of SSH, port forwarding, mounting remote drives, etc., not actually running remote desktop. So you don't RDP and open your IDE on the remote machine, you open the IDE on your cheapo laptop and use whatever SSH or remote filesystem mechanism it provides to connect it to your dev machine. Services like Tailscale make it easy to establish the connectivity between devices. Doesn't work for all dev workflows though, sometimes you're forced to use the GUI on the remote host.
Thanks for the explanation, but then an IDE just runs on a cheapo laptop with a mount even slower than hdd. I don’t get the idea of the advice then. It stops being a cheap terminal and becomes a cheap laptop?
Well, most of the IDEs still perform all of the work on the remote machine and just stream IO to the laptop, so you're not actually editing files on the laptop, you're sending file editing commands to the remote machine, all the compilation and execution stuff happens on the remote machine, etc. For example, VS Code has client/server components which make the experience feel seamless and handle network disruptions to hide latency and make it feel like it's all happening locally. This setup works pretty great if you're mostly editing text files, i.e. source code.
Actually mounting a remote disk solves a different set of problems, such as if you need to edit something that doesn't support doing the work on the remote machine or if you want to explore the remote disk in Finder or some other GUI.
It seems Grand Theft Auto fits the author's definition of a "cozy game" quite well. Particularly the open world wandering aspect of the game, where people spend significant amounts of their real-world time completing side quests and accumulating resources and buying fancy houses and cars without any real end goal. Perhaps for some degree of real-world social status among their peers. It's simply fun to participate in the markets of GTA and Animal Crossing - where the article's metaphor holds up regardless of whether time is spent stealing cars or catching butterflies.
Voxel is pushing the boundaries of applied computer vision to solve risk in physical industries. Accidents and injuries are bad for people and bad for business. Help us ensure the people who make our world go 'round get home safe, every day. Our technology addresses the key cost drivers for workers’ compensation, general liability, and property damage, which cost employers over $500 billion annually.
We have a wonderful engineering team you'll love working with and plenty of complex problems to sink your teeth into. Plus, fill your resume with trendy buzzwords by joining Voxel: AI, computer vision, the cloud, Kubernetes, distributed systems, edge computing, React, and so much more!
- Writing & communicating technical topics (i.e. how do you distill complex technical concepts to the appropriate level of detail to have meaningful discussions with the target audience; applies to all technical topics and becomes more important as you advance in your career)
- Testing (unit/integration/e2d; but more conceptually, how do you gain confidence that your code does what it's intended to do?)
Definitely agree with all of them. I didn't work at places that valued testing until fairly recently and I'm absolutely shocked that I was able to get by as long as I did without it (plenty of incidents and bugs were involved though).
Every book I've read on software develop always hits on testing and I can't believe I ignored it for so long saying "but my code is hard to test". Then it's your code's fault. If you can't write tests because the code isn't structured to do so, that means your code has bad structure IMO (I'm sure there are situations where this is trickier but they're the minority). The amount of bugs I produce has dropped dramatically since I started writing tests for almost all my code. Seriously a career changing thing that was pretty obvious but I just ignored.
So important and sets you apart from a developers who lack the ability to explain what they've done in terms of how a non-technical user/customer can understand.
