wppick

Even if it says milk the quality still depends on what they fed the cow that produced the milk. How much Palm oil was in the cows diet and what effect does that have on the milk. Even things like was the milk taken from an infected/inflamed utter?

Go to your grocery store and see if they have half and half or whipping cream with just milk and cream as ingredients. At lot of grocery stores I've been to don't have any cream it's a recipe with cream guar gum and a few other ingredients. They shouldn't be able to call that recipe the same name "cream". My point is even trying to just buy these ingredients is itself complicated

> It has come as a shock to some AI researchers that a large neural net that predicts next words seems to produce a system with general intelligence

When I write prompts, I've stopped thinking of LLMs as just predicting a next word, and instead to think that they are a logical model built up by combining the logic of all the text they've seen. I think of the LLM as knowing that cats don't lay eggs, and when I ask it to finish the sentence "cats lay ..." It won't generate the word eggs even though eggs probably comes after lay frequently

It's called "prompt engineering", and there's lots of resources on the web about it if you're looking to go deep on it

All tax. Income tax, payroll tax, consumption tax

Also upwards accumulation of wealth can sometimes mean less tax revenue. Middle class salary workers pay a lot of tax, so with more upwards accumulation of wealth (maybe accelerating due to AI) then what will happen to tax revenue? People getting laid off don't pay tax, and shifting that money to corporate, tax havens, and cap gains types of taxes will probably end up lower overall

Debt is just promises for future currency. One persons debt is another person asset. But what happens is when you "over promise" by accumulating too much debt then all those people with debt as their assets think they have X dollars, but if there's more debt than underlying resources can cover then it might end up all those people only end up getting like 0.65X or possibly even lower. Kind of like a bank run

> Some people are gifted in memorization of these things

Those are usually people who aren't changing languages or frameworks. Memory is mostly recency and repetition, so if you want better memory then narrowing scope is a good strategy. I'd rather go broad so that I can better make connections between things but have to always look up the specifics especially now with LLMs right there

One of the reasons I hate interviewing for software jobs is that the logic seems to be the opposite of this, and instead you should have any possible esoteric concept or possible problem ready at the top of your head instantly. And the same idea now with not allowing LLM for technical interviews

> An ounce of prevention is worth a pound of cure, after all.

  Don’t do what? Consider the primary cause of conflicts: simultaneous operations occurring on the same data on different nodes. That happens because data may not have distinct structural or regional boundaries, or because a single application instance is interacting with multiple nodes simultaneously without regard for transmission latency.

  Thus the simplest way to avoid conflicts is to control write targets

  Use “sticky” sessions. Applications should only interact with a single write target at a time, and never “roam” within the cluster.

  Assign app servers to specific   (regional) nodes. Nodes in Mumbai shouldn’t write to databases in Chicago, and vice versa. It’s faster to write locally anyway.

  interact with specific (regional) data. Again, an account in Mumbai may physically exist in a globally distributed database, but multiple accessors increase the potential for conflicts.

  Avoid unnecessary cross-node activity. Regional interaction also applies on a more local scale. If applications can silo or prefer certain data segments on specific database nodes, they should.

  To solve the issue of updates on different database nodes modifying the same rows, there’s a solution for that too: use a ledger instead

Best points are this summary near the end. IMO it's better to also allow for slower writes doing something simpler than trying to complex distributed stuff just so writes are quick. Users seem to have pretty long tolerance for something they understand as a write taking even many seconds.

The formula is usually more money and ability to work special team isolated from the usual toxic orgs. I think A9 was probably somewhat like that, and AWS probably used to be at some point long ago

One of the most interesting things to me when reading this was that it was treated as a bug even though it was that hard to reproduce. Most dev shops would not have the bandwidth and management but in to spend the time to dig into something like that unless it was high severity, and also it sounds like it was also getting caused from a modded version of the software

Kubernetes is way heavier than Erlang’s lightweight processes, so for millions of tasks at scale, a middle-ground solution could blend Erlang’s concurrency efficiency with k8s’ orchestration power, dodging containers’ overhead while keeping flexibility for diverse workloads. That's if you don't actually need the strict isolation of pods/containers and you're just trying to run something at massive scale. I don't get why so many people want to run everything as heavy container processes or pods vs coming up with a better solution. The point is we don't have to fit every problem into the shoe called kubernetes if it doesn't seem to fit, and we should look at other ways to spin up millions of processes

Try experimenting with diet like cutting out/down on sugar or salt and see if it makes any difference. There's no strong evidence that EMF can cause tinnitus but would be interesting to test that out somehow too (camping/cabin trip in a radio free zone?)