mjuarez
mjuarez on Hacker News
Exactly the same case here. A few years ago, pre-ChatGPT, my wife was working with a massive database in SPSS or R (can't remember which). Now these "databases" are really just huge CSV/TSV files, with millions of records, one record per line. She was applying some very complicated mathematical functions to every single row, and she was frustrated because it was going to take days to apply a particular calculation she was working on to the whole database.
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.
> Not sure if they're related but apparently procedures we're significantly changed after the first incident to prevent the second incident.
Which obviously didn't work. Or worse, made the second incident more likely.
They don't have produce a good compiler. They just have to take the ones that already exist go much faster. That's likely much easier, and you can validate using existing test suites.
Like others have said, it's not reasonable to ask this.
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.
Having had this on my right eye a few months ago, I can confirm, the pain is excruciating, and my body was in panic mode. I rushed to the ophtalmologist, who confirmed I had a large abrasion. She says some people sleep with their eyes half open, and because you don't blink while sleeping, that exposed part of your eye completely dries out, and when you blink in the morning, you can rip away a chunk of the cornea.
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.
Could you post the initial 6KB version? I'd love to have a version that I can actually read and understand. I don't care if it's 2K LOC.
There's always backroom negotiations going on with investments like these. Private valuations are normally hyped-up, and with the current batch of AI companies, 100x so.
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.
Not to be _that_ guy, but it was technically -48V DC.
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.
When it was about the 7th incubator iteration, I got curious so I read the actual JEP history, and it had this informative tidbit, also included in the latest release:
"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.
This is misleading. It's actually taxing 36% of _assumed gains_ of say 5% on all assets. So if you have $1M in savings, you'll end up paying 1.8% or $18K/annum, regardless of the actual investment return. I can see it would be painful during down years, but most of the time it would be ok.
By default, Snowflake doesn't seem to use any crytographic hash algorithms, so that's not completely unexpected. Based on (1) this link, it uses a proprietary 64-bit hash, and has this tidbit: "Do not use HASH to create unique keys."
(1) https://docs.snowflake.com/en/sql-reference/functions/hash
You can still buy an Intel iMac Mini with 64GB RAM and 10GB ethernet. If you don’t like the M1 mini, buy the Intel one.
Isn’t that why sales taxes exist?