4 ms·
It's not for you, it's for every new hire. You can always build on top of the base image, but it sets a nice lower bound and gets people started fast.
by WaxProlix 4y ago
It's not for you, it's for every new hire. You can always build on top of the base image, but it sets a nice lower bound and gets people started fast.
- eikenberry 4y agoProblem is with people who put together these sorts of systems tend to think theirs is best and everyone should use it. For example I once interviewed at a place where every developer got an identical Mac with the dev environment already setup and you couldn't use something else as they thought it better if everyone had the same setup to enable easier pairing. I could really see something similar happening with these systems.. seems like the kind of setup that would have appealed to that company I interviewed at.
- spicybright 4y agoSetting up a working dev environment can take days to a week+ in my experience. On boarding can take a while, so getting a VM image or whatever that works out of the box that you can build on is a really good thing. It's great too because if your own environment breaks, you can compare to a working one to fix it. Just because a company might abuse it doesn't mean we should avoid it.
- eikenberry 4y agoI have no problem with the idea of having a pre-existing image to kick off your dev setup. Just more that, human nature being what it is, it is unlikely to stop there. It will vary from company to company of course and I think my current company would adopt it in a good way but I also can think of one or two previous employers who would politicize and abuse the idea. IE. it's no slam dunk. Like any other tool of this sort is will be used for good and ill.