Tuning Costs on my Azure Development Machine
I’ve been storing my development machines up in Azure instead of buying a new laptop. And I really like this approach. By far the most useful aspect is that I needed to completely rebuild a machine the other day to get my development tools all working properly. The conversion from an older version of my dev tools to a newer version did not go so well, and the solution turned out to be just moving to a new machine. In Azure this was trivial as I just fired up a new VM. But this is something you could do locally as well, and I’m wondering if I need to do that, because one thing I’m learning is that AZURE can be Expensive. Now by “expensive” it should be noted that I just hit $60/mo in my VM dev environment, so not actually that much money, but it’s an environment I only use a few hours per month for side work, so very expensive per hour. A couple of issues I’ve had: When you remove a VM, it doesn’t automatically remove the disks, which is maybe a good thing, but on a VM you on