nxobject

Come to think about it, if I wanted a write-once-run-forever-language, Elisp would be the ultimate language to do so...

I look forward to seeing a lifehacking hyper-optimizer streamline this to a polished daily workflow...

"I have a bucket of mud, in which I stick my hands for 15 minutes every morning.

Every weekend, I inoculate at a 1:5:5 ratio with biologically active stream dirt (after petri-dishing to check for activity), and a mix of poor-quality soil cover, and some compost; I finish by adding a 10-10-10 balanced fertilizer.

Recently, I've been seeing if there are any additional benefits to smearing all over my arms; I'm conducting a 3 month/3 month comparison experiment, with a washout period in-between...

Don't forget to buy my exclusive eBook!"

Well, I guess I'm at that point in my two-year cycle where I alternate between BBEdit and Emacs as my daily driver...

That's the reputation NSA has (had?), too.

I guess I'm going to have to be an even bigger stickler to my colleagues for computing those margins of error.

I think the burden of proof's on you to show that the "changes" mentioned by TFA will do the "resolution" you want. For now -- as a working statistician who uses Census products -- we have a lot of collateral damage that impacts our ability to reliably represent the status of the United States. As well as a sh*t publication with no one's name on it, and the expectation that the Census will publish fewer and slower going forwards.

In the non-webdev realm, it's gobsmacking that you can put "FROM debian/eol:buzz" in a Dockerfile, and it will do what it says...

As a side note, the name "MathKernel" is overloaded -- that's what Mathematica's own kernel executable is called, which is a little unfortunate when you have tooling that already refers to it.

(Just for (my) reference, the TC39 proposal is here:

https://github.com/tc39/proposal-signals)

I’m sad they’re retiring Snowball soon, though.

Speaking of learning by practice, here's two things I got a lot from:

- Take apart scrap hardware, and learn to both de-solder, re-solder, and test that you haven't pulled any pads in the process!

- Get an SMD soldering practice kit as well -- one where you have to put little bird-seed resistors flush to surfaces. It taught me a lot about how liquid solder works!

I made the mistake of thinking I'll learn while I work on the hardware I actually cared about. Big mistake.

As a taxpayer, the only silver lining here is that we won't be paying for the ballroom... /s

As a fun addition, I think the atomic clock/time standards division went HP → Agilent → Symmetricom → Microsemi → Microchip. You could have bought a HP 5071A Cesium Frequency Standard under all of these badges!

https://www.microchip.com/en-us/products/clock-and-timing/co...

Now that I think about it, I'm sure some AI lab would pay non-trivial $ for the entire wiki's full edit history.

It looks like both do standard individual covariate checks for post-match balance, with SMDs. I'm surprised they haven't assessed balance for at least pairwise interactions, too -- we should be balancing out joint risk factors too, no?

I haven't worked on these designs, but I remember the methodologist that taught me this in grad school giving us a lecture about this.

EDIT: the BMJ article (laudably) provides access to the analyis code, although I won't have time to review it:

github.com/nilskruger/Tirzepatide-and-the-Risk-of-Atherosclerotic-Cardiovascular-Events

Beyond safety concerns, it’d be sad for working users to lose some ability to understand and steer thinking, too. These are tools for us, after all.

> One other way I have been thinking of is just delay the delivery of the pages, either limit bandwidth or just wait for a bit until you deliver the page. For one user a (lets say max)3s delay on some pages is not a huge deal, however at scale that adds up and means the client can't gather other pages in the meantime

Or some kind of vintage “set up a request in a form and press a submit form, and we’ll pretend to take a while to put things together.”

> But, this “vulnerability” is the thing everybody knows about docker since forever

OP’s point exactly - it seemed somehow in their vibecoding workflow, they forgot to even do a human architectural sniff test for the stuff everyone knows. It reflects very negatively on them.

Gotcha! No, I feel the same way as well... there's no way "release" should somehow denote something bigger than "ship".

I think another classic reference: Jobs saying to the original Macintosh team - "real artists ship"!

When was that? Just went there last year - they technically never stopped the Saturday night shows during the pandemic, so we’d both have watched the same uninterrupted theatrical run…

Dick Van Dyke, dammit!

I thought about that, too. I think they’re doing this for the same reason IBM has supported Linux LPARs: since a lot of customers who lease System/z currently probably get overprovisioned hardware that they’ll never fully use, why not try a last-ditch attempt to sell the excess capacity as ARM LPARs?

Now you’re thinking like a Big Blue sales rep.

OpenAI's been building bridges with quite a few math departments these days – I'm sure they first thing they said is "please, god, no analogies"!

For one, the whole text would show up in Safari's Reader mode, so I can skip past the hilariously low UI density that AI-generated websites have these days. Before AI you'd have to go out of your way put that much CSS padding into Wordpress! If everyone's going to play Terence Tao, at least copy his stylesheet.

There used to be – pre-LLM days – a "Summarize" service that "summarized" prose to a length of your choice by deleting sentences. I'm sure it was once someone's pride and joy.

Ouch, that was indeed a typo...

I was briefly excited that people were aware they lacked the understanding.

As the article belatedly mentions, the ~40 GB automated tape library for HARVEST was the bee's knees... and possibly the inspiration for "harvest now, encrypt later".

PS – Primary sources for the IBM 7950/HARVEST on Bitsavers, excellent as always:

https://www.bitsavers.org/pdf/ibm/7950/

> She was beloved around the world, but she was an institution back home.

And the rest of the world is envious!