Ephera

This is a highly confusing post for anyone who doesn't follow the Apple drama...

Look at what letters the play button covers, or rather the letters it doesn't cover...

LÖFFELSTIEL

As in, you call main() recursively? Don't think, I've ever tried that in any language...

You can make external tools available to the LLM and then provide it with instructions for when/how to use them.
So, for example, you'd describe to it that if someone asks it about math or chess, then it should generate JSON text according to a given schema and generate the command text to parametrize a script with it. The script can then e.g. make an API call to Wolfram Alpha or call into Stockfish or whatever.

This isn't going to be 100% reliable. For example, there's a decent chance of the LLM fucking up when generating the relatively big JSON you need for describing the entire state of the chessboard, especially with general-purpose LLMs which are configured to introduce some amount of randomness in their output.

But well, in particular, ChatGPT just won't have the instructions built-in for calling a chess API/program, so for this particular case, it is likely as dumb as auto-complete. It will likely have a math API hooked up, though, so it should be able to calculate a logarithm through such an external tool. Of course, it might still not understand when to use a logarithm, for example.

The problem is that corporations are not holistic organizations. In theory¹, a company could not have any juniors and always just hire seniors from the outside. And if your boss has reason to believe that this is more cost-effective, then they have to strive for that, even if they're well aware that it cannot work when all companies strive for that.

¹) In practice, I've actually found that juniors are important, too. If you staff a project team with only seniors, you quickly end up in a situation, where they don't talk enough to each other. They know how to solve things technologically, so they don't need to tell each other about their challenges and what solution they chose.
Similarly, you likely end up in a situation, where only big problems are being tackled, because everyone can tackle big problems and they're just very visible, highly prioritized problems. But when you add up enough small problems, they become just as problematic.

If you run a build command on the CLI, it should tell you the full type names...

The conventional ternary is structured like a normal if-else. In fact, in many languages with functional influence, they're the same thing.

For example, you can write this in Rust:

let vegetable = if 3 > 4 { "Potato" } else { "Tomato" };

Those also happen to be errors you'd typically run into, if you don't yet really know Rust...

Well, I happen to separately ~~only eat foods that don't cast a shadow~~ do the vegan thing and my genes don't like the taste of onion either, so uhh... 😅

But still good info. I haven't yet tried cooking whole-grain buckwheat myself, so knowing a combination that works, I can figure out substitutes or other combinations which are likely to work.

According to the screenshot I took, it was a gargoyle berserker with an axe. I had some ridiculous luck with armor drops, so basically every resistance was either maxxed or close to it. I only really got into trouble down in Zot:5...

And hmm, I should do more with Lugonu. I never really have a reason to pick him, but that means I also don't experiment with him, so I won't really learn what reasons there are to pick the guy...

I actually do, yes. Hundreds, if not thousands, of hours played and I made it down there and back out exactly once. 🙃