274 karma · joined March 1, 2018
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.
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.
Netflix is now an ad/ tech company.
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.
Discoveries are often statistical in their nature about how uncertain the are.
Use self hosted runners if you are worried about costs or have special requirements.
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.
Sometimes the rabbit holes you might encountered aren't interesting.
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.
We are rich in compute and we don't feel the need to optimize anymore. Optimization is an afterthought or a never thought and features run the world.
It's nice to finally get some comms, but this is incredibly late and incomplete.
If the bash script is ran on thousands of containers where its not possible to babysit. My number one job is to stop immediately when an error happens and surface that error to any monitoring system.
Why the hell am I getting targeted?
It's worrying that your uptime indicates you don't patch frequently.
We keep track of our monthly recurrent bills. We limit this increase as much as we can. This all comes out of a special checking account. Beginning of month we transfer bills to this from savings. Currently about 40 percent of our income goes to this.
Entire paychecks go into "savings". This is used to transfer to other "budgets".
Also each paycheck has certain HSA, and retirement savings deductions withdrawn. We don't pay attention to this.
We each have our own debit card that we "pay" ourselves with. This is approximately 10 percent of our income. We use this for expenses such as eating out, hobbies, small individual expenses that we don't want to justify to each other.
The remaining money we have an agreement that we must discuss any decisions with each other before using.
There are problems with this method, and sometimes we cheat, or use credit cards. But we have long term goals and love each other and strict money management isn't as important as having a happy relationship without having to constantly worry.
These do reduce, but don't elimate incidents.
Unilateral change blocks, stink, but don't put support in the weird position of taking on something they can't.
I could see this really changing how users interact with each other.