Remember the old joke about how everything in software can be fixed by another layer of abstraction, except too many layers of abstraction? Docker in a dev setting is just adding another layer of abstraction without solving the underlying problems.<p>We recently experienced exactly the scenario described in the article when on boarding our team with a customer. At first it looks slick to be up and running so fast. The problem is, you still have to keep that Dockerfile updated correctly so you'd better understand your dependencies. You still have to have redis, postgresql, and whatever other system dependencies installed. The moment you need to update your application that causes a need to update your docker images means that a 30 second fix just turned into a bigger administrative deal.<p>Want to use containers in production? Go for it, have fun. Do I think you need better dependency management and a clear way to keep developer environments in sync? Absolutely. I'm just not yet convinced Docker itself is adding anything to that problem.