They are the ones that talk to the customers so the engineers don’t have to.

Often those customers are others in the same company.

NPCs? Yikes.

As opposed to you because you are not tribal and never make emotional decisions.

Reducing people like this is itself an emotional defense mechanism. We are fallible to the things you describe. All political bubbles have people who make this same exact claim about all the other bubbles.

There intelligence in recognizing this. Neither you nor I are in the one true bubble.

Based on many of the other comments, I don’t think most people understood the joke.

What exactly do you think the vm is running on if not the system kernel with potentially more layers.

The container should always be updated to march production. In a non-container environment every developer has to do this independently but with containers it only has to be done once and then the developers pull the update which is a git style diff.

Best practice is to have the people who update the production servers be responsible for updating the containers, assuming they aren’t deploying the containers directly.

It’s essentinally no different than updating multiple servers, except one of those servers is then committed to a local container respository.

This also means there are snapshots of each update which can be useful in its own way.

Quite the opposite.

The older you get the less clever it feels to point out the common mistakes of others