To add to the anecdata here, I had covid for a week (bedridden but otherwise not that bad), then had a single day in which I tested negative, and then it rebounded for a week, due to Paxlovid. Sounded like it was pretty common. So that was a waste of 15 days. On the plus side, my second week was much the same as the first week as far as symptoms go.
Another example is Joe Biden, who had this exact thing happen (covid twice in a row with paxlovid).
Notable because while the chance of him just catching it again from someone are not 0, but about as low as it can go (an elderly POTUS under intense medical supervision and quarantine procedures).
The HTML source is pretty good too. A doctype that's half HTML5, half XHTML. A pre-IE7 script tag thing. A meta-keywords tag. Lists that don't actually use any list tags. Raw PHP tags being dumped into the HTML output. No closing body or html tags. This joke has _layers_, man.
I _think_ what they're saying is a specialized/curried function that takes a single argument is better than the method it's replacing that takes three strings or whatever. That is, `foo.a("a").b("b").c("c")` is better than `foo.a("a", "b", "c")`. Which...sure, but 1. if you're really passing 2-3 parameters in with identical types, maybe use inline value classes instead? Or at least type aliases?, and 2. if you can't or don't want to do that, named arguments help.
Type safe builders/factories work and should be used where appropriate (e.g. to catch invalid state at compile time) but I don't see how this has anything to do with the currying shown in the post. The compiler checks the param types whether the function has a single param or not.
Tangential, but what I appreciate about Elixir/Erlang is that you have ETS out of the box that is basically a key-value store on a lightweight Erlang process (without socket access or network calls) with flexible 'types', and then DETS brings persistence, mnesia adds schemas, queries, transactions, replication and other DBMS-like features... all this and you can use Erlang's actor model to cluster and horizontally scale, or just use it like a simple L1 cache, as described in the article
Most people use "order of magnitude" to mean "by a factor 10". I've always thought this was inappropriate. The origin of this expression is that the scientific use of magnitude implies a logarithmic scale. But "magnitude" was first used in astronomy with a scale that had a 2.5 base, not a 10 base.
Tried that game out, but found it to be realllllllllly tedious. eg initial missions took walking, while carrying some person's body over the shoulder, for "miles". Urk.
