3 ms·
Isn't "setting up your environment" pretty much a one time cost, though? In my head at least, losing a couple days up front doesn't matter as much, it's the ti
by rogerdpack 10y ago
Isn't "setting up your environment" pretty much a one time cost, though? In my head at least, losing a couple days up front doesn't matter as much, it's the time after that the needs to be optimized. But maybe that's just my work place where people tend to stay on the same team for years...
- marcosdumay 10y agoShouldn't be. When you automate "setting up your environment", you are able to switch between several of them, create new ones for forks or extra tests, and roll back to debug production issues.
- infinii 10y agoIgnoring the one time aspect. It's the standardization that is important. Docker environments enforce uniformity that are beneficial for testing. No more of the "it works on my machine" excuses. Although the article mentioned development environment specifically, there is recurring benefit in being able to power up a Docker VM for testing purposes.