So in an earlier post I mentioned outlined how I use a central dev machine with remote VSCode to keep one checkout of my code and develop on it, no matter what device I’m using, while maintaining a good developer experience (low latency). There’s a couple of issues that I needed to overcome while developing this approach. When developing it is common to fire up a development server that you can hit with a browser to see how the final product will behave.

I’ve been playing with using an iPad Pro as my daily driver machine recently. This is hardly new. There’s heaps of people out there doing this. I’m a coder however, so getting access to a decent development machine is important. I thought I’d collect some of the tools that I’ve been using to use the machine as effectively as possible. The iPad pro is so close to being a perfect machine.

Virtualisation is a pretty commonly known practice these days. IT operations staff use it as a method of consolidation and getting rid of old legacy hardware. Now we are being presented with virtualisation on demand facilities, usually referred to as Cloud Computing. This allows any user to create a virtual machine as a clone of a disk image at any time, use it for a while, and then throw it away.