2,081 karma · joined June 9, 2020
I think that's something I don't want to imagine
I use my personal laptop for $WORK and everything work related is done via the VM.
Yet they're pushing to use farmland for solar farms and social housing.
There's a real hatred of farmers among the UK Leftist/Green crowd.
This is not the same as saying there's no problem.
A fraction of humans will ever compete in the Olympics. People train their whole lives for it. It's not about 'scale', it's about safety and fairness. It's not reasonable to expect them to 'shut up' about it.
I don't want to watch a man beat up a woman in a boxing ring.
It suprises me that anything designed by the OTel community could ever meet 'low-overhead' expectations.
if (next_head == buffer.size())
next_head = 0;
partGetting into the weeds of what a compiler does with your code is fun.
People have been doing micro optimisations since computers became a thing, you benefit from them every day without realising - and seemingly not appreciating - it.
To roll back you tell GCE to use the previous image. It does all the rolling over for you.
Our deployment process looks like this:
- Jenkins: build the code to debian packages hosted on JFrog
- Jenkins: build a machine image with ansible and packer
- Jenkins: deploy the new image either to test or prod.
Test deployments create a new Instance Group that isn't automatically attached to any load balancer. You do that manually once you've confirmed everything has started ok.
A shared_mutex comes in useful when you can't really have multiple copies of the shared data due to perhaps memory usage, so readers fail to acquire it when the writer is updating it.
We didn't have to invent any homegrown orchestration tool. Our infra is hundreds of VMs across 4 regions.
Can you give an example of what you needed to do?