The point was that "republic" simply means "not a monarchy". The state is a "public thing/matter", not a private concern.

The grid has been forced to change faster than the operator would have liked it to in many places, which is a good thing.

In the main, although the Spanish national blackout just over a year ago suggests that maybe it changed too fast. (Hard to use a stronger word than "maybe" because my understanding is that the report on the causes didn't really say anything).

We are a republic for this reason.

No, you are a republic because your founding fathers, probably ascribing James III more power than he really had as a post-Glorious Revolution monarch, decided that head of state should not be a hereditary position.

Whitespace is a HUMAN affordance for a HUMAN audience. If you think it looks kinda okay, that's all that's needed.

There's a bit more to it than that: consistent whitespace means that version control diffs contain relevant changes and you don't need to filter out the changes that just remove some spaces from the end of a line. This is also really a human affordance, but while there are humans in the loop either approving changes or needing to understand when something changed, it's a valuable one. And there's a general principle here which is directly relevant to LLM-generated code, which is that until LLMs have minimising the diffs as part of their goals they're going to produce diffs which take a lot of effort for humans to review.

*head bangs in approval*

Please, no. Often when writing code I need the API reference and only the API reference. I know what I want to do and how to do it, I just need a quick check of the exact order of arguments or exact symbol names. I don't need to try to sift that out of commentary. Likewise when I'm learning how to use the library I'm more interested in the overall view. I don't need to know the exact names of the options for a call, only what the options are for. I expect the code in the user's guide to be accurate, but I don't want the same things out of it that I want out of the API reference.

Oh, forgot to link the dry density for you: here you go. 341kcal/100g. Aka 3,41kcal/g.

Which, like I said, should be obvious, since they're almost entirely carbs (~4kcal/g) and protein (~4kcal/g), and they're, as noted, dry (12-16% moisture). It would be quite the trick indeed to get something that is dry and and is almost entirely comprised of things that are 4kcal/g to be 1,38kcal/g! ;)

Just in case you need help:

Your calculation: 195g (dry weight) × 1.38 kcal/g = 269 calories per pound of cooked beans.
Correction: Because you used 1.38 kcal/g (the cooked density) as if it were the dry density, you essentially diluted the calories twice.
The Actual Math: 195g of dry beans * 3.4 kcal/g (actual dry density) = 663 kcal.

When those 195g of dry beans absorb water to weigh 454g (1 pound), they still contain those same 663 calories (since water has zero calories).

Canned beans are ALREADY COOKED. *facepalm*. You can eat them straight out of the can.

which is waaaay more than I would want to eat at a sitting.

I can't think of a single ingredient - any ingredient - that I would want to eat exclusively as my diet, so this is a really stupid argument.

Except for the bit where it does that caching for a loop where each lookup only occurs once. Because everybody caches lookups, so that must be the right thing to do (it's the most likely thing to happen) in a case where the cache is never used. Riiiiight...

Something critical to note: intent is the most important thing to document when it comes to software. You can see what it does by reading the code, that's straightforward. What I need to know most, both when writing software and maintaining it later, is why it's doing that. What's it supposed to be doing? Why is it doing it in that way? What were the alternatives and why weren't they chosen? How is it supposed to be used by code that calls it? An LLM can't generate any of that just from the code.

This is why traditionally software libraries have had two separate pieces of documentation: an API reference that details every call and it's arguments and results, and a user's guide that lays out how and why to use the library.

In general, "damping pleasure" is not most people's experience with GLP-1 agonists. What it does is more like separate pleasurable experiences from having an urgent need to continue doing them.

I'd believe the Iceland numbers. I had a doctor once who wanted to get me on antidepressants, and got mad when I didn't want to, and completely ignored my pleadings of "But I'm not depressed", "I enjoy life", "I'm probably the least depressed person you'll meet", etc. He just really liked his patients to be on it. The Icelandic medical system is very into anything that "medicates symptoms" rather than treating diseases. For example, during COVID, it was essentially impossible to get drugs like paxlovid, but they made parkodín (tylenol with codeine) over-the-counter.