longcommonname

Level 0. Use infra like kafka, and eventing to replicas.

I've found the exact opposite. We have lots of gcp cloudsql instances. Each team handles their own dbs for however they decide to split their services.

Our operational costs are more distributed, they are more but they indicate the cost of each product and they separate our data very well.

Teams can do their own migrations, and we can prevent some rogue service from violating the data.

We are currently in progress for a very large migration from what you have. But I'm sure we just did it wrong.

Wonder what this means for the tax implications and if it puts them below the threshold that they agreed to employ.

Absolutely not. I have learned all sorts of things. But I have to seek them out.

More research should be done around detransitioners. Doctors need to evaluate the whole patient and in the case of informed consent they should confirm that the patient is aware of all the potential changes.

That being said, gate keeping what I do with my body is wrong. I knew all the potential side effects when I transitioned. I read the wpath in full. I was comfortable with all the risks.

This type of critical judgment of children's health care is needed and I hope the doctors are being more rigorous than what the author suggests.

I feel terrible for the girls who made a decision they regret and lost parts of their body that made them happy. Their doctors, and parents failed them. I am also happy that so many people were able to successfully transition.

The timing of the article is concerning with so many states trying to withhold life saving care I worry that the nuance of this article will be lost.

Would you provide a summary of how you noticed the increased traffic and how you found this post?

Disney is primarily an entertainment company and focuses on users enjoyment.

Netflix is now an ad/ tech company.

I am a trained military lab tech, military chef and I now do computer things as a civilian.

My military training included all those things. When you are feeding a war / humanitarian effort / training you have very little budget to provide a meal that hundreds will want to enjoy in a safe manner.

Don't minimize the knowledge/ effort required to do this.

Models based on our understanding of the world provide a level of certainty lower than experimentation but still scientifically valid.

Discoveries are often statistical in their nature about how uncertain the are.

This is possible with github actions. Have one job create a matrix of other jobs for each of your runners.

Use self hosted runners if you are worried about costs or have special requirements.

Try gcsfuse to write logs to a bucket.

It's the one thing I like about our airflow. Everything else you said is echoed.

Also, the toil of dealing with many airflow instances when you have engineers who don't want to automate it.

Seems like prioritizing the common good is in line with big aggro if we don't care about the independent farmers this could impact.

He could have gotten a sponsor, or just didn't care about that part of the problem.

Sometimes the rabbit holes you might encountered aren't interesting.

The biggest difference between the two is how it runs.

If you have many clusters then you get to chose between many or one argocd instance. We run a few argo instances that manage many clusters.

If you use flux, all of cluster needs to have access to github. If you run argo you can restrict it so that the argo cluster (which manages many others) only needs access.

You still have to have argo get access to the child clusters.

I prefer the simplicity of flux, I like the read only ui of argo.

The thing I really don't like about argocd is that you have to give the parent cluster admin to every cluster it manages. If you use git webooks you've now had to expose your controller that can manage your fleet to the public.

Argocd also randomly has really bad bugs show up. Like completely ignoring appsets. Or pathological syncing cases.

Ads are their own form of entertainment.