using remote resources as a part of your local dev flow can be very useful if your local environment is constrained on cpu/ram/gpu/ssd/bandwidth. this can be a

using remote resources as a part of your local dev flow can be very useful if your local environment is constrained on cpu/ram/gpu/ssd/bandwidth. this can be as simple as an ephemeral ec2 spot machine that reacts every time files on it’s filesystem change. it then does stuff, like building and shipping. your local setup needs to rsync files from local to remote every time you save a file. i’m on an upload constrained setup right now, and this[1] significantly speeds up my iterations uploading lambda zips. fancier setups probably are similarly advantageous, but add tradeoffs proportional to their complexity. 1. https://github.com/nathants/aws-gocljs/blob/258ea5bb72d06a5041174b7ef4522b40e21eaf8e/bin/relay.sh https://github.com/nathants/aws-gocljs/blob/258ea5bb72d06a50...