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.
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.
The bullies win.
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.
Even nomadic culture have housing they carry with them.
Or just don’t buy shit you don’t need.
With Apple the devkit would be a Mac that can run the latest version of Xcode same as any other Apple dev workflow.