When Docker is up and running, code behaves the same way whether the container sits on a developer's laptop or on a remote machine. That consistency is the core draw for DevOps work: failures reproduce instead of hiding, so "production-only" bugs stop being a category. Consistency also extends to people — a team can be handed one dev environment that behaves identically across platforms, which removes the usual fights with individual machines.
The obvious conclusion would be to containerize everything, but web development is already complicated, and Docker sometimes feels like more than it's worth. The counterargument, made by Andrew Welch, is that deep Docker knowledge isn't a prerequisite for getting real work done with it.
Docker is a devops tool that some people find intimidating because there is much to learn in order to build things with it. And while that’s true, it’s actually quite simple to start using Docker for some very practical and useful things, by leveraging what other people have created.
That view has weight. Most of the technology in daily use isn't understood in depth, yet it is still usable. In this particular case, Docker is run all day for CodePen's dev environment, and that's the extent of the usage — it isn't reached for everywhere, the way Andrew does. Still, the isolation it puts between projects is easy to see as liberating.
For anyone who moves between machines, the more practical benefit is Andrew's point about portability:
Switching to a new computer is easy. You don’t have to spend hours meticulously reconfiguring your shiny new MacBook Pro with all the interconnected tools & packages you need.
Hopping between computers for one reason or another happens often enough that making the switch without fuss is genuinely appealing.



