Personally I had similar results when searching for known terms for certain concepts that I didn't know the name for. And usually I had to guide the process to find the actual expression used in the domain (it usually made up a lot of fancy and well-fitted names itself). And sometimes it helped to gonback and change the query. Harder if you have to wait that long, though :)

So.. I guess I would trust its process (mentioning "research" a lot) more than its chosen result :) Not sure if it you wanted it to be a synthesizer or rather an assistant. I'd go with what is closer to your intention or what you think it resulted in in the end.

An interesting observation might be that guiding that (I don't dare to say it, but anyway) research process might still be an important part and the network's self-evaluation might not be as good as one would need it to be at this point in time. I'd guess it's about adding ones personal judgement early to not end up at the wrong spot after a long processing time. Then again you are using a certain selection of simple and more complex models, so I can't say if there might be a way to have that kind of harsher judgement that one would apply oneself emulated in the proces and what side effects might come form that choice of models you made.

In the end I was just surprised by the number of picky replies your post got, so I just thought that you discussing the perfect description with the LLM might make be a fun solution. Personally I am a big fan of interactively talking to LLMs at the moment though, so I might be the wrong guy to know your intended audience and use case enough. Just couldn't see how using the term "research" would be the problem.

What description would itself come up with, BTW?

When you anwer with "I agree, LLMs have biases.", I immediately suspect that to be an LLM calming me after correcting it, though. So, the world has definitely changed and we might need to allow for correcting the broadness of words and meanings.

After all you did not write thesis, scientific research or similar and I remember it being called researching when people went looking up sources (which took them longer than an agent or LLM these days). Compressing that into a report might make it a review, but anyway. Great that you assembled a useful work tool here for some who need exactly that.

This is hard to correct with a global training, as you would need to correct each step, even the most basic ones, instead. As it's hard to convince someone that their result is not correct, when you actually would have to show the errors in the steps that led there.

For LLMs it feels even more tricky when thinking about complex paths being encoded somehow dynamically in simple steps than if there was some clearer/deeper path that could be activated and corrected. Correcting one complex "truth" seems much more straightforward (sic) than effectively targeting those basic assumptions enough so that they won't build up to something strange again.

I wonder what effective ways exist to correct these reasoning models. Like activating the full context and then retraining the faulty steps, or even "overcorrecting" the most basic ones?

Discussing number data with current LLMs also does not seem right at the moment. Not sure if simple column-specific conversion tasks might work.

In german Excel it's might be ok due to its original focus on numbers, but replacing decimal "." with the german "," also forces you to use a semicolon everywhere where you would use a comma (function, vector/array notations). To me the most annoying issue with localized programming languages. And consecutive ";;;" just looks awful. And what would happen to command/line endings...

BTW, Apple once tried to translate content-specific parts of their AppleScript language (like Dialogs etc) but in the process also hit some enumerations which often sit at the border between programming language and content. Big desaster in certain edge cases.

Anyway. Of course I like that the effort was made. There are famous Asterix comic books translated into all kinds of languages and dialects. I'd really like to see great localized coding languages, but I guess they will have to avoid line ending semicolons and only use integers :)

Elon: "Comedy!"

It was useful in a way but basically evolved into interface-based controller patterns due to the needed complexities and the whish to keep the basic underlying design pattern. So I'd expect to see lots of enhanvement requests once that box was opened :)

There was an early Java UI toolkit by some browser vendor (IFC by Netscape, probably) that allowed to string action elements together like that.

I still find the principal question of "if I need additional components anyway, should I just get the more complex ones" interesting. It's located somewhere between quality, price, the definition of simple and optimal, as well as one of ones personal (or this week's) perspective on the art of the craft.

The projects is not a discrete player that basically pushes SD card data via a few digital standard ICs out as PWM, it uses a pretty sophisticated MCU after all. So, is a I2S DAC the logical solution or the fast PWM, I still find it hard to decide, especially when i have to order (even the simple or mechanical) parts anyway, or should I have a few I2S DACs in the drawer with the Pico these days.

Not sure if I can bring that point across. It's more about what are your default parts these days. I always have a few i2c OLED displays in that drawer, and the project uses one, too, thirty years ago it might have been resistors, LEDs and a few logic ICs instead. So I wonder, would I go discrete (or "simple") for that particular part of the solution for a particular reason or not. And also, why do I still have no I2S DACs stocked in that drawer, while I have display, sensors etc.

So maybe it's just about audio being a somehow ignored interface in (my) embedded tinkering. Or it's more general and about a modernized selection of stocked parts and using those more naturally while still being aware of the simpler solutions. I use pretty complex (but inexpensive) I2C sensors these days, after all.

Ok, many words on that small part of the overall decision making...

Great that the author chose one and finished (and published) the project instead of stopping at that annoying junction :)

I think it was using a wide master screen that the terminals connected to via vnc, displaying different parts of the master screen. Only three or four screens wide, though, and not optimized for user interaction. But a live app nonetheless.

Would be great to also have one on that boys & girls club where the whole idea was invented and what else they might have come up in the 80s.

The "invent a game with cups" at least is a great hint towards motivating kids (on a different level than actually competing in the resulting game) close to a Sesame Street kind of mindset from back then and might deserve a story on its own for "hacking" cups into being toys and even a sport in the end.

Great work. Thanks a lot for sharing.

Ah, I don't know.

(I must say that I was happy to see/read that article, though)