People getting upset about handicap spots are morons. I’m sure there is some overlap between them and those who don’t return carts.
People getting upset about handicap spots are morons. I’m sure there is some overlap between them and those who don’t return carts.
Damn. That’s some commitment.
They didn’t ask for an example of American broken thinking but you provided it anyway because it’s another thing Americans excel at.
Tell me you don’t live somewhere where it gets well below freezing without telling me you don’t live somewhere where it gets well below freezing.
Have had mutinies small children. Always put the cart away. Doors lock and children aren’t that fragile.
Anyone parking in a handicap spot is the one type of person no one should judge when they don’t put their cart away.
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.
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.
I always think of the stockholders because often I am him.
My frugal lifetime is to pirate the content and used the saved subscription price to purchase additional stock each month.
Play both sides and always come out on top, or something.