You're getting too hung up on the word "happiness". The earring gives you good advice. Good according to whom? According to you. It helps you succeed at your goals and live a fulfilling life.
[dead]
https://en.wikipedia.org/wiki/Nocebo
It's a black box, but you can run tests to quantify the behaviour and establish, for example, that a certain model is X% more likely to give a certain behaviour.
> Initially I didn’t instruct Claude to use the Socratic method, but that works much better. It’s significantly less “information-dumpy”. When I know a topic well, Claude successfully shortcuts the basics.
The password can only be compelled via a judge. A policeman can't demand it on whim.
Why would it add pressure?
Sure, but you can receive the service and also keep the money spent within the country.
I just have a black page.
It's best practice to avoid mutable defaults even if you're not planning to mutate the argument. It's just slightly annoying having to work around this by defaulting to None.
Not surprising at all if you've used LLMs to generate fiction; they always choose the same few names.
Yeah, it's a bit counter-intuitive.
> Ignoring requires-python upper bounds. When a package says it requires python<4.0, uv ignores the upper bound and only checks the lower. This reduces resolver backtracking dramatically since upper bounds are almost…
Okay, but are the puzzles fun?
> Maybe the answer is to do away with advance notice and adopt SemVer with many major versions Yes.
My toddler was playing with my Kindle the other day, and he bought a £600 (yes, six hundred) volume of books. I was unable to refund them automatically, and when looking for help I was confronted with a "fuck off"…
I was once working on a project where we had a gRPC server that inserted data into the DB for another service. This split was probably a mistake, as the interface we exposed resulted in us making twice as many DB calls…
They're not saying it is.
ok
That's weird. I thought LLMs loved over-explaining their code?
Thanks, I hate it.
"These are self-imposed limitations that fit my preferred-style for model design... I find that these constraints encourage a better designed model that can be assembled easily and predictably, including by others."…
Aphantasia gang!
Huh, I did not know about the wholesale price issue, that's pretty bad. It also incentivises avoiding cheap sources from dominating the market.
You can't switch water suppliers, so there is no such incentive to be competitive.
You're getting too hung up on the word "happiness". The earring gives you good advice. Good according to whom? According to you. It helps you succeed at your goals and live a fulfilling life.
[dead]
https://en.wikipedia.org/wiki/Nocebo
It's a black box, but you can run tests to quantify the behaviour and establish, for example, that a certain model is X% more likely to give a certain behaviour.
> Initially I didn’t instruct Claude to use the Socratic method, but that works much better. It’s significantly less “information-dumpy”. When I know a topic well, Claude successfully shortcuts the basics.
The password can only be compelled via a judge. A policeman can't demand it on whim.
Why would it add pressure?
Sure, but you can receive the service and also keep the money spent within the country.
I just have a black page.
It's best practice to avoid mutable defaults even if you're not planning to mutate the argument. It's just slightly annoying having to work around this by defaulting to None.
Not surprising at all if you've used LLMs to generate fiction; they always choose the same few names.
Yeah, it's a bit counter-intuitive.
> Ignoring requires-python upper bounds. When a package says it requires python<4.0, uv ignores the upper bound and only checks the lower. This reduces resolver backtracking dramatically since upper bounds are almost…
Okay, but are the puzzles fun?
> Maybe the answer is to do away with advance notice and adopt SemVer with many major versions Yes.
My toddler was playing with my Kindle the other day, and he bought a £600 (yes, six hundred) volume of books. I was unable to refund them automatically, and when looking for help I was confronted with a "fuck off"…
I was once working on a project where we had a gRPC server that inserted data into the DB for another service. This split was probably a mistake, as the interface we exposed resulted in us making twice as many DB calls…
They're not saying it is.
ok
That's weird. I thought LLMs loved over-explaining their code?
Thanks, I hate it.
"These are self-imposed limitations that fit my preferred-style for model design... I find that these constraints encourage a better designed model that can be assembled easily and predictably, including by others."…
Aphantasia gang!
Huh, I did not know about the wholesale price issue, that's pretty bad. It also incentivises avoiding cheap sources from dominating the market.
You can't switch water suppliers, so there is no such incentive to be competitive.