Roughly a truncated cone with diameters ~7 nuts and ~9 nuts, and the cup is ~12 nuts high (loose guesses, it is hard to tell due perspective and nuts of different sizes). Throw in an extra layer to account for the heap at the top (which is a dome taller than 1 hazelnut, but treating it as a shorter but full layer should give some error cancellation) to give a height of 13. The volume of a truncated cone of those dimensions is ~657 cubic hazelnut diameters. Random sphere packing is 64% space-efficient (though wall effects should decrease this number) giving a total of 420 nuts (nice).

Multiple edits for clarity and typos.

Arsenic is a classic murder poison. It’s been known since anciemt times, though possibly unsuited to your onset requirement. Acute poisoning by ingestion is generally within a few hours, but if your character sustains lower doses over time, you could probably draw out the timeline to whatever you wanted. It would be obvious that the character is unwell during this time, but the symptoms aren’t super specific and could be confused with e.g. food poisoning.

Or just invent a mushroom like others said. The toxins are diverse enough that I doubt anyone would be too upset if you tuned it exactly to your timeline and desired symptoms.

Cyanide poisoning is famously pretty fast though…

What a coincidence, the end of my support for windows is also approaching.

jk I scrubbed that shit from my personal devices years ago after graduating.

It doesn’t work as well spoken, though? Pretty sure Police is pronounced something like po-lee-tseh.

Also, I think you might have swapped a police with Police: “Police police, (whom) Police police police, police Police police.”

$6.49 from Giant near Philly today, and somehow still sold out. Severe inventory issues…

Ikr, I hate when people draw too many bonds to the OH in formic acid. However, that annoyance is secondary to the new contender for HAC’s position as the stupidest abbreviation for acetic acid.

Hence, Clojure. It’s not just functions that implement IFn… as the string of “cannot cast to clojure.lang.IFn” errors that I get because I couldn’t be bothered to validate my data’s shape is eager to inform me.

Related: spicy foods. I used to be basically intolerant of it but now hate eating non-spicy versions of foods I’ve grown accustomed to. Spicy peppers and hot chili powder have become a crutch for my otherwise mediocre cooking skills.

Yeah. The magnet quench flash boils a bunch of helium which is itself expensive, and presents a nice asphyxiation hazard as well. And then, assuming the quench damaged nothing, you have to set up the magnet again by getting the coils back down to superconducting temperatures… to get there, you end up boiling off a lot more helium. And then you have have to bring an engineer in to get the electrons spinning through the coil again and wait for the wobbles in the current to stabilize.

Or so I think. I work with NMR spectrometers and not MRIs, but it’s essentially the same technology.

Mitochondrion

Nah, reach is a huge advantage. I’m not sure how rapier fencing differs from regulation sabre/epée/foil, but here’s my 2 cents from that perspective:

Smaller people are not, as a rule, substantially quicker than larger. If you see any difference in your experience, it’s likely a selection bias (shorter people have to be quicker to compete at the same level). The shorter person must enter the strike range of the taller person before the taller person comes within theirs and must be significantly quicker or more skilled to overcome that dead space. If the taller person can maintain a proper distance, gg. Taller people can also lunge farther, giving a wider active range.

Targeting is a smaller issue than you make it out to be; footwork and maintaining balance, which reposition the core, are at least as important as leaning to dodge, and advantage the taller person (longer legs = more movement range). If the taller person is coming from above as you say, they can just continue their slash (sabre) downward toward that less mobile core, or squat a bit deeper if the arc won’t reach. If instead you were referring to a poke, they’re either already targeting the torso anyway (foil) or whatever body part is most easily reachable (epée; still often torso, but cheeky wrist/arm strikes can be something of an equalizer here), and anyway they are already striking at a range that the shorter person cannot, making a successful counterattack more difficult.

Besides reach, a height difference is brutal when it comes to sabre fencing; the shorter person is restricted to targeting arms and torso (can’t reach the head easily), so the taller person can anticipate strikes from fewer angles. The taller person can come from any direction and has gravity on their side for own overhead strikes. Those suck to defend against.

So could we produce a surface tension-free water?

Homie dats a gas. Or supercritical fluid, which actually is indeed used for “washing” (SC CO2 is used to decaffeinate coffee). However, like others said, surface tension /= cleaning ability. Part of what soap does is increase the effective solubility of things that are not normally soluble.

I went up to the Lake Champlain area where there was some high altitude cloud cover. Fortunately, it didn’t affect the viewing basically at all. A cool side effect of the clouds/related atmospheric conditions though was that the sun had a 22° halo. I wish that 1) I’d had a camera that could capture it and that 2) I’d had the presence of mind to pay attention to what happened to it in the moments before and after totality.

The point about stress is interesting. I’ve been playing with pronouncing the phrase, and almost everything tends toward [ɐ] when I speak the syllables one at a time, even the ones I marked with and pronounce as a schwa in normal speech. The notable exceptions are the final schwas in “obstruction” and “onions”, which tend toward [ɪ], and the -nel of “tunnel”, which is something like [nɫ] (vocalic ɫ) ~ [nəɫ].

It helps when most of the vowels are the same and most other letters match their English counterparts lol.

In case you get the urge to learn sooner:

Here are some quick refs for consonants and vowels in English (RP = received pronunciation (a standardized form of English from the UK), GA = General American). Wikipedia pages for specific English dialects (e.g., Australian English) also contain a bunch of word/IPA pairs. Here are audio charts for vowels and consonants.

yup

Thank you for reminding me of this channel, I’d forgotten about it.

Interesting about the merging. Schwa has always been weird for me because in my dialect it can be many sounds. I grew up saying “obstruction” as [ʌbstɹʌkʃɪn] like those around me. Then I hit grade school and was told by a straight-faced teacher that both the first and last syllables in this and similar words were schwas while pronouncing them differently :)

Don’t a lot of these use the “strut” vowel (/ʌ/) and not schwa (/ə/) per se?

My transcription would be

/wʌts ʌp? wʌz dʌg gənə kʌm? dʌg lʌvz bɹʌntʃ. nʌʔʌ dʌgz stʌk kəz əv ə tʌnəl əbstɹʌkʃən. ə tɹʌk dʌmpt ə tʌn əv ʌnjənz. ʊχ./

So many solver solutions that day, either Z3 or Gauss-Jordan lol. I got a little obsessed about doing it without solvers or (god forbid) manually solving the system and eventually found a relatively simple way to find the intersection with just lines and planes:

1. Translate all hailstones and their velocities to a reference frame in which one stone is stationary at 0,0,0 (origin).
2. Take another arbitrary hailstone (A) and cross its (rereferenced) velocity and position vectors. This gives the normal vector of a plane containing the origin and the trajectory of A, both of which the thrown stone must intersect. So, the trajectory of the thrown stone lies in that plane somewhere.
3. Take two more arbitrary hailstones B and C and find the points and times that they intersect the plane. The thrown stone must strike B and C at those points, so those points are coordinates on the line representing the thrown stone. The velocity of the thrown stone is calculated by dividing the displacement between the two points by the difference of the time points of the intersections.
4. Use the velocity of the thrown stone and the time and position info the intersection of B or C to determine the position of the thrown stone at t = 0
5. Translate that position and velocity back to the original reference frame.

It’s a suboptimal solution in that it uses 4 hailstones instead of the theoretical minimum of 3, but was a lot easier to wrap my head around. Incidentally, it is not too hard to adapt the above algorithm to not need C (i.e., to use only 3 hailstones) by using line intersections. Such a solution is not much more complicated than what I gave and still has a simple geometric interpretation, but I’ll leave that as an exercise for the reader :)