Richard Feynman on Computation (Stephen Wolfram) | AI Podcast Clips

Stephen Wolfram recalls working with Richard Feynman at Thinking Machines Corporation, where Feynman trusted intuition over detailed calculations. Wolfram describes experimenting with Rule 30 on the Connection Machine and discovering computational irreducibility, the idea that some systems can't be predicted without actually running them.
Chapters
When you were at Caltech, did you get to interact with Richard Feynman at all? Do you have any memories of Richard?
We, we worked together quite a bit actually, in fact on. And in fact both when I was at Caltech and after I left Caltech, we were both consultants at this company called Thinking Machines Corporation, which was just down the street from here actually as ultimately ill fated company. But I used to say this company is not going to work with the strategy they have. And Dick Feynman always used to say, what do we know about running companies? Just let them run their company. But anyway, he was not into that kind of thing and he always thought that my interest in doing things like running companies was a distraction, so to speak. And for me it's a mechanism to have a more effective machine for actually getting things, figuring things out and getting things to happen.
Did he think of it? Because essentially what you used, you did with the company. I don't know if you were thinking of it that way, but you're creating tools to empower your, to empower the exploration of the university.
Do you think, did he, did he understand that point?
The point of tools of.
I think not as well as he might have done. I mean I think that. But you know, he was actually my first company which was also involved with, well, was involved with more mathematical computation kinds of things. You know, he was quite, he had lots of advice about the technical side of what we should do and so on.
Do you have examples, memories of thoughts that.
Oh yeah, yeah. He had all kinds of. Look, he. In, in the business of doing sort of, you know, one of the hard things in math is doing integrals and so on. Right. And so he had his own elaborate ways to integrals and so on. He had his own ways of thinking about sort of getting intuition about how math works. And so his sort of meta idea was take those intuitional methods and make a computer follow those intuitional methods. Now it turns out for the most part, like when we do integrals and things, what we do is we build this kind of bizarre industrial machine that turns every integral into products of maya g functions and generates this very elaborate thing. And actually the big problem is turning the results into something a human will understand. It's not quotes doing the integral. And actually Feynman did understand that to some extent. And I'm embarrassed to say he once gave me this big pile of calculational methods for particle physics that he worked out in the 50s and he said it's more use to you than to me type thing and I was like, I intended to look at it and give it back. And I still have my files now. But that's what happens when it's finiteness of human lives. If he'd lived another 20 years, I would have remembered to give it back. But I think that was his attempt to systematize the ways that one does integrals that show up in particle physics and so on. Turns out the way we've actually done it is very different from that way.
What do you make of that difference between. So Feynman was actually quite remarkable at creating sort of intuitive. Diving and creating intuitive frameworks for understanding difficult concepts. Is.
And I'm smiling because the funny thing about him was that the thing he was really, really, really good at is calculating stuff. But he thought that was easy because he was really good at it. And so he would do these things where he would calculate some, do some complicated calculation in quantum field theory, for example, come out with the results, wouldn't tell anybody about the complicated calculation because he thought that was easy. He thought the really impressive thing was to have this simple intuition about how everything works. So he invented that at the end. And because he'd done this calculation and knew how it worked, it was a lot easier. It's a lot easier to have good intuition when you know what the answer is. And then he would just not tell anybody about these calculations. And he wasn't meaning that maliciously, so to speak. It's just he thought that was easy. And that led to areas where people were just completely mystified and they kind of followed his intuition. But. But nobody could tell why it worked because actually the reason it worked was because he'd done all these calculations and he knew that it was. Would work. And you know, when I, he and I worked a bit on quantum computers, actually back in 1980, 81, before anybody had heard of those things. And you know, the typical mode of. I mean, he always used to say, and I now think about this because I'm about the age that he was when I worked with him. And, you know, I see the people who are one third my age, so to speak, and he was always complaining that I was one third his age and there various things. But he would do some calculation by hand on a blackboard and things come up with some answer. I'd say, I don't understand this. I do something with a computer. And he'd say, I don't understand this. So there'd be some big argument about what was going on. But it was always, and I think actually many of the things that we realized about quantum computing that were sort of issues that have to do particularly with the measurement process are kind of still issues today. And I kind of find it interesting. It's a funny thing in science that there's a remarkable. It happens in technology too. There's a remarkable sort of repetition of history that ends up occurring eventually. Things really get nailed down, but it often takes a while, and often things come back decades later. Well, for example, I could tell a story actually happened right down the street from here. When we were both at thinking machines. I had been working on this particular cellular automaton called Rule 30 that has this feature that from very simple initial conditions, it makes really complicated behavior. And actually of all silly physical things, using this big parallel computer called the Connection Machine that that company was making, I generated this giant printout of Rule 30 actually on the same kind of printer that people use to make layouts for microprocessors. So one of these big large format printers with high resolution and so on. So, okay, so print this out. Lots of very tiny cells. And so there was sort of a question of how some features of that pattern. And so it was very much a physical on the floor with meter rules trying to measure different things. So Feynman kind of takes me aside, we've been doing that for a little while, and takes me aside and he says, I just want to know this one thing. He says, I want to know how did you know that this Rule 30 thing would produce all this really complicated behavior that is so complicated that we're going around with this big printout and so on? And I said, well, I didn't know. I just enumerated all the possible rules and then observed that that's what happened. He said, oh, I feel a lot better. You know, I thought you had some intuition that he didn't have that would let. When I said, no, no, no, no intuition, just experimental science.
So that's such a beautiful sort of dichotomy there of. That's exactly what you showed, is you really can't have an intuition about an irreducible. I mean, you have to run it.
Yes, that's right.
That's so hard for us humans and especially brilliant physicists like Feynman to say that you can't have a compressed, clean intuition about how the whole thing.
Yes.
Works.
Yes. No, he was. I mean, I think he was sort of on the edge of understanding that point about computation. And I think he found that. I think he always found computation interesting. And I think that was sort of what he was a little bit poking at. I mean, that intuition, you know, the difficulty of discovering things. Like even you say, oh, you know, you just enumerate all the cases and you just find one that does something interesting. Right. Sounds very easy. Turns out, like, I missed it when I first saw it because I had kind of an intuition that said it shouldn't be there. So I had kind of arguments, oh, I'm going to ignore that case because whatever.
And how did you have an open mind enough because you're essentially the same person as Richard Fein, like the same kind of physics type of thinking. How did you find yourself having a sufficiently open mind to be open to watching rules and them revealing complexity?
Yeah, I think that's an interesting question. I've wondered about that myself, because it's kind of like you live through these things and then you say, what was the historical story? And sometimes the historical story that you realize after the fact was not what you lived through, so to speak. And so what I realized is, I think what happened is I did physics, kind of like reductionistic physics, where you're throwing the universe and you're told, go figure out what's going on inside it. And then I started building computer tools and I started building my first computer language, for example. And computer language is not like. It's sort of like physics in the sense that you have to take all those computations people want to do and kind of drill down and find the primitives that they can all be made of. But then you do something that's really different because you're just saying, okay, these are the primitives. Now hopefully they'll be useful to people. Let's build up from there. So you're essentially building an artificial universe, in a sense, where you make this language, you've got these primitives, you're just building whatever you feel like building. And so it was sort of interesting for me because from doing science where you just throw in the universe as the universe is, to then just being told you can make up any universe you want. And so I think that experience of making a computer language, which is essentially building your own universe, so to speak, is, you know, that's kind of the. That's what gave me a somewhat different attitude towards what might be possible. It's like, let's just explore what can be done in these artificial universes, rather than thinking the natural science way of let's be constrained by how the universe actually is.
Yeah, by being able to program, essentially, you've. As opposed to being limited to just your mind and a pen. You. You now have. You've basically built another brain that you can use to explore the universe by.
Yeah.
Computer program. You know, there's a kind of a brain, right.
And it's. Well, it's, it's. Or a telescope or, you know, it's a tool. It lets you. Lets you see stuff.
But there's something fundamentally different between a computer and a telescope. I mean, it just. Yeah, I'm hoping not to romanticize the notion, but it's more general.
The computer is more general and it's. I think, I mean, this point about, you know, people say, oh, such and such a thing was almost discovered at such and such a time. The, the distance between, you know, the building the paradigm that allows you to actually understand stuff or allows one to be open to seeing what's going on. That's really hard. And, you know, I think in. I've been fortunate in my life that I've spent a lot of my time building computational language. And that's an activity that in a sense works by sort of having to kind of create another level of abstraction and kind of be open to different kinds of structures. But, you know, it's always, I mean, I'm fully aware of, I suppose, the fact that I have seen it a bunch of times of how easy it is to miss the obvious, so to speak. That at least is factored into my attempt to not miss the obvious, although it may not succeed.










