We have a single harbor instance at work, backed by PG. The folks ran into some sort of performance issue during their testing (not documented) and their solution was to use cloud native pg, run two postgres, and add additional second layer of connection pooling.
We eventually hit a bug in a combination of certain images, docker desktop (not even supported by us), and permissions. The error looked related to the connections, so I suggested the pooler be bypassed as a test. They ignored the suggestion for two weeks until it was the last thing to test.
Sure enough bypassing the pooler helped stabilize the connection from harbor during image uploads.
Now I need to talk to them about properly vertical scaling PG before we try and run two with replication, in the same kube cluster, in the same physical data center.
I get why people blame indentation like this. I don't think it's right or wrong to ignore the tooling that directly addresses minor issues with indentation or matching braces honestly.
That said, my preference is to use the tools built into my editor and available on the CLI or web to assist and fix formatting and syntax. You get instant feedback on incorrect formatting, and I generally find that synthetic scope mistakes (regardless of method) are eliminated.
Appreciate the recommendation for the quantum thief. I really enjoyed accelerando which was a recommendation from a friend so I look forward to checking this one out. If it's good I'll share it with the same friend who taught me about accelerando.
Not the first time I've come across great recommendations in the comments of HN!
>WASHINGTON, May 12 (Reuters) - Artificial intelligence company Anthropic on Tuesday released an expanded suite of features for lawyers using its Claude AI assistant, including tools for specialized legal topics and access within Claude to other legal research and AI products.
The methanol doesn't "come out in the heads" and batch size doesn't affect the final concentration as a % because roughly the same ratio is present during a run with a slight in crease in the tails due to the with methanol bonds with water.
Under
> 7.4. Antidotes and Elimination Enhancement
> 7.4.2. Ethanol
A therapeutic blood ethanol level of about 22 mmol/L (100 mg/dL) is recommended.
...
>If ethanol was coingested with methanol and the blood ethanol level initially was >22 mmol/L (100 mg/dL), the bolus dose of ethanol can be skipped.
It's like you didn't even read your own source.
They are calling it recommended for certain conditions, and saying you can skip parts of treatment for co-ingestion!
Then in the conclusions section
> Despite its extensive use, methanol poisoning remains a critical public health concern globally, often resulting from accidental or intentional ingestion and outbreaks linked to contaminated beverages.
They've called out contaminated beverages, not outputs of distillation.
You've been had by misinformation and now you're peddling lies.
I think we need more Software Engineers, and fewer Computer Scientists.
IME, CS as a profession, doesn't need to concern itself with maintenance, secure coding practices, administration, system implementation, etc. There's no class called "maintaining this POS code base from 10 years ago."
CS folk fail when they don't make the top of a leader board for sorting algos.
Software Engineers fail if they tell you that maintenance requires 10 manual touch points over a weekend.
Different concerns. While software engineering is built upon CS fundamentals, ultimately your concern is with what's coming years down the line when your unpatched "hack week" project is underpinning the business model.
> A 10% ethanol solution administered intravenously is a safe and effective antidote for severe methanol poisoning. Ethanol therapy is recommended when plasma methanol concentrations are higher than 20 mg per dl, when ingested doses are greater than 30 ml and when there is evidence of acidosis or visual abnormalities in cases of suspected methanol poisoning.
I remember running KDE3 and it consumed too much ram for too little stability. Much worse desktop experience than today.