Skip to content
Peter Norvig: Artificial Intelligence: A Modern Approach | Lex Fridman Podcast #42
This video isn’t embeddableWatch on YouTube →
Lex Fridman PodcastLex Fridman Podcast

Peter Norvig: Artificial Intelligence: A Modern Approach | Lex Fridman Podcast #42

Peter Norvig is a research director at Google and the co-author with Stuart Russell of the book Artificial Intelligence: A Modern Approach that educated and inspired a whole generation of researchers including myself to get into the field. Thank you for listening ❤ Check out our sponsors: https://lexfridman.com/sponsors/ep42-sb See below for timestamps, and to give feedback, submit questions, contact Lex, etc. *CONTACT LEX:* *Feedback* - give feedback to Lex: https://lexfridman.com/survey *AMA* - submit questions, videos or call-in: https://lexfridman.com/ama *Hiring* - join our team: https://lexfridman.com/hiring *Other* - other ways to get in touch: https://lexfridman.com/contact *OUTLINE:* 0:00 - Introduction 0:37 - Artificial Intelligence: A Modern Approach 9:11 - Covering the entire field of AI 15:42 - Expert systems and knowledge representation 18:31 - Explainable AI 23:15 - Trust 25:47 - Education - Intro to AI - MOOC 32:43 - Learning to program in 10 years 37:12 - Changing nature of mastery 40:01 - Code review 41:17 - How have you changed as a programmer 43:05 - LISP 47:41 - Python 48:32 - Early days of Google Search 53:24 - What does it take to build human-level intelligence 55:14 - Her 57:00 - Test of intelligence 58:41 - Future threats from AI 1:00:58 - Exciting open problems in AI *PODCAST LINKS:* - Podcast Website: https://lexfridman.com/podcast - Apple Podcasts: https://apple.co/2lwqZIr - Spotify: https://spoti.fi/2nEwCF8 - RSS: https://lexfridman.com/feed/podcast/ - Podcast Playlist: https://www.youtube.com/playlist?list=PLrAXtmErZgOdP_8GztsuKi9nrraNbKKp4 - Clips Channel: https://www.youtube.com/lexclips *SOCIAL LINKS:* - X: https://x.com/lexfridman - Instagram: https://instagram.com/lexfridman - TikTok: https://tiktok.com/@lexfridman - LinkedIn: https://linkedin.com/in/lexfridman - Facebook: https://facebook.com/lexfridman - Patreon: https://patreon.com/lexfridman - Telegram: https://t.me/lexfridman - Reddit: https://reddit.com/r/lexfridman

Lex FridmanhostPeter Norvigguest
Sep 30, 20191h 3mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:000:37

    Introduction

    1. LF

      The following is a conversation with Peter Norvig. He's the director of research at Google and the co-author with Stuart Russell of the book Artificial Intelligence: A Modern Approach that educated and inspired a whole generation of researchers, including myself, to get into the field of artificial intelligence. This is the Artificial Intelligence podcast. If you enjoy it, subscribe on YouTube, give it five stars on iTunes, support on Patreon, or simply connect with me on Twitter @lexfridman, spelled F-R-I-D-M-A-N. And now, here's my conversation with Peter Norvig.

  2. 0:379:11

    Artificial Intelligence: A Modern Approach

    1. LF

      Most researchers in the AI community, including myself, own all three editions, red, green, and blue, of the, uh, Artificial Intelligence: A Modern Approach. It's a field-defining textbook, as many people are aware, that you wrote with Stuart Russell. How has the book changed and how have you changed-

    2. PN

      (laughs) Yeah.

    3. LF

      ... uh, in relation to it from the first edition to the second to the third and now fourth edition as you work on it?

    4. PN

      Yeah. So it's, so it's been a lot of years, a lot of changes. One of the things changing from the first to m- m- maybe the second or third was just the rise of, uh, computing power, right? So I think in the, in the first edition we said, uh, "Here's predicate logic, but, uh, that only goes so far 'cause pretty soon you have millions of, uh, short little predicate expressions and they couldn't possibly fit in memory. Uh, so we're gonna use first-order logic that's, uh, more concise." And then we quickly r- realized, "Oh, predicate logic is pretty nice because there are really fast SAT solvers and other things, and look, there's only millions of expressions and that fits easily into memory, or maybe even billions fit into memory now." So, that was a change of, uh, the type of technology we needed just because the hardware expanded.

    5. LF

      Even to the second edition?

    6. PN

      Yeah. Yeah.

    7. LF

      So resource constraints were loosened significantly for the second edition?

    8. PN

      Yeah. Yeah. And then-

    9. LF

      And that was early 2000s, second edition?

    10. PN

      Right. So '95-

    11. LF

      Yeah.

    12. PN

      ... was the first and then, uh, 2000, 2001 or so. And then, uh, moving on from there, I think we're s- we're starting to see that again with the, uh, GPUs and then, uh, more specific type of, uh, machinery like the TPUs and w- we're seeing custom ASICs and so on, uh, for deep learning. So, we're seeing another advance in terms of the hardware. Then I think another thing that we especially noticed this time around is in all three of the first editions, we kind of said, "Well, we're gonna find AI as maximizing expected utility."

    13. LF

      Mm-hmm.

    14. PN

      "And you tell me your utility function and now we've got 27 chapters worth of cool techniques for how to optimize that." I think in this edition, we're saying more, "You know what? Maybe that optimization part is the easy part-

    15. LF

      Mm-hmm.

    16. PN

      ... and the hard part is deciding what is my utility function? What do I want? And if I'm a collection of agents or a society, uh, what do we want as a whole?"

    17. LF

      So, you touched that topic in this edition. You get-

    18. PN

      Yeah.

    19. LF

      ... a little bit more into utility.

    20. PN

      Yeah. Yeah.

    21. LF

      That's really interesting. Uh, on a, uh, a technical level or almost pushing the philosophical?

    22. PN

      I guess it, it is philosophical, right? So we, we've always had a philosophy chapter, which, which I was, uh, glad to s- that we were supporting. And now, it's less kind of the, uh, you know, Chinese room-type argument-

    23. LF

      Mm-hmm.

    24. PN

      ... and more of these, uh, ethical and societal-type issues. Uh, so we get into, uh, the issues of, uh, fairness and bias and, uh, and just the issue of, uh, aggregating utilities.

    25. LF

      So, how do you encode human values into a utility function?

    26. PN

      (laughs)

    27. LF

      Is, is there something that you can do purely through data in a learned way or is there some systematic... Obviously, there's no good answers yet. There's just, uh-

    28. PN

      Yeah.

    29. LF

      ... beginnings to this, uh, to, to even opening the door to these questions.

    30. PN

      Right. So, there is no one answer. Yes, there are techniques, uh, to try to learn that. So we talk about inverse reinforcement learning.

  3. 9:1115:42

    Covering the entire field of AI

    1. LF

      so maybe taking a quick step back, uh, at the beginning of the Artificial Intelligence: The Modern Approach book or writing, so here you are in the '90s when you first sa- uh, sat down with Stuart to write the book, uh, to cover an entire field, which is one of the only books that has successfully done that for AI and actually in- in a lot of other computer science fields. You know, it's a diff- it's a h- it's a huge undertaking. So, m- th- it must've been quite daunting. What was that process like? Did you envision that you would be trying to cover the entire field? Was there a systematic approach to it that was more step-by-step? How was-

    2. PN

      Yeah.

    3. LF

      ... how did it feel?

    4. PN

      So I guess it came about, you know, I'd go to lunch with the other AI faculty at Berkeley and we'd say, uh, you know, "The field is changing. Seems like the current books are a little bit behind. Nobody's come out with a new book recently. We should do that." And everybody said, "Yeah, yeah. That's a great thing to do." Uh, and we never did anything.

    5. LF

      (laughs) Right.

    6. PN

      And then I ended up, uh, heading off to, uh, industry. I went to, uh, Sun Labs, so I thought, "Well, that's the end of my possible academic publishing career."

    7. LF

      Mm-hmm.

    8. PN

      But I met Stuart again at a conference, like a year later and said, "You know that book we were always talking about? You guys must be half done with it by now, right?"

    9. LF

      (laughs)

    10. PN

      And he said, "Well, we keep talking. We never do anything."

    11. LF

      Right.

    12. PN

      So I said, "Well, you know, we should do it." And I think the reason is that we all felt it was a time where the field was changing, and th- that was in two ways. So, you know, the good old-fashioned AI was based, uh, primarily on Boolean logic, and you had a few tricks to deal with uncertainty. And it was based pr- primarily on knowledge engineering-

    13. LF

      Mm-hmm.

    14. PN

      ... that the way you got something done is you went out and you interviewed an expert and you wrote down by hand everything they knew. And we saw in- in, uh, '95 that the field was changing in- in two ways. One, we were moving more towards probability ru- rather than Boolean logic, and we were moving more towards machine learning rather than knowledge engineering.

    15. LF

      Mm-hmm.

    16. PN

      Uh, and the other books, uh, hadn't caught that wave. They were still in the, uh, more in the- in the old school, although certainly they had part of that, uh, on the way. But we said, "If we start now completely taking that point of view, we can have a- a different kind of book." And we were able to put that together.

    17. LF

      And, uh, what was literally the process if you remember? What... Did you start writing a chapter? Did you outline s-

    18. PN

      Yeah. I guess, I guess we did an- an outline and then we sort of assigned chapters to each person. At the time, uh, I had moved to Boston and Stuart- Stuart was in Berkeley, so basically, uh, we did it, uh, uh, over the internet and- and, uh, you know, that's n- that wasn't the same as doing it today. (laughs) It meant, uh, you know, uh, dial-up lines and Telnetting in-

    19. LF

      Right.

    20. PN

      ... and, and (laughs) -

    21. LF

      (laughs)

    22. PN

      ... you know, you, uh, you Telnet it into, uh, one shell and you type cat filename and you-

    23. LF

      Right.

    24. PN

      ... hoped it was captured at the other end and...

    25. LF

      And certainly you're not sending, uh, images and figures back and forth.

    26. PN

      Right, right, that didn't work.

    27. LF

      (laughs) But, you know, did you anticipate where the field would go, uh, from that day, uh, from, uh, from the '90s? Did you see the growth into learning-based methods, into data-driven methods, that followed in the future decades?

    28. PN

      W- we certainly thought that, uh, learning was important. I guess we, w- we missed it as, uh, being as important as it, as it is today. We mi- we missed this idea of big data. We missed it, uh, uh... the idea of deep learning hadn't been invented yet. We could have, uh, taken the book from a complete, uh, machine learning point of view right from the start. We chose to do it more from a point of view of, we're gonna first develop the different types of representations and we're gonna talk about different types of environments, of, uh, is it fully observable or partially observable and is it, uh, deterministic or stochastic and so on. And we, uh, made it more complex along those axes rather than, uh, focusing on the machine learning axis first.

    29. LF

      Do you think... You know, there's some sense in which the deep learning craze, uh, is extremely successful for a particular set of problems and, you know, eventually it's going to, in the general case, hit challenges. And so in terms of the difference between, uh, perception systems and robots that have to act in the world, do you think, uh, we're gonna return to AI modern approach type breadth in edition five and six-

    30. PN

      Yeah.

  4. 15:4218:31

    Expert systems and knowledge representation

    1. LF

      looking at the, some success but certainly, uh, eventual demise, the partial demise of experts as symbolic, uh, systems in the '80s, do you think there is kernels of wisdom in the work that was done there with logic and reasoning and so on that will rise again in your view?

    2. PN

      So certainly I think the idea of representation and reasoning is crucial, that, uh, you know, sometimes you just don't have enough data about the world to learn de novo, uh, so you've got to have a, a, some idea of representation, whether that was programmed in or told or whatever, and then be able to take, uh, steps of reasoning. I, I think the problem, uh, with, uh, you know, the good old-fashioned AI was, uh, one, we tried to base everything on these, uh, symbols that were atomic. And that's great if you're, like, trying to define the properties of a triangle.

    3. LF

      Right.

    4. PN

      Right? Because they have necessary and sufficient conditions. Uh, but things in the real world don't. The real world is, is messy and doesn't have sharp edges, and atomic symbols do. So that was a, a poor match. And then the other aspect was that the, uh, reasoning was universal and applied anywhere, which in some sense is good, but it also means there's no guidance as to where to apply.

    5. LF

      Mm-hmm.

    6. PN

      And so you, you know, you started getting these paradoxes like, uh, uh, "Well, if I have a mountain and I remove one grain of sand, uh, then it's still a mountain," and, "But if I do that repeatedly, at some point it's not," right? And, uh, with logic, you know, there's nothing to stop you from applying things, uh, repeatedly. Uh, but maybe with, uh, something like, uh, deep learning, and I don't really know what the right name for it is, uh, we could separate out those ideas. So, one, we could say, uh, you know, a mountain isn't just an atomic notion. It, it's some sort of, something like a word embedding that, uh, uh, has a, uh, a more complex representation.

    7. LF

      Mm-hmm. Yeah.

    8. PN

      And secondly, we could somehow learn, yeah, there's this rule that you can remove one grain of sand, uh, and you can do that a bunch of times but you can't do it, uh, a near infinite amount of times. But on the other hand, when you're doing induction on the integers, sure, then it's fine to do it an infinite number of times. And if we could l- uh, somehow we have to learn when these strategies are applicable-... rather than having the strategies be completely neutral and avai- uh, available everywhere.

  5. 18:3123:15

    Explainable AI

    1. PN

    2. LF

      Anytime you use neural networks, anytime you learn from data or form representation from data in an automated way, it's not very explainable as to, uh, or it's not introspective to us humans in terms of, uh, how this neural network sees the world. Where... Why does it succeed so brilliantly on so many, in so many cases and fail so miserably in surprising-

    3. PN

      Yeah.

    4. LF

      ... ways and small. So, what do you think is this... is, um, the future there? Can simply more data, better data, more organized data solve that problem, or is there elements of symbolic systems that need to be brought in which are a little bit more explainable?

    5. PN

      Yeah. So, I prefer to talk about trust and, uh, validation and verification rather than just about explainability. And then I think, uh, explanations are one tool that you use towards those goals. And I think it is an important issue that, uh, we don't want to use these systems unless we trust them and we want to understand where they work and where they don't work, and- and an explanation can be part of that, right? So, I apply for loan and I get, uh, denied, uh, I want some explanation of why, and uh, you have, uh, in Europe we have the GDPR that says, uh, you're required to be able to get that. But on the other hand, an explanation alone is not enough, right? So, you know, we were used to dealing with people and with, uh, organizations and corporations and so on, and they can give you an explanation and you have no guarantee that that explanation relates to reality.

    6. LF

      Right.

    7. PN

      Right? So, the bank can tell me, "Well, you didn't get the loan 'cause you didn't have enough collateral," and that may be true or it may be true that they just didn't like my, uh, religion or- or something else. Uh, I can't tell from the explanation, and that's, uh, that's true whether the decision was made by a computer or by a person. So, I want more. I do want to have the explanations and I want to be able to, uh, have a conversation to go back and forth-

    8. LF

      Mm-hmm.

    9. PN

      ... and said, "Well, you gave this explanation, but what about this?"

    10. LF

      Mm-hmm.

    11. PN

      "And what would have happened if this had happened? And, uh, what would- what would I need to change that?" So, I think a conversation is- is a better way to think about it than just, uh, an explanation as a single output. Uh, and I think we need testing of various kinds, right? So, in order to know, was the decision really based on my collateral or was it based on my, uh, religion or skin color or whatever? I can't tell if I'm only looking at my case, but if I look across all the cases, then I can detect a pattern.

    12. LF

      Right.

    13. PN

      Right? So, you want to have that kind of capability. Uh, you want to have these adversarial testing, right? So, we thought we were doing pretty good at, uh, object recognition in- in images. We said, "Look, we're- we're at sort of pretty close to human level of performance on ImageNet," and so on. Uh, and then you start seeing these adversarial images and you say, "Wait a minute, that part is nothing like (laughs) human performance." Uh-

    14. LF

      Yeah, you can mess with it really easily.

    15. PN

      You can mess with it really easily, right?

    16. LF

      Yeah.

    17. PN

      And, uh, yeah, you can do that to humans too, right? So...

    18. LF

      In a different way, perhaps.

    19. PN

      Right. Humans don't know what color the dress was.

    20. LF

      Right.

    21. PN

      And so they're vulnerable to certain attacks that are different than the attacks on the- on the machines, but the, you know, the attacks on the machines are so striking, uh, they really change the way you think about what we've done, right?

    22. LF

      Mm-hmm.

    23. PN

      And the- and the way I think about it is, I think part of the problem is we're seduced by, uh, our low-dimensional metaphors, right?

    24. LF

      (laughs) Yeah. I like-

    25. PN

      So, you know, you look-

    26. LF

      I like that phrase. (laughs)

    27. PN

      You look in a- in a textbook and you say, "Okay, now we've mapped out the space and, you know, uh, cat is here and dog is here, and maybe there's a tiny little spot in the middle-

    28. LF

      Yeah.

    29. PN

      ... where you can't tell the difference, but mostly we've got it all covered." And if you believe that metaphor, uh, then you say, "Well, we're nearly there," and, uh, you know, there's only going to be a couple adversarial images.

    30. LF

      Yeah.

  6. 23:1525:47

    Trust

    1. LF

      so on. But take it back to the... this, uh, this word trust. Uh, do you think we're a little too hard on our robots in terms of-

    2. PN

      (laughs) .

    3. LF

      ... uh, the standards we apply? So, you know, of, uh, there's a dance, there's a- there's a- there's a dance in non-verbal and verbal communication between humans. You know, if we apply the same kind of standard in terms of humans, you know, we trust each other pretty quickly. Uh, you know, you and I haven't met before and there's some degree of trust (laughs) .

    4. PN

      Yeah.

    5. LF

      Right? That, uh, nothing's gonna go crazy wrong. And yet to AI, when we look at AI systems or... we seem to approach, uh, through skepticism always, always.

    6. PN

      Yeah.

    7. LF

      And it's like they have to prove through a lot (laughs) of hard work that they're even worthy of, uh, even inkling of our trust. What do- what do you- what do you think about that? How- how do we break that barrier, close that gap?

    8. PN

      I think that's right. I think that's a big issue. Uh, just listening, uh, my friend, uh, Mark Moffett is a naturalist and he says, uh, "The most amazing thing about humans is that you can walk into a- a coffee shop or a, uh, a busy street in a city..."... and there's lots of people around you that you've never met before, and you don't kill each other.

    9. LF

      (laughs) Yeah.

    10. PN

      He says, "Chimpanzees cannot do that."

    11. LF

      Yeah, right. (laughs)

    12. PN

      Right? If a chimpanzee is in a situation where, "Here's some, uh, that aren't from my tribe..." Bad things happen.

    13. LF

      Especially in a coffee shop, there's delicious food around, you never know.

    14. PN

      Yeah, yeah. But, but we humans have figured that out.

    15. LF

      Yeah.

    16. PN

      Right? Uh, and you know-

    17. LF

      For the most part.

    18. PN

      ... for the most part. We still go to war, we still do terrible things, uh, but for the most part, we've learned to trust each other and, and live together. Uh, so that's gonna be important for our, uh, our AI systems as well, and I th- also, I think, uh, you know, a lot of the emphasis is on AI, uh, but in many cases, uh, AI is part of the technology, but isn't really the main thing. So a lot of, of what we've seen is more due to communications technology-

    19. LF

      Mm-hmm.

    20. PN

      ... than AI te- AI technology. Yeah, you wanna make these good decisions, but the reason, uh, we're able to have any kind of system at all is we've got the communication so that we're collecting the data and so that we can reach lots of people around the world. I think that's a, a bigger change that we're dealing with.

    21. LF

      Speaking of reaching a lot of people around

  7. 25:4732:43

    Education - Intro to AI - MOOC

    1. LF

      the world, on the side of education, you've, uh ... one of the many things in terms of education you've done, you taught the Intro to Artificial Intelligence course that signed up 100,000- 160,000 students. It was one of the first successful example of an massive, uh, of a MOOC, massive open online course. What did you learn from that experience? Uh, what do you think is the future of MOOCs, of education online?

    2. PN

      Yeah. It was a great fun doing it, particularly, uh, being right at the start just because it was exciting and new, but it also meant that we had less competition.

    3. LF

      (laughs) Yeah.

    4. PN

      Right? So, uh, one of the things you hear about, uh, "Well, the problem with MOOCs is, uh, the completion rates are, are so low, so they must be a failure." And, and I got to admit, I'm a prime contributor, right?

    5. LF

      Mm-hmm.

    6. PN

      I've probably, uh, started 50 different courses that I haven't finished, but I got exactly what I wanted out of them because I had never intended to finish them. I just wanted to, uh, dabble in a little bit, either to see the topic matter or just to see the pedagogy of, "How are they doing this class?" So I guess the main thing I learned is, when I came in, I thought, uh, the challenge was information, saying, "If I'm just to take the stuff I want you to know and I'm very clear and explain it well, then my job is done and, uh, good things are gonna happen." Uh, and then in, in doing the course, I learned, uh, well, yeah, you gotta have the information, but really, the motivation is the most important thing, that, uh, if students don't stick with it, then it doesn't matter how good the content is.

    7. LF

      Mm-hmm.

    8. PN

      Uh, and I think being one of the first classes, we were helped by a sort of exterior motivation. So, we tried to do a good job at making it enticing and setting up, uh, uh, ways for, uh, you know, the community to work with each other, to make it more motivating, but really, a lot of it was, "Hey, this is a, a new thing, and I'm really excited to be part of a new thing." And so the students brought their own motivation. And so I think this is great because there's lots of people around the world who have never had this before-

    9. LF

      Mm-hmm.

    10. PN

      ... you know, uh, who'd never have the opportunity to, uh, go to Stanford and take a class, or go to MIT, or go to one of the other schools. Uh, but now we can bring that to them, and if they bring their own motivation, uh, they can be successful in a way they couldn't before. But that's really just the top tier of people that are ready to do that. The rest of the people, uh, j- just don't see or, you know, don't have the motivation and don't see how, if they push through and were able to do it, what advantage that would get them. Uh, so I think we got a long way to go before we're able to do that, and I think it'll be m- some of it is based on technology, but more of it's based on the idea of community, that you gotta actually get people together. Some of that getting together can be done online. I think some of it really has to be done in person to be able to, in order to build that type of, uh, community and trust.

    11. LF

      You know, there's an intentional mechanism that we've developed, uh, a short attention span, especially younger people, um, because sort of shorter and shorter videos online, uh, there's a, whatever the, th- the way the brain is dev- is developing now with people that have grown up with the internet, they have a, quite a short attention span. So, and I, I would say I had the same when I was growing up too, probably for different reasons. So, I probably wouldn't have, uh, learned as much as I have if I wasn't forced to sit in a physical classroom-

    12. PN

      Mm-hmm.

    13. LF

      ... sort of bored, sometimes falling asleep-

    14. PN

      Sure. (laughs)

    15. LF

      ... but sort of forcing myself through that process in sometimes extremely difficult computer science courses. What, what's the difference, in your view, between in-person education experience, which you, uh, first of all, yourself had and you yourself taught-

    16. PN

      Yeah.

    17. LF

      ... and online education?

    18. PN

      Right.

    19. LF

      And how do we close that gap, if it's even possible?

    20. PN

      Yeah. So, I think there's two issues. One is whether it's in person or online, so sort of the physical location, and then the other is, uh, kind of the affiliation, right? So, you stuck with it in part because you were in the classroom and you saw everybody else was suffering-

    21. LF

      Right. (laughs)

    22. PN

      ... the same, the same way you were.

    23. LF

      Yeah.

    24. PN

      Uh, but also because you were enrolled, you had paid tuition.

    25. LF

      Yeah.

    26. PN

      Sort of everybody was expecting you to stick with it. Uh-

    27. LF

      Mm-hmm. Society, parents-

    28. PN

      Yeah.

    29. LF

      ... c- uh, peers.

    30. PN

      Right.

  8. 32:4337:12

    Learning to program in 10 years

    1. LF

      So our field, programming, you've also done a lot of, you've done a lot of programming yourself. In, uh, 2001, you wrote a great article about programming called Teach Yourself Programming in 10 Years. Sort of responds to-

    2. PN

      Yeah.

    3. LF

      ... all the books that say Teach Yourself Programming in 21 Days. So, if you were giving advice to someone getting into programming today, this is, uh, a few years since you've written that article, what's the best way to undertake that journey?

    4. PN

      I think there's lots of different ways and I think, uh, programming means more things now. And I guess, you know, when I wrote that article, I was thinking more about becoming a professional software engineer. And I thought that's a, you know, a c- sort of a career-long, uh, field of study. Uh, but I think there's lots of things now that people can do where programming is a part of solving what they wanna solve, uh, without it achieving that professional-level status.

    5. LF

      Yeah.

    6. PN

      Right? So, I'm not gonna be going and writing a million lines of code, but, you know, I'm a biologist or a physicist or something, or a, even a historian, and I've got some data, and I wanna ask a question of that data. And I think for that, uh, you don't need 10 years, right? So, eith- there are many shortcuts to, uh, being able to a- answer those kinds of questions. And, and you know, you see today a lot of, uh, emphasis on, uh, learning to code-

    7. LF

      Mm-hmm.

    8. PN

      ... teaching kids how to code. Uh, I think that's great. Uh, but I wish they would change the message a little bit, right? So, I think code isn't the main thing. I don't really care if you know the syntax of JavaScript or if you can, uh, connect these blocks together in this visual language. Uh, but what I do care about is that you can analyze a problem, uh, you can, uh, think of a solution, you can, uh, carry out, uh, you know, make a model, run that model, test the model, see the results, uh, uh, verify that they're reasonable, uh, ask questions and answer them. Right? So, it's more, uh, modeling and problem-solving-

    9. LF

      Mm-hmm.

    10. PN

      ... and you use coding in order to do that, uh, but it's not just learning coding for its own sake.

    11. LF

      That's really interesting. So, it's actually almost, in many cases, it's learning to work with data, to extract-

    12. PN

      Yeah.

    13. LF

      ... something useful-

    14. PN

      Yeah.

    15. LF

      ... out of data. So, when you say problem-solving, you really mean taking some kind of, maybe collecting some kind of dataset, cleaning it up, and saying something interesting about it-

    16. PN

      Yeah.

    17. LF

      ... which is useful in all kinds of domains.

    18. PN

      And, uh, you know, and I see myself, uh, being stuck sometimes in kind of the, the old ways.

    19. LF

      Mm-hmm.

    20. PN

      Right? So, you know, I'll be working on a project, uh, maybe with a, a younger employee and we say, "Oh, well, here's this new package that could help solve this, uh, problem." And I'll go and I'll start reading the manuals and, you know, I'll be-

    21. LF

      (laughs)

    22. PN

      ... two hours into reading the manuals and then, uh, my colleague comes back and says, "I'm done."

    23. LF

      Yup.

    24. PN

      You know? "I downloaded the package. I installed it. I tried calling some things. The first one didn't work. The second one worked. Now I'm done." And, and I say, "But I have 100 questions about how does this work and how does that work?" And they say, "Who cares," right? "I don't need to understand the whole thing. I unders- I answered my question. It's a big complicated package. I don't understand the rest of it, but I got the right answer." And I'm just, it's hard for me to get into that mindset. I want to understand the whole thing and, you know, if they wrote a manual, I should probably read it. And, but that's not necessarily the right way. And I, I think I have to get used to dealing with more, being more comfortable with uncertainty and not knowing everything.

    25. LF

      Yeah. So, I struggle with the same. It's sort of the, the spectrum between Donald, Don Knuth-

    26. PN

      Yeah.

    27. LF

      ... who's kind of the very, you know, b- before he can say anything m-... about a problem, he really has to get down to the machine code as, uh, assembly.

    28. PN

      Yeah.

    29. LF

      Versus exactly what you said, of, uh... of several students in my group that, uh, you know, 20 years old and they can solve almost any problem within a few hours that would take me probably weeks, because I would try to, as you said, read the manual. So, do you think the nature of mastery is... You're, you're mentioning biology, sort of outside disciplines, applying programming, but

  9. 37:1240:01

    Changing nature of mastery

    1. LF

      computer scientists... So over time, there's higher and higher levels of abstraction available now. So with, with, uh, this week-

    2. PN

      Hm. Yeah.

    3. LF

      ... there's the, the TensorFlows Summit, right?

    4. PN

      Yeah.

    5. LF

      (laughs) So if you're, if you're not particularly into deep learning, but you're still a computer scientist, uh, you can accomplish an incredible amount with, uh, TensorFlow without really knowing any fundamental internals of machine learning. Do you think the nature of mastery is, is changing, uh, even for computer scientists, like what it means to be an expert programmer?

    6. PN

      Yeah, I think that's true. You know, we never really should have focused on programmer, right? Because that's still... it's, it's a skill and what we really want to focus on is the result. So we, we built this, uh, ecosystem where the way you can get stuff done is by programming it yourself.

    7. LF

      Right.

    8. PN

      At least when I started, it... you know, library functions meant you had square root and that was about it.

    9. LF

      (laughs)

    10. PN

      (laughs) Right?

    11. LF

      Yeah.

    12. PN

      Everything else you built from scratch.

    13. LF

      Yeah.

    14. PN

      And then we built up an ecosystem where a lot of times, well, you can download a lot of stuff that does-

    15. LF

      Yeah.

    16. PN

      ... a big part of what you need. And so now, it's more a question of, uh, assembly rather than, uh, uh, manufacturing, and, uh, that's a different way of looking at problems.

    17. LF

      From another perspective, in terms of mastery and looking at programmers or people that reason about problems in a computational way, so Google, uh, you know, the... from the hiring perspective, from the perspective of hiring or building a team of programmers, uh, how do you determine if someone's a good programmer? Or if somebody... again-

    18. PN

      Yeah.

    19. LF

      ... because I don't want to deviate from... I want to move away from the word programmer, but somebody who could solve problems of large-scale data and so on. What's, what's, uh... how do you build a team like that through the interviewing process for them?

    20. PN

      Yeah, and I, and I think, uh, as a company grows, uh, you get more, uh, expansive in the types of people you're looking for, right? So, uh, I think, you know, in the early days, we'd interview people and the question we were trying to ask is, uh, how close are they to Jeff Dean?

    21. LF

      (laughs)

    22. PN

      (laughs) And most people-

    23. LF

      Sure.

    24. PN

      ... were pretty far away.

    25. LF

      Yeah.

    26. PN

      But we'd take the ones that were, you know, not that far away.

    27. LF

      Yeah.

    28. PN

      And so we got kind of a homogeneous group of people who were really great programmers.

    29. LF

      Yeah.

    30. PN

      Uh, then as the company grows, you say, "Well, we don't want everybody to be the same, to have the same skillset." And so now, we're, uh, hiring, uh, biologists in our health areas and we're hiring physicists and we're hiring, uh, mechanical engineers and we're hiring, uh, you know, uh, social scientists and ethnographers and people with different backgrounds, uh, who bring different skills.

  10. 40:0141:17

    Code review

    1. LF

      Mm-hmm. So you, uh, mentioned that you, uh, still may partake in code reviews. Given that you have a wealth of experience, as you've also mentioned (laughs) , uh, what errors do you often see and tend to highlight in the code of junior developers, of people coming up now, uh, given your background from LISP-

    2. PN

      Oh.

    3. LF

      ... to, uh, a couple of decades of programming?

    4. PN

      Yeah, that's a great question. You know, sometimes I try to look at the flexibility of the design, of, yes, you know, this API solves this problem, but, uh, where is it going to go in the future? Who else is gonna wanna call this?

    5. LF

      Mm-hmm.

    6. PN

      And, uh, you know, are, are you making it easier for them to do that?

    7. LF

      Is this a matter of, uh, design? Is it documentation? Is it, is it, uh, sort of an amorphous thing you can't really-

    8. PN

      Yeah.

    9. LF

      ... put into words? It's just how it feels? If you put yourself in the shoes of a developer, would you use this kind of thing?

    10. PN

      I think it is how you feel, right?

    11. LF

      Right.

    12. PN

      And so, yeah, documentation is good, uh, but it's, but it's more a design question, right? If you get the design right, then people will figure it out, whether the documentation's good or not, and if-

    13. LF

      Right.

    14. PN

      ... and if the design's wrong, uh, then it'll be harder to use.

    15. LF

      How have,

  11. 41:1743:05

    How have you changed as a programmer

    1. LF

      uh, you, yourself, changed as a programmer-

    2. PN

      (laughs)

    3. LF

      ... over the years, as... in, in the way... you've already started to say sort of, you want to read the manual, you want to understand the core of the-

    4. PN

      Yeah.

    5. LF

      ... from the syntax to the how the language is supposed to be used and so on. But, uh, what's the evolution been like from the '80s, '90s, to today?

    6. PN

      I guess one thing is, you don't have to worry about, uh, the small details of efficiencies as much-

    7. LF

      Exactly.

    8. NA

      So true.

    9. PN

      ... as you used to, right? So, like, I remember, uh, I did my, uh, LISP book, uh, in the '90s, and one of the things I wanted to do was say, uh, here's how you do an object system, and, uh, basically, uh, we're gonna make it so each object is a hash table, and you look up the methods, and here's how it works. And then I said, "Of course, the real common LISP object system is much more complicated. It's got all these efficiency-type issues-"

    10. LF

      Mm-hmm.

    11. PN

      "... and this is just a toy. Nobody would do this in real life." And it turns out, Python pretty much did exactly- (laughs)

    12. LF

      (laughs)

    13. PN

      ... what I said-

    14. LF

      Yeah.

    15. PN

      ... and said, uh, objects are, uh, just dictionaries. And yeah, they have a few little, uh, tricks as well. But mostly, you know, the thing that would've been 100 times too slow in the '80s is now plenty fast for most everything today.

    16. LF

      So you had to, as a programmer, let go of...... perhaps an obsession that I remember coming up with of trying to write efficient code.

    17. PN

      Yeah, yeah. To say, you know, what really matters is the total time, uh, it takes to get the project done.

    18. LF

      (laughs) Yeah.

    19. PN

      And most of that's gonna be the programmer time.

    20. LF

      Yep.

    21. PN

      Uh, so if you're a little bit less efficient, but it makes it easier to understand and modify, then that's the right trade-off.

  12. 43:0547:41

    LISP

    1. PN

    2. LF

      So, you've written quite a bit about Lisp. Your book on programming is in Lisp. You, you, you have a lot of code out there that's in Lisp. So, um, uh, m- myself and people who don't know what Lisp is should look it up.

    3. PN

      Yeah.

    4. LF

      It's my favorite language. For many AI researchers, it is a favorite language. The favorite language they never use-

    5. PN

      (laughs)

    6. LF

      ... uh, these days. (laughs) Uh, so what part of Lisp do you find most beautiful and powerful?

    7. PN

      So, I think the beautiful part is the simplicity. T- that in half a page, you can define the whole language. And o- other languages don't have that, so you feel like you can hold everything in your head. And then, you know, a lot of people say, "Well, then that's too simple, you know. Here's all these things I wanna do, and uh, you know, my Java or Python or whatever has 100 or 200 or 300 different syntax rules, and don't I need all those?"

    8. LF

      Mm-hmm.

    9. PN

      And Lisp's answer was, "No, we're only gonna give you eight or so s- syntax rules, but we're gonna allow you to define your own."

    10. LF

      Mm-hmm.

    11. PN

      Uh, and so that was a very powerful idea. And I think this idea of saying, uh, "I can start with my problem and with my data, and then I can build the language I want, uh, for that problem and for that data, and then I can make Lisp define that language." So, you, uh, you're sort of, uh, mixing levels and saying, "I'm simultaneously a, a programmer in a language and a language designer," and that allows a better match between your problem and your eventual code. And I think Lisp had, uh, done that better than other languages.

    12. LF

      Yeah, it's a very elegant implementation of functional programming, but why do you think Lisp has not had the mass adoption and success-

    13. PN

      Yeah.

    14. LF

      ... of languages like Python? Is it the parentheses?

    15. PN

      (laughs)

    16. LF

      Is it all the parentheses?

    17. PN

      Yeah. (laughs) Yeah. So, I think a couple things. So, one was, I think it was designed for a single programmer or a small team, and a skilled programmer who had the good taste to say, "Well, I'm, I am doing language design and I have to make g- good choices." And if you make good choices, that's great. If you make bad choices, y- uh, you can hurt yourself.

    18. LF

      Mm-hmm.

    19. PN

      And it can be hard for other people on the team to understand it.

    20. LF

      Right.

    21. PN

      So, I think there was a, a limit to the scale of the size of a project in terms of number of people that Lisp was good for. And as an industry, we kind of grew, uh, beyond that. I think it is in part the parentheses. You know, one of the jokes is the acronym for Lisp is, uh, Lots Of Irritating Silly Parentheses.

    22. LF

      (laughs)

    23. PN

      Uh, my acronym was, uh, Lisp Is Syntactically Pure, saying all you need is parentheses and atoms. But I remember, you know, so we had the, the AI textbook and, uh, because we did it in the '90s, we had, uh, we had pseudocode in the book, but then we said, "Well, we'll have Lisp online," 'cause that's the language of AI at the time.

    24. LF

      Mm-hmm.

    25. PN

      And I remember some of the students complaining 'cause they hadn't had Lisp before and they didn't quite understand what was going on. And, and I remember one student complained, "I don't understand how this pseudocode corresponds to this Lisp." And there was a one-to-one correspondence between the (laughs) the, uh, symbols in the code and the pseudocode, and the only thing difference was the parentheses.

    26. LF

      (laughs)

    27. PN

      (laughs) So, I said, "It must be that for some people, a certain number of left parentheses shuts off their brain."

    28. LF

      (laughs) Yeah, it's very, it's very possible in that sense, and Python just goes the other way.

    29. PN

      Yeah.

    30. LF

      It just-

  13. 47:4148:32

    Python

    1. LF

      So, what's the story in Python behind pyTudes? Your GitHub repository-

    2. PN

      Yeah.

    3. LF

      ... with puzzles and exercises in Python is pretty fun.

    4. PN

      Yeah, just, uh, uh, it seemed like fun. Uh, you, you know, I like, uh, doing puzzles and I like, uh, being an educator. I, I did a class with Udacity, uh, Udacity 212, I think it was, that was basically problem-solving, uh, uh, using Python and looking at different problems. And-

    5. LF

      Does pyTudes feed that class, uh, in terms of the exercises? I was wondering what the-

    6. PN

      Uh, yeah, so the class, the class came first.

    7. LF

      Yeah.

    8. PN

      Some of the stuff that's in pyTudes was write-ups of what was in the class, and then some of it was just continuing to, uh, to, uh, work on new problems.

    9. LF

      So, what's the organizing madness of pyTudes? Is it just a-

    10. PN

      Yeah, it's just-

    11. LF

      ... collec- a, a collection of cool exercises?

    12. PN

      Just whatever I thought was fun.

    13. LF

      Okay, awesome.

  14. 48:3253:24

    Early days of Google Search

    1. LF

      So, you were the director of search quality at Google from-

    2. PN

      Yeah.

    3. LF

      ... 2001, '02, to 2005. In the early days, uh, when there was just a few employees and when the-

    4. PN

      Yeah.

    5. LF

      ... when the company was growing like crazy, right? So-Th- I mean, Google revolutionized the way we discover, and share, and aggregate knowledge, so just, this is, uh, this is one of the fundamental aspects of civilization, right, is information being shared, and there's different mechanisms throughout history, but Google has just 10X improved that, right? And you're a part of that, right? People discovering that information. So, what, what were some of the challenges on a philosophical or the technical level in those early days?

    6. PN

      It definitely was an exciting time, and as you say, we were doubling in size every year. And the challenges were, we wanted to get the right answers, (laughs) right? And, uh, we had to figure out what that meant. We had to implement that, and we had to make it all, uh, efficient and, uh... We had to keep on testing and seeing if we were delivering good answers. Uh-

    7. LF

      And now when you say good answers, it means whatever people are typing in, in terms of keywords, in terms of that kind of thing, that the- that the results they get are ordered by the desirability for them of those results. Like, they're like... The first thing they click on will likely be the thing that they were actually looking for.

    8. PN

      Right. One of the metrics we had was focused on the first thing. Uh, some of it wa- fo- was focused on the whole page. Some of it was focused on, you know, the top three or so. So, we looked at a lot of different metrics for- for how well we were doing, and we broke it down into subclasses of, you know, maybe here's a type of, uh- of, uh, query that we're not doing well on. Then we try to fix that. Uh, early on, we started to realize that we were in an adversarial position, right? So, we started thinking, uh, "Well, we're kind of like the card catalog in the library."

    9. LF

      Mm-hmm.

    10. PN

      Right? So, the books are here, and we're off to the side and- and we're just, uh, reflecting what's there. And then we realized every time we make a change, the webmasters make a change.

    11. LF

      (laughs)

    12. PN

      And it's, uh, game theoretic. And so we had to think not only of, is this the right move for us to make now? But also, if we make this move, what's the countermove gonna be? Is that gonna get us into a work- worse place? In which case we won't make that move, we'll make a different move.

    13. LF

      And did you find... I mean, I assume with the popularity and the growth of the internet, that people were creating new content. So, you're almost helping guide the creation of new content.

    14. PN

      Yeah. So, that's certainly true, right? So, we- we kn- we definitely changed, uh, the structure of the network, right? So, if you think back, you know, in the- in the very early days, uh, uh, Larry and Sergey had the PageRank paper, and Jon Kleinberg had this, uh, hubs and authorities model, which says the web is made out of these, uh, hubs, which will be my page of cool links about dogs or whatever-

    15. LF

      Mm-hmm.

    16. PN

      ... and people would just list links. Uh, and then there'd be authorities, which were the ones, uh, that- page about dogs that most people link to. That doesn't happen anymore. People don't bother to say, "My page of cool links-"

    17. LF

      Mm-hmm.

    18. PN

      ... uh, 'cause we took over that function, right? So- so, uh, we changed th- the way that worked.

    19. LF

      Did you imagine back then that the internet would be as massively vibrant as it is today? I mean, it was already growing quickly, but it's just another... I- I don't know if you've ever-

    20. PN

      You know-

    21. LF

      ... if you- today, if you sit back and (laughs) just look at the internet with wonder, the amount of content that's just constantly being created, constantly being shared-

    22. PN

      Yeah.

    23. LF

      ... and deployed.

    24. PN

      Yeah. It- it's, uh, it's always been surprising to me.

    25. LF

      (laughs)

    26. PN

      I- I guess I'm not very good at- at, uh-

    27. LF

      Predicting the future?

    28. PN

      ... predicting the future.

    29. LF

      Okay. (laughs)

    30. PN

      Uh, and I remember, you know, being a graduate student in- in 1980 or so, and, uh, you know, we had the ARPANET, and then there was this, uh, proposal to, uh, commercialize it-

  15. 53:2455:14

    What does it take to build human-level intelligence

    1. LF

      the future, what do you think it takes to build a system that approaches human-level intelligence? Y- you've talked about, of course, that w- you know, we shouldn't be so obsessed about creating human-level intelligence, just cr- create systems that are very useful for humans. But what do you think it takes-

    2. PN

      Yeah.

    3. LF

      ... to, uh, to- uh, to, uh, yeah, approach that level?

    4. PN

      Right. So, certainly, I- I don't think human-level intelligence is one thing, right? So, I think-

    5. LF

      Right.

    6. PN

      ... there's lots of different tasks, lots of different capabilities. I also don't think, uh, that should be the goal, right? So, I, you know, I wouldn't want to create a, uh, calculator that could do multiplication at human level, right?

    7. LF

      Right.

    8. PN

      That would- that would be a step backwards. And so for many things, we should be aiming far beyond human level. Uh, for other things, uh, maybe human level is a good level to aim at. Uh, and for others we'd say, "Well, let's not bother doing this 'cause we al- we already have humans who can take on those tasks." So, as you say, I like to focus on, uh, what- what's a useful tool?

    9. LF

      Right.

    10. PN

      And- and in some cases, being at human level is an important part of crossing that threshold to- to make the tool useful. So, we see in- in things like these, uh, uh, personal assistants now that you get either on your phone or on a- a speaker that sits on the table, uh, you wanna be able to have a conversation with those.

    11. LF

      Mm-hmm.

    12. PN

      And- and I think as an industry, we haven't quite figured out what the right model is for what these things can do.

    13. LF

      Right.

    14. PN

      Uh, and we're aiming towards, well, you just have a conversation with them the way you can with a person.

    15. LF

      Right.

    16. PN

      Uh, but we haven't delivered on that model yet, right? So, you can ask it, "What's the weather?" You can ask it-... play some nice songs, uh, and, uh, you know, five or six other things and then you run out of stuff that it can do.

  16. 55:1457:00

    Her

    1. LF

      In terms of, uh, deep meaningful connection, so you've mentioned the movie Her as one of your favorite AI movies. Do you think it's possible for a human being to fall in love with an AI system, AI assistant as you mentioned? So taking this big leap from, uh, "What's the weather?" to, you know-

    2. PN

      Yeah.

    3. LF

      ... having a, a deep connection.

    4. PN

      Yeah. I, I think, uh, as people, that's what we love to do.

    5. LF

      Yeah.

    6. PN

      And, uh, I was at a, uh, a showing of Her where we had a panel discussion and, and somebody asked me, uh, "What other movie do you think Her is similar to?" And my answer was, uh, "Life of Brian." Which, which is not a science fiction movie.

    7. LF

      Mm-hmm.

    8. PN

      Uh, but both movies are about wanting to believe in something that's not necessarily real.

    9. LF

      (laughs) Yeah. By the way, for people who don't know, it's Monty Python. Yeah.

    10. PN

      Yeah.

    11. LF

      (laughs) That's been brilliantly put.

    12. PN

      Right?

    13. LF

      But, so-

    14. PN

      So, uh, I mean, I think that's just the way we are. We, we want to trust, we want to believe, we want to fall in love and, uh, it doesn't necessarily take that much, right? So, uh, you know, my kids, uh, fell in love with their teddy bear.

    15. LF

      Right.

    16. PN

      And the teddy bear was not very interactive, right? (laughs)

    17. LF

      (laughs)

    18. PN

      So that's all us.

    19. LF

      Yeah.

    20. PN

      Pushing our feelings onto our devices and our things, and, and I think that that's what we like to do, so we'll continue to do that.

    21. LF

      So, yeah, as human beings we long for that connection and just AI has to, uh, do a little bit of work to, uh, to c- catch us-

    22. PN

      Yeah.

    23. LF

      ... on the other end.

    24. PN

      Yeah. And certainly, you know, if you can get to, uh, dog level-

    25. LF

      (laughs)

    26. PN

      ... a lot of people have invested a lot of, uh, love in their pets.

    27. LF

      In their pets. Some, some people, uh, as I've been told in working with autonomous vehicles, have invested a lot of love into their inanimate cars.

    28. PN

      Yeah. (laughs)

    29. LF

      So it, it really doesn't take much.

  17. 57:0058:41

    Test of intelligence

    1. LF

    2. PN

      Yeah.

    3. LF

      So what is a good test... to linger on the topic that, uh, may be silly or a little bit philosophical, what is a good test of intelligence in your view? Is natural conversation like in the Turing test a good, a good test? Put another way, what would impress you-

    4. PN

      Yeah.

    5. LF

      ... if you saw a computer do it these days?

    6. PN

      Yeah, I mean, I get impressed all the time, right?

    7. LF

      (laughs) Okay.

    8. PN

      Right? So, uh-

    9. LF

      But like really impress you.

    10. PN

      You know, Go playing, uh, StarCraft playing, uh, those are all pretty cool. You know, and I think, uh, sure, conversation is important. I think, uh, you know, we sometimes have these tests where it's easy to fool the system, where you can have a chatbot that can have a conversation, but you never, uh, it never gets into a situation where it has to be deep enough that, uh, it really reveals itself as, as being in- intelligent or not. I think, uh, you know, Turing suggested that, uh, but I think if he were alive, he'd say, "You know, I didn't really mean that seriously."

    11. LF

      (laughs)

    12. PN

      Right?

    13. LF

      Yeah. Yeah.

    14. PN

      And, and I think, uh, and you know, this is just my opinion, but, but I think Turing's point was not that, uh, this test of conversation is a good test. I think his point was having a test is the right thing.

    15. LF

      Mm-hmm.

    16. PN

      So rather than having the philosopher say, "Oh, no, AI is impossible," you should say, "Well, we'll just have a test and then the result of that will, will tell us the answer." And it doesn't necessarily have to be a conversation test.

    17. LF

      That's right. And coming up a new better test as the technology evolves is probably the right

  18. 58:411:00:58

    Future threats from AI

    1. LF

      way. Do you worry as a lot of the general public does about... not a lot, but some vocal, uh, part of the general public about the existential threat of artificial intelligence? So, looking farther into the future, as you said, most of us are not able to predict much. So when shrouded in such mystery, there's a concern of, well, you think, start thinking about worst case.

    2. PN

      Mm-hmm. Yeah.

    3. LF

      Is that something that occupies your mind space much?

    4. PN

      So I certainly think about, uh, threats, I think about, uh, dangers, uh, and I think, uh, any new technology, uh, has positives and negatives, and if it's a powerful technology, it can be used for bad as well as for good. So I'm certainly not worried about, uh, the robot apocalypse, uh-

    5. LF

      Mm-hmm.

    6. PN

      ... and the Terminator type scenarios. I am worried about change in employment and, uh, are we gonna be re- able to react fast enough to deal with that? I think we're, you know, we're already seeing it today where a lot of people are, are disgruntled about, uh, uh, the way income inequality is, is working and, uh, and automation could help accelerate those kinds of, uh, problems. I see powerful technologies can always be used as weapons, uh, whether they're robots or drones or whatever. Uh, some of that, uh, we're seeing due to AI, a lot of it, uh, you don't need AI.

    7. LF

      Mm-hmm.

    8. PN

      Uh, and I don't know what's a, what's a worse threat if it's a autonomous drone or, uh, it's, uh, CRISPR technology becoming available or... we have lots of, uh, threats to face and some of them involve AI and some of them don't.

    9. LF

      So the threats that technology presents, are you, for the most part, optimistic about technology also alleviating those threats or creating new opportunities or protecting us from the more detrimental effects of these new technologies?

    10. PN

      Yeah, I don't know. It, it... again, it's hard to predict the future and, uh-

    11. LF

      (laughs) Yes.

    12. PN

      ... as a succ- society so far we've survived, uh, nuclear bombs-

    13. LF

      Somehow, yeah.

    14. PN

      ... and, and other things. Of course, uh, only societies that have survived are having this conversation.

    15. LF

      (laughs)

    16. PN

      So, uh, uh, maybe that's a survivorship bias

  19. 1:00:581:02:57

    Exciting open problems in AI

    1. PN

      there.

    2. LF

      Yeah. What problem stands out to you as exciting, challenging, impactful to work on in the near future for yourself, for the community and, and broadly?

    3. PN

      So, I, you know, we talked about these, uh, assistants in conversation. I, I think that's a great area. I think, uh, combining, uh, common sense reasoning, uh, with, uh, the power of data i- is a, a great area.

    4. LF

      In which application? In, in conversation relations or just broadly speaking?

    5. PN

      Just in, in general, yeah. As a programmer, I'm interested in, uh, programming tools, both in terms of, uh, you know, the current systems we have today with, with TensorFlow and so on. Can we make them much easier to use for a broader-

    6. LF

      Mm-hmm.

    7. PN

      ... uh, class of people? And also, can we apply, uh, machine learning to, uh, the more traditional type of programming, right? So, you know, when you go to Google and you, uh, type in a query and you spell something wrong, it says, "Did you mean..."

    8. LF

      Mm-hmm.

    9. PN

      And the reason we're able to do that is 'cause lots of other people made a similar error and then they corrected it. Uh, we should be able to go into our code bases and our bug fix bases and, uh, when I type a line of code, it should be able to say, "Did you mean such and such?" If you type this today, you're probably gonna fi- type in this bug fix, uh, tomorrow.

    10. LF

      Yeah, that's a really exciting application of, uh, almost a, a- an assistant for the coding programming experience-

    11. PN

      Yeah.

    12. LF

      ... at every level. So, I think I could s- safely speak for the entire AI community (laughs) -

    13. PN

      Mm-hmm.

    14. LF

      ... first of all for, uh, thanking you for the amazing work you've done. Uh, certainly for the amazing work you've done with, uh, AI: A Modern Approach book.

    15. PN

      Yeah, thank you.

    16. LF

      I think we're all looking forward very much for the fourth edition and then the fifth edition and so on.

    17. PN

      Yeah, yeah.

    18. LF

      So, uh, Peter, thank you so much for talking today.

    19. PN

      Yeah, thank you. A pleasure.

Episode duration: 1:03:12

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode _VPxEcT_Adc

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.