dotinvoke

My experience with AI tools is the opposite. The biggest energy thieves for me are configuration issues, library quirks, or trivial mistakes that are hard to spot. With AI I can often just bulldoze past those things and spend more time on tangible results.

When using it for code or architecture or design, I’m always watching for signs that it is going off the rails. Then I usually write code myself for a while, to keep the structure and key details of whatever I’m doing correct.

A mobile keyboard—limited as it is—has no trouble producing an em-dash, requiring little more than a long press on the - button.

It makes no sense to go looking to the past for the ultimate health diet, ancient people had life expectancies of like 40.

I’ll admit that I struggle to read their Byzantine pricing tables but that is $15 per 1k searches, right?

What is your preferred alternative?

Brave does not permit you to store search results unless you opt for the $26/mo plan.

I emailed them about it and that policy applies to storing any data derived from search results as well.

Those old homes are usually used as storage for things that don't fit into their new, urban homes. The market value and taxes are low, so there's no point in selling.

Then eventually, without realizing, you have gone there for the last time, and there's nothing left to move to your new home.

Alternatively, the last old person who lived in the house dies or goes into a care home, and their kids (if they have any) never find the time to clear out the old place. There's no one to sell it to, anyway, so they have all the time in the world.

I had the same idea, but now I a Postgres database that has very high latency for simple queries because the CPU is busy building large HNSW indexes.

My impression is that it might be best to do vector index construction separately from the rest of the data, for performance reasons. It seems vector indexes are several orders of magnitude more compute intensive than most other database operations.

As a long-time Audible subscriber, I’d estimate that I skip 1 in 3 books because of the narrator’s voice or bad recording setup.

Why not just feed that information back into the algorithm itself?

I read it before on Twitter, it’s probably adapted to fit into the 280-character limit.

Job switching should be less of a problem with a 12% unemployment rate, though.

Greek workers have the option to work in any of the 27 EU countries, and a few non-EU countries like Switzerland and Norway.

Given that there is a shortage of skilled workers prompting this policy, it makes little sense to allow employers to demand more unpaid overtime of workers. That just means more Greeks working outside of Greece.

Greek workers already work more hours than any other EU country while making basically no money, so making Greeks work even more hours should probably not be a government priority.

Removing needless regulation and speeding up government permits would be a better idea.

Now that people are training AI models for video this might actually be worth something as training data.