The UK is one of the halfway countries that still uses miles and gallons for vehicles

Only for fuel consumption, but not fuel. Which his funny because we dispense fuel (and just about everything else) in liters, so MPG is an entertainingly irritating figure. We should use MPL obviously.

Pandering to Reform voters is pointless, they are not going to vote Labour unless they go full fascist.

Probably not even then. If you're going to vote for a racist, why not go for the real deal instead of a half arsed knockoff where you're not even sure if they're really committed or just doing it to try and impress.

Here it is every single year. Varies by State, of course. Some States it is 2 years, some have no inspections at all. https://en.wikipedia.org/wiki/...

In NM it's yearly: they ensure your tire treads aren't too deep and that you have one emergency spare in place of a regular wheel. They'll also put some chips in your windscreen if you ask nicely.

it augers the beginning of the end of total immunity for social media conglomerates.

You've drilled down to heart of the matter.

They do. Some people don't use them; and (if disciplined) use one or more worksheets to store data and refer to it purely internally and (otherwise) just sort of ad-hoc mix data and formulas.

In some cases a database connection is where the data comes from; but the number of cells grows because it's conceptually easier(and in practice often less opaque, given the ugliness of displaying very large cell contents) to munge on the data step by step rather than trying to ram everything into one transformation.

Coming from the IT side; and having to field questions from the perpetrators of some absolutely hideous excel sheets from time to time(no, I didn't even know that there was a way of creating a type of embedded image that actually quietly triggers the print spooler subsystem to do something that generates a new image based on the contents of another region of the spreadsheet, still don't know how they did that; but it's objectively depraved) I understand the hate; but I do have to admit that spreadsheets are pretty good for napkin-math thinking-it-through type processes.

Like when you work it out on paper; you've got your input, then you have a cell with the contents of the first transformation you wanted to make, then the second, then the third, and so on, and at each step you can think "does this value make sense?"

It rapidly gets out of hand in quantity; but as a rapid sketchpad for thinking something through you could do a whole lot worse. It's also tempting(again, tempting down the path of darkness in quantity) for dealing with jobs that need both a bit of string munging and a pretty-printed output.

You send the intern down to storage with a barcode scanner and have them start snagging SNs and MACs and stuff from the shipment of new gear. Turns out various vendors use different prefixes on different barcode values to inform their own ERP/inventory system/warehouse people which of the 5 closely spaced barcodes their scanner hit. And each vendor uses a different set of conventions, and while obvious enough they aren't documented. Ok, no problem; intern comes back with raw list; all the Lenovo SNs get a 'last x characters' substring; all the Cisco MACs get another transform, whatever.

Obviously if it were your inventory/warehouse system you wouldn't be treating the barcode scanner as a raw HID device and doing ad-hoc transformations, there would be a program that automatically uses the prefixes to populate the correct parts of the form; but you want to stick your head into ERP project hell rather than come up with maybe a dozen lightweight string manipulations? Obviously, you could also do it in your choice of scripting language and iterate through one CSV to create another; but that mostly just conceals what you did from anyone who doesn't use that scripting language; while you can walk basically anyone employable through the logic of the spreadsheet prettifying.

or a paper in Nature

That's not a paper in Nature, it's a paper in Scientific Reports, a much lower tier journal published by the same company.

Hells bells that is godawful though, and inexcusable from a publishing point of view.

SciRep is a very mixed bag. It's where you go when you've exhausted the higher impact factor journals. There are some really good papers in there, but also bad ones and with the vast deluge (even pre AI slop) of papers, getting good peer reviewers for mid to lower tier journals has been more or less impossible for years.

I read that as H2O conflicts first... I will let someone else insert the other obvious meme.

Yes it will keep being LLMs are LLMs week until the outside world moves on from hammering "LLMs are magic" week every week.

LLMs are of course LLMs.

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.

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 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.

and the ratio of cars to artics is a bit lower than that.

That is true, but it's also not uniform: some roads are 50% artics, and many others get almost none.