mjuarez
Joined 10 years ago
Joined 10 years ago
Which obviously didn't work. Or worse, made the second incident more likely.
I propose we defeat this with the obvious: Simply, figure out what are some of the markers Claude and others will use for these tools, and sprinkle them randomly on everything we type or produce, all the time, 100%. If users flood the tools, and everything returns as AI-generated, then the tools become useless.
https://www.databricks.com/blog/introducing-omnigent-meta-ha...
After that, I've been doing Systane ointment or gel, right before going to bed, and eye drops in the morning, as soon as I wake up. Every single day. The doctor said it doesn't happen overnight, it's usually a drying out over multiple days, but I'm not taking any chances.
Do yourself a favor and have a doctor check it out.
I assume Anthropic said something like "We'll give you 3% of our company for $30B, since we're valued at $1T now! So cheap!", and Google immediately came back with "Hell no. We'll give you even more, $40B... but it's for 11% of the company. Take it or leave it." With all the issues they're having, what leverage does Anthropic have at that point?
Basically, Google made them an offer they couldn't refuse.
Honestly, that was pretty surprising to me when I had to work with some telco equipment a couple of decades ago. To this day, I don't think I've encountered anything else that requires negative voltage relative to ground.
"The Vector API will incubate until necessary features of Project Valhalla become available as preview features. At that time, we will adapt the Vector API and its implementation to use them and then promote the Vector API from incubation to preview."
Project Valhalla has been "in progress" for at least a decade now (Wikipedia say 2014). So who knows when we'll actually see a Vector API in preview.
(1) https://docs.snowflake.com/en/sql-reference/functions/hash
So I took a look for about 30 mins figuring out the code (I don't know SPSS or R), and it turns out she was doing some calculations that were identical for every single line, regardless of that line's fields. So I pre-calculated a few things, prior to starting the per-record-loop, and then just used the pre-calculated values every time. After that, every run took less than 5 minutes. She's amazing at math and economics, but optimizing low-level code is not something she has done in the past.