Francois Chollet

You are increasing its usefulness, its scope of applicability, but not its intelligence because skill is not intelligence.

And that's the fundamental confusion

that people run into is that they're confusing skill and intelligence.

That's memorization benchmarks.

It depends how you want to define reasoning, but there are two definitions you can use.

So one is, I have available a set of program templates.

It's like the structure of the puzzle.

which can also generate its solution.

And I'm just going to identify the right template, which is in my memory.

I'm going to input the new values into the template, run the program, get the solution.

And you could say this is reasoning.

And I say, yeah, sure, okay.

But another definition you can use is reasoning is the ability to, when you're faced with a puzzle, given that you don't have already a program in memory to solve it,

You must synthesize on the fly a new program based on bits of pieces of existing programs that you have.

You have to do on-the-fly program synthesis.

And it's actually dramatically harder than just fetching the right memorized program and replying it.

Sure.

I mean, in order to do on-the-fly program synthesis, you actually need building blocks to work from.

So knowledge and memory are actually tremendously important in the process.

I'm not saying it's memory versus reasoning.