They clearly didn't even use a proper image generator - that's clearly the old crappy ChatGPT-builtin image generator. It's not like it's a useful figure with a few errors - the entire thing is sheer nonsense - the more you look at it, the worse it gets. And this is Figure 1 in a *paper in Nature*. Just insane.

This problem will decrease with time (here are two infographics from Gemini 3 I made just by pasting in an entire very long thread on Bluesky and asking for infographics, with only a few minor bits of touchup). Gemini successfully condensed a really huge amount of information into infographics, and the only sorts of "errors" were things like, I didn't like the title, a character or two was slightly misshapen, etc. It's to the point that you could paste in entire papers and datasets and get actually useful graphics out, in a nearly-finished or even completely-finished state. But no matter how good the models get, you'll always *have* to look at what you generate to see if it's (A) right, and (B) actually what you wanted.

And clearly God (who as we know, is a scalar field) is an AI. That's why there's so much "slop" in the Bible - factual errors, contradictions, different versions of the same text that heavily contradict each other, etc etc. It all makes so much more sense now!

Damn that is spot on. Nearly every fast food joint applies for temporary foreign workers visas so they can pay below market wages.

At one point last week I pasted the first ~300 words or so of the King James Bible into an AI detector. It told me that over half of it was AI generated.

And seriously, considering some of the god-awful stuff passing peer review in "respectable" journals these days, like a paper in AIP Advances that claims God is a scalar field becoming a featured article, or a paper in Nature whose Figure 1 is an unusually-crappy AI image talking about "Runctitiononal Features", "Medical Fymblal", "1 Tol Line storee", etc... at the very least, getting a second opinion from an AI before approving a paper would be wise.

One of my common online searches is fur technical info about software bugs. Google's assistant is great at giving me results that apply to three OS versions ago.

The problem is that the LLM only does one trick. When you start integrating other software with it, the other software's input has to be fed in the same way as your other tokens. As the last paragraph of TFS says, "every clock check consumes space in the model's context window" and that's because it's just more data being fed in. But the model doesn't actually ever know what time it is, even for a second; the current time is just mixed into the stew and cooked with everything else. It doesn't have a concept of the current time because it doesn't have a concept of anything.

You could have a traditional system interpreting the time, and checking the LLM's output to determine whether what it said made sense. But now that system has to be complicated enough to determine that, and since the LLM is capable of so much complexity of output it can never really be reliable either. You can check the LLM with another LLM, and that's better than not checking its output at all, but the output checking is subject to the same kinds of failures as the initial processing.

So yeah, we can do that, but it won't eliminate the [class of] problem.

Every tech company needs at least three things to start with: The business guy, the brain, and the lawyer. Ideally there should also be a marketing guy, but you can add them in later. Also, none of them have to be male, I just like saying "guy", buddy.

Yes and no, depending. If you are building an application in Excel, yes, all you said is true. If you are using one, no, none of it is. Spreadsheets can be set up such that the user just stuffs data into them where they are supposed to, then clicks a button to get results. Or maybe they don't even have to hit a button.

For the simplest useful example I can think of, I put together a spreadsheet which produces a table we use for asset valuation. This spreadsheet changes every year. If you load my spreadsheet, it will be correct for the current year. No user has to think about that at all, they just load it and get a correct table. You can extrapolate this to basically any level of complexity because Excel has VBA and you can script everything. The user just follows instructions, and they aren't even allowed to edit any cells which could break anything.

They are going to lose the next election, maybe to Reform, if they don't turn things around. Pandering to Reform voters is pointless, they are not going to vote Labour unless they go full fascist. Meanwhile they are alienating everyone else.

LibreOffice doesn't have cloud sharing features that allow multiple users to access a shared file with different permissions.

LibreOffice Calc does allow multiple users to edit a spreadsheet on a network drive, but doesn't have a user permission system or integration with a single login somewhere. The other apps like Writer don't support collaboration at all.

I agree. They are just so much less adroit than Blair's government was. Being less completely shit than the Tories is just not good enough.

In case anyone is going this far down the hole, it turned out great. Even though the item was shipped from the US, because the seller didn't respond I got a refund without having to return it.

So far Aliexpress has been responsive to 100% of my issues and I only have needed to be a little patient and not expect everything to be solved immediately or arrive immediately.

I guess it's conceivable. Not sure if every EV's battery diagnostics can report total charge received in the last 12 months. If it's consistently available, then yes, in principle, the MOT inspector could stick a dongle into the ODB port as part of the inspection and the government could use that rather than mileage. But I guess the government thinks mileage is less politically & emotionally contentious than an extra kWh charge.

I agree that a database-backed application is the right way to go for that much data. However, Finance used Excel because they could. We all like to talk about how bad an idea it is to do that, but Excel brought financial computations on large data sets to people who can't write any code. It has enabled thousands upon thousands of businesses to do things they couldn't do before without paying a programmer to develop a solution they cannot maintain. The fact that other spreadsheets regularly crater when handed data that Excel has no trouble with is exactly why we have so much Excel.

I like to use Drupal to rapidly create database applications which can handle a lot of data without writing code. But I wouldn't expect someone in accounting to be able to do that at all, and that just shifts the problem domain. Instead of getting stuck with Excel, now I'm getting stuck with Drupal. All of the logic just winds up in a different system that you can't trivially transfer it out of, so you have the same exact maintainability problem, except more people know how to work with Excel.