1,638 karma · joined July 28, 2020
In an expanding universe, energy isn't conserved. (Unless we do the trick we always do with energy and just define it to be conserved https://youtu.be/lCgKTpIzjRk?t=174 )
I don't know exactly why you think this applies to charge conservation. The U(1) symmetry is where charge conservation comes from and it isn't affected by an expanding universe.
However, my post sucked and I didn't get around to emphasizing that. In quantum mechanics, it's possible for some state to have zero probability, and it's those probabilities that we're talking about everything being possible.
There's also the epistemic side where we know that there's a chance our theories are wrong in any given way. Those can't go to zero based on our model since the whole point is we're not restricting to a model. BTW, I really like your example as a good, clean limiting case.
-------------
I'm sure people have come up with theories that violate conservation of charge, but they'd have to break U(1). I don't know what conservation CPT would break, if any; Noether's theorem shouldn't apply to it as a discrete symmetry.
Kaiser is an HMO. They are the insurer and try to have their employees, such as these nursing lines, perform almost all of their care. Shifting from one line of business to another is purely internal and can't game Medical Loss Ratio like your scenario.
> they don’t have much incentive to lower total cost because 20% of a larger number means more total profit
There is some bad incentive here for sure. That being said, insurers do compete on price so they lose customers if they charge more than other insurers. Also, regulatory rate review can decide whether they can raise premiums a given amount.
This doesn't seem like a money-saving measure exactly. The main AIs the article talks about is making sure nurses on their nurses' lines aren't being assholes. I guess this used to be spot checked before so you save on that? Maybe? It seems like they are trying to solve the problem of some of their nurses staffing their nurses' line not treating their patients the way they're supposed to.
I think normal people are more likely to have the experience where they can't remember a name and why/how/where they know someone from. I of course forget things like anyone, but that's unrelated.
Every once in a while I don't recognize someone and I go through this whole thing of bringing up every biographical detail about them I remember and all the things we've talked about to show that I'm not an asshole who wasn't paying attention in the past. Fortunately, I have a decent memory for such things.
But also, I suspect the article is just wrong. "The hard languages got easy first" isn't true in practice and the impressive examples given are not representative or as magical as the poster makes them out to be.
The takeaway might be right in the end, but the post isn't right in the beginning.
I'm not sure this is true.
Sometimes. Sometimes they practice by text or phone.
> They’re also good at extracting information in a way that (at least currently) sycophantic LLMs don’t replicate.
If I had to guess, I think I'd guess that mainstream LLM chatbots are better at getting honest and applicable medical histories than most doctors. People are less likely to lie/hide/prevaricate and get more time with the person.
One of the things I respected OpenAI for at the release of ChatGPT was not trying to prevent these topics. My employer at the time had a cutting-edge internal LLM chatbot for a which was post-trained to avoid them, something I think they were forced to be braver about in their public release because of the competitive landscape.
It's definitely striking, I can't deny that. I crossed the last remnants of an almost-extinct glacier last year that my guide guessed would be gone in 1-3 years: at the beginning of his career it was a real glacer with non-trivial extents, crevasses, etc.
Wikimedia also seems to have a presence in the UK https://wikimedia.org.uk/ that presumably would be affected.
In most cases they might have enough pull to get folks blacklisted by payment processors, but wikimedia in particular might win that one.
with sql_context(columns="x"):
query, values = sql(t"SELECT {col} FROM y")
I think1. this is relying on the `col = "x"` in the previous example
2. columns is a set of strings, so it might be sql_context(columns={"foo", "bar", "x"}) to allow those as valid options. It just happens that "x" is a collection supporting the `in` operator so it works much like the set {"x"} would.
2a. (You might hope that something would convert such a string to a singleton set, but I don't think it does, which would have weird results with a multi-letter string.)