Images, containers, and orchestration are (historically) constructs for deployment. As a result, there’s a huge amount of history, evolution, and tooling surrounding these constructs that’s somewhat irrelevant (and a barrier to entry) for developers. Given Docker’s new focus on developers (who may not have a DevOps background), it’s worth asking how these technologies should be recontextualized and explained for development workflows.