Stephen Wolfram

If it isn't small, it probably isn't right.

But it's pretty small.

And one of the ideas of orphan language is it's a language that humans can read.

It's not a language which... Programming languages tend to be this one-way story of humans write them and computers execute from them.

Orphan language is intended to be something which is sort of like math notation, something where humans write it and humans are supposed to read it as well.

And so kind of the workflow that's emerging is kind of this human mumbles some things.

Large language model produces a fragment of orphan language code.

then you look at that, you say, well, typically you just run it first.

You see, does it produce the right thing?

You look at what it produces.

You might say that's obviously crazy.

You look at the code.

You see, I see why it's crazy.

You fix it.

If you really care about the result and you really want to make sure it's right, you better look at that code and understand it because that's the way you have the sort of checkpoint of did it really do what I expected it to do.

Now, you go beyond that.

I mean, what we find is, for example, let's say the code does the wrong thing.

Then you can often say to the large language model, can you adjust this to do this?

And it's pretty good at doing that.

Interesting.