Devs not aware of where and how is their software running, while ops are not aware what they're running? That sound like a recipe for a disaster. You don't need to know everything, that's why there are separate teams... but the way it's described in the slides is slightly scary to me. I've seen people caring only about their own area and lobbing things over the wall for other teams to take out over. It never ended well.
I think it was more "I want to write my code without how it ends up packaged or deployed having influence on how I write it", and vice versa.
We definitely don't have that at my job. We have to be conscious of the dev, test, build and production environments when coding. Ops has to be more conscious of what they are deploying than they'd like. It's not that either team doesn't care about the other's work or the big picture.
If how it's deployed doesn't influence the way you write software, you're either: a) developing something trivial, or b) deploying something that's not going to work well in the long run.
I can't really argue with that. Just giving my interpretation of the slide. I still don't know Docker very well, maybe it's not as revolutionary as it seems to be.
