WEBVTT - The Ghost in the Machine

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to Tech Stuff, a production from I Heart Radio.

0:00:11.840 --> 0:00:16.400
<v Speaker 1>Hey there, and welcome to text Stuff. I'm your scary

0:00:16.440 --> 0:00:20.720
<v Speaker 1>but not Harry host Jonathan Strickland, executive producer with I

0:00:20.880 --> 0:00:24.200
<v Speaker 1>Heart Radio and how the tech are You. We are

0:00:24.280 --> 0:00:27.600
<v Speaker 1>continuing our spooky episode series and the lead up to

0:00:27.640 --> 0:00:32.839
<v Speaker 1>Halloween twenty twenty two. Apologies if you're from the future

0:00:33.200 --> 0:00:38.360
<v Speaker 1>listening back on this episode. That's why the bizarre theme

0:00:38.479 --> 0:00:42.120
<v Speaker 1>is popping up. We've already talked recently about stuff like

0:00:42.360 --> 0:00:47.040
<v Speaker 1>vampire power and zombie computers where I'm really grasping at

0:00:47.040 --> 0:00:51.680
<v Speaker 1>tenuous connections to horror stuff for tech. But now it's

0:00:51.680 --> 0:00:56.720
<v Speaker 1>time to tackle the ghost in the machine. These days,

0:00:57.360 --> 0:01:01.000
<v Speaker 1>that phrase is frequently bandied about with relation to stuff

0:01:01.040 --> 0:01:06.040
<v Speaker 1>like artificial intelligence, But the the man who coined the

0:01:06.080 --> 0:01:10.560
<v Speaker 1>phrase itself was Gilbert Ryle in nineteen nine, and he

0:01:10.720 --> 0:01:15.000
<v Speaker 1>wasn't talking about artificial intelligence at all. He was talking about,

0:01:15.280 --> 0:01:19.479
<v Speaker 1>you know, real intelligence, and he was critiquing a seventeenth

0:01:19.520 --> 0:01:24.720
<v Speaker 1>century philosopher's argument about the human mind. That philosopher was

0:01:24.800 --> 0:01:30.560
<v Speaker 1>Renee des Cartes, who famously wrote cogito ergo sum I drink. Therefore,

0:01:30.600 --> 0:01:33.679
<v Speaker 1>I am sorry it's gonna be impossible for me to

0:01:33.680 --> 0:01:39.120
<v Speaker 1>talk about philosophers without quoting Monty Python because I'm a dork. Okay, No,

0:01:39.319 --> 0:01:43.240
<v Speaker 1>cogito ergo sum actually means I think, therefore I am

0:01:43.360 --> 0:01:46.800
<v Speaker 1>or that's how we interpret it. But that wasn't really

0:01:46.840 --> 0:01:50.919
<v Speaker 1>the bit that Gilbert Ryle was all riled up about.

0:01:51.480 --> 0:01:56.800
<v Speaker 1>See de Cartes believed in dualism. Now, I don't mean

0:01:56.920 --> 0:01:59.400
<v Speaker 1>that he believed in showing up at dawn to sword

0:01:59.480 --> 0:02:02.840
<v Speaker 1>fight other philosophers. Though, if someone wants to make a

0:02:02.840 --> 0:02:07.640
<v Speaker 1>philosopher version of Highlander, I am down with that and

0:02:07.640 --> 0:02:11.200
<v Speaker 1>I will back your Kickstarter. No. No, deke Hart believed

0:02:11.680 --> 0:02:15.760
<v Speaker 1>that the mind and you know, consciousness and sentience and

0:02:15.760 --> 0:02:19.720
<v Speaker 1>all this kind of stuff are separate from the actual

0:02:20.280 --> 0:02:24.520
<v Speaker 1>gray matter that resides in our noggains. So, in other words,

0:02:25.000 --> 0:02:28.440
<v Speaker 1>intelligence and awareness and all that other stuff that makes

0:02:28.560 --> 0:02:34.440
<v Speaker 1>you you exists independently of your physical brain. That there

0:02:34.560 --> 0:02:39.120
<v Speaker 1>is this this component that is beyond the physical. Now,

0:02:39.240 --> 0:02:43.240
<v Speaker 1>Ryle referred to this concept as the ghost in the machine,

0:02:43.840 --> 0:02:47.800
<v Speaker 1>that somehow all the things that represent you are you know,

0:02:47.880 --> 0:02:51.919
<v Speaker 1>to too great effect, ethereally independent of the brain itself.

0:02:52.320 --> 0:02:56.520
<v Speaker 1>And Ryle rejects that notion. And you know, Ryle appears

0:02:56.520 --> 0:02:59.800
<v Speaker 1>to be right. We know this because there are plenty

0:02:59.840 --> 0:03:03.919
<v Speaker 1>of case studies focusing on people who have experienced brain injuries,

0:03:04.280 --> 0:03:08.560
<v Speaker 1>either from some physical calamity or a disease or something

0:03:08.560 --> 0:03:13.800
<v Speaker 1>along those lines. And these events often transform people and

0:03:13.919 --> 0:03:19.639
<v Speaker 1>change their behaviors and their underlying personalities. So the damage

0:03:19.680 --> 0:03:23.240
<v Speaker 1>to the physical stuff inside our heads can change who

0:03:23.320 --> 0:03:27.320
<v Speaker 1>we are as people. That seems to dismiss this concept

0:03:27.480 --> 0:03:31.520
<v Speaker 1>of dualism, that the mind and the brain are not

0:03:32.000 --> 0:03:38.040
<v Speaker 1>separate entities. Take that decartes anyway. That's where we get

0:03:38.040 --> 0:03:41.040
<v Speaker 1>the phrase the ghost in the machine. The machine in

0:03:41.080 --> 0:03:44.720
<v Speaker 1>this case is a biological one in the original sense

0:03:44.760 --> 0:03:49.120
<v Speaker 1>of the phrase. In nineteen sixty seven, Arthur Kustler he

0:03:49.200 --> 0:03:52.200
<v Speaker 1>wrote a book called The Ghost in the Machine and

0:03:52.720 --> 0:03:54.680
<v Speaker 1>or at least it was published in nineteen sixty seven,

0:03:54.760 --> 0:04:00.560
<v Speaker 1>and he was a Hungarian born Austrian educated journalist. So

0:04:00.720 --> 0:04:04.560
<v Speaker 1>his book The Ghost of the Machine was an attempt

0:04:04.600 --> 0:04:09.880
<v Speaker 1>to examine and explain humanity's tendency towards violence, as well

0:04:09.920 --> 0:04:13.360
<v Speaker 1>as going over the mind body problem that Ryle had

0:04:13.400 --> 0:04:15.920
<v Speaker 1>addressed when he coined the phrase to begin with in

0:04:16.040 --> 0:04:19.280
<v Speaker 1>nineteen forty nine. All right, then, flash forward a couple

0:04:19.320 --> 0:04:22.880
<v Speaker 1>of decades one and we get the title of what

0:04:22.960 --> 0:04:26.760
<v Speaker 1>was the fourth studio album of the Police, you know,

0:04:26.920 --> 0:04:31.160
<v Speaker 1>Sting and the Police. Now I say this in case

0:04:31.200 --> 0:04:33.680
<v Speaker 1>you were thinking that Sting and Company were naming their

0:04:33.720 --> 0:04:37.320
<v Speaker 1>album off the technological use of the term ghost of

0:04:37.360 --> 0:04:40.520
<v Speaker 1>the Machine, but they were not. Sting good Old Gordy

0:04:40.880 --> 0:04:44.599
<v Speaker 1>had read Cussler's book and he took the album's title

0:04:44.760 --> 0:04:48.400
<v Speaker 1>from the book title. So in case you're wondering, that's

0:04:48.400 --> 0:04:51.119
<v Speaker 1>also the album that brought us songs like every little

0:04:51.160 --> 0:04:55.160
<v Speaker 1>thing she does is magic and spirits in the material world.

0:04:56.120 --> 0:05:01.120
<v Speaker 1>For a really recent exploration of due all is um well,

0:05:01.279 --> 0:05:04.599
<v Speaker 1>arguably it's more than dualism. I guess you can actually

0:05:04.600 --> 0:05:09.839
<v Speaker 1>watch Pixars Inside Out. That's a film that solidified my

0:05:09.920 --> 0:05:13.680
<v Speaker 1>reputation as an unfeeling monster among my friends because I

0:05:13.720 --> 0:05:16.880
<v Speaker 1>didn't feel anything when bing Bong meets his final fate.

0:05:16.960 --> 0:05:19.400
<v Speaker 1>I just couldn't care. I mean, he's not even real

0:05:19.560 --> 0:05:22.960
<v Speaker 1>in the context of the film, let alone in my world,

0:05:23.000 --> 0:05:27.200
<v Speaker 1>so why would I? Okay, never mind? Anyway. In Inside Out,

0:05:27.680 --> 0:05:32.799
<v Speaker 1>we learned that our emotions are actual anthropomorphic entities living

0:05:32.839 --> 0:05:38.080
<v Speaker 1>inside our heads that share the controls to our behavior

0:05:38.160 --> 0:05:41.760
<v Speaker 1>that we are in effect governed by our emotions, and

0:05:41.880 --> 0:05:45.600
<v Speaker 1>our emotions in turn are the responsibilities of entities like

0:05:46.200 --> 0:05:50.919
<v Speaker 1>joy and anger and disgust. They cart probably would have

0:05:50.960 --> 0:05:55.000
<v Speaker 1>been thrilled, and Ralph likely would have rolled his eyes. Anyway,

0:05:55.000 --> 0:05:58.039
<v Speaker 1>the trope of having a little voice inside your head

0:05:58.640 --> 0:06:02.680
<v Speaker 1>that is somehow separate from you and also you is

0:06:02.720 --> 0:06:05.680
<v Speaker 1>a really popular one. I always think of Homer Simpson,

0:06:05.960 --> 0:06:09.000
<v Speaker 1>who will often find himself arguing with his own brain

0:06:09.120 --> 0:06:13.640
<v Speaker 1>for comedic effect. It's another example of dualism in popular culture.

0:06:14.000 --> 0:06:17.719
<v Speaker 1>But the idiom the ghost of the machine survived its

0:06:17.760 --> 0:06:22.359
<v Speaker 1>initial philosophical and journalistic trappings, and now folks tend to

0:06:22.480 --> 0:06:25.920
<v Speaker 1>use it to describe stuff that's actually in the technological world.

0:06:26.160 --> 0:06:29.320
<v Speaker 1>We're talking about machines, as in the stuff that we

0:06:29.400 --> 0:06:32.040
<v Speaker 1>humans make, as opposed to the stuff that we are

0:06:33.360 --> 0:06:37.200
<v Speaker 1>generally in tech. The phrase describes the situation in which

0:06:37.240 --> 0:06:41.839
<v Speaker 1>a technological device or construct behaves in a way counter

0:06:41.960 --> 0:06:45.960
<v Speaker 1>to what we expect or want. Uh. At least that

0:06:46.040 --> 0:06:47.800
<v Speaker 1>was the way it was used for quite some time.

0:06:47.960 --> 0:06:51.359
<v Speaker 1>So for example, let's say that you've got yourself a

0:06:51.440 --> 0:06:55.720
<v Speaker 1>robotic vacuum cleaner, and you've set the schedule so that

0:06:55.800 --> 0:06:58.720
<v Speaker 1>it's only going to run early in the afternoon. And

0:06:58.760 --> 0:07:02.560
<v Speaker 1>then one fight, you wake up hearing the worrying and

0:07:02.680 --> 0:07:05.680
<v Speaker 1>bumping of your room ba as it aimlessly wanders your

0:07:05.720 --> 0:07:09.800
<v Speaker 1>home in search of dirt and dust to consume, and

0:07:09.840 --> 0:07:12.040
<v Speaker 1>you spend a few sleepy moments wondering if there's some

0:07:12.120 --> 0:07:15.920
<v Speaker 1>sort of conscientious intruder who's made their way into your

0:07:15.960 --> 0:07:19.760
<v Speaker 1>house and now they're tidying up before you realize, no,

0:07:19.920 --> 0:07:23.760
<v Speaker 1>it's that darn robot vacuum cleaner. There's a ghost in

0:07:23.880 --> 0:07:26.600
<v Speaker 1>the machine. It's decided on its own to come awake

0:07:26.640 --> 0:07:30.000
<v Speaker 1>and start working. Now, alternatively, maybe you just goofed up

0:07:30.040 --> 0:07:32.040
<v Speaker 1>when you create the schedule and you mixed up your A,

0:07:32.240 --> 0:07:35.560
<v Speaker 1>M S and your PMS. That's also a possibility. But

0:07:36.120 --> 0:07:38.840
<v Speaker 1>you know, sometimes technology does behave in a way that

0:07:38.960 --> 0:07:42.880
<v Speaker 1>we don't expect. Either there's a malfunction or it just

0:07:43.200 --> 0:07:47.080
<v Speaker 1>encounters some sort of scenario that it was not designed for,

0:07:47.200 --> 0:07:50.040
<v Speaker 1>and so the result it produces is not the one

0:07:50.120 --> 0:07:53.840
<v Speaker 1>we want, and we tend to try and kind of

0:07:53.920 --> 0:07:57.040
<v Speaker 1>cover that up with this. This blanket explanation of ghosts

0:07:57.040 --> 0:08:00.280
<v Speaker 1>in the machine kind of stands as a placeholder until

0:08:00.280 --> 0:08:04.160
<v Speaker 1>we can really suss out what's going on underneath. Programmers

0:08:04.240 --> 0:08:07.320
<v Speaker 1>sometimes use the phrase ghost in the machine to describe

0:08:07.400 --> 0:08:11.600
<v Speaker 1>moments where you get something unexpected while you're coding, Like

0:08:11.640 --> 0:08:14.480
<v Speaker 1>you get an unexpected result, like you've coded something to

0:08:14.560 --> 0:08:19.120
<v Speaker 1>produce a specific outcome and something else happens instead. So

0:08:20.360 --> 0:08:24.200
<v Speaker 1>the programmer didn't intend for this result to happen, and

0:08:24.280 --> 0:08:28.080
<v Speaker 1>so therefore the cause must be external, right, It's got

0:08:28.080 --> 0:08:30.840
<v Speaker 1>to be some sort of ghost of the machine that's

0:08:30.880 --> 0:08:33.360
<v Speaker 1>causing this to go wrong. Now I'm joshing a bit here.

0:08:33.400 --> 0:08:37.160
<v Speaker 1>Of course, Usually this is a way for a programmer

0:08:37.200 --> 0:08:39.439
<v Speaker 1>to kind of acknowledge that things are not going to plan,

0:08:40.120 --> 0:08:42.439
<v Speaker 1>and that they need to go back and look over

0:08:42.480 --> 0:08:45.160
<v Speaker 1>their code much more closely to find out what's going on.

0:08:45.240 --> 0:08:49.480
<v Speaker 1>Where did things go wrong? Does encoding all it takes

0:08:49.559 --> 0:08:52.720
<v Speaker 1>is like a skipped step where you know you just

0:08:52.960 --> 0:08:56.080
<v Speaker 1>you just missed a thing and you you went on

0:08:56.080 --> 0:08:59.760
<v Speaker 1>one step beyond where you thought you were, or maybe

0:08:59.760 --> 0:09:02.400
<v Speaker 1>you may to typo you got some missed key strokes

0:09:02.440 --> 0:09:04.840
<v Speaker 1>in there. That can be all it takes to make

0:09:04.920 --> 0:09:07.280
<v Speaker 1>a program misbehave, and so then you have to hunt

0:09:07.320 --> 0:09:10.560
<v Speaker 1>down the bugs they're causing the problem. But you know,

0:09:10.640 --> 0:09:13.319
<v Speaker 1>if a program is acting very oddly, you might call

0:09:13.400 --> 0:09:17.559
<v Speaker 1>it a ghost of the machine scenario. Now, I'm not

0:09:17.679 --> 0:09:21.280
<v Speaker 1>sure about the timeline for when folks in the tech

0:09:21.320 --> 0:09:24.920
<v Speaker 1>space began to appropriate the phrase ghost in the machine

0:09:25.000 --> 0:09:27.760
<v Speaker 1>for their work, because when it comes to stuff like this,

0:09:28.320 --> 0:09:31.719
<v Speaker 1>you're really entering the world of folklore, and folklore is

0:09:31.800 --> 0:09:36.080
<v Speaker 1>largely an oral tradition, where you are passing ideas along

0:09:36.440 --> 0:09:39.560
<v Speaker 1>one person to the next, speaking about it. There's not

0:09:39.600 --> 0:09:43.760
<v Speaker 1>necessarily a firm written record, at least not one where

0:09:43.800 --> 0:09:46.160
<v Speaker 1>you can point to something and say this is where

0:09:46.200 --> 0:09:49.280
<v Speaker 1>it began, not like Ryle's version of the phrase goes

0:09:49.360 --> 0:09:52.120
<v Speaker 1>to the machine itself, which was published, so we can

0:09:52.160 --> 0:09:54.960
<v Speaker 1>point to that. They're saying, this is where the phrase

0:09:55.000 --> 0:09:57.800
<v Speaker 1>comes from. This would be what Richard Dawkins would refer

0:09:57.840 --> 0:10:01.640
<v Speaker 1>to as a meme, a little nugget of culture that

0:10:01.720 --> 0:10:06.360
<v Speaker 1>gets passed on from person to person. But it also

0:10:06.480 --> 0:10:11.120
<v Speaker 1>has been used in literature to refer to technological situations.

0:10:11.600 --> 0:10:15.880
<v Speaker 1>Arthur C. Clark, whom I've referenced many times in this show,

0:10:16.160 --> 0:10:19.240
<v Speaker 1>as he's the guy who explained that any sufficiently advanced

0:10:19.240 --> 0:10:23.920
<v Speaker 1>technology is indistinguishable from magic. He also used the phrase

0:10:24.240 --> 0:10:28.440
<v Speaker 1>ghost in the Machine to talk about AI. Specifically, he

0:10:28.600 --> 0:10:31.480
<v Speaker 1>used it in his follow up to his novel, his

0:10:31.520 --> 0:10:34.800
<v Speaker 1>work of fiction, two thousand one, A Space Odyssey. The

0:10:34.880 --> 0:10:39.400
<v Speaker 1>follow up is called, fittingly enough, two thousand ten Odyssey to.

0:10:40.679 --> 0:10:45.480
<v Speaker 1>Chapter forty two of two thousand ten is titled the

0:10:45.559 --> 0:10:48.559
<v Speaker 1>Ghost in the Machine, and the focal point for that

0:10:48.640 --> 0:10:54.040
<v Speaker 1>chapter is characters discussing how that's the AI system from

0:10:54.080 --> 0:10:56.760
<v Speaker 1>two thousand one that caused all the trouble. So quick

0:10:56.840 --> 0:10:58.840
<v Speaker 1>recap of two thousand one for those of you not

0:10:58.920 --> 0:11:02.360
<v Speaker 1>familiar with the story, UH and two thousand and one.

0:11:02.440 --> 0:11:05.199
<v Speaker 1>The film, the Stanley Kubrick film gets pretty loosey goosey,

0:11:05.280 --> 0:11:08.120
<v Speaker 1>So we're just gonna focus on the main narrative. Here.

0:11:08.520 --> 0:11:12.880
<v Speaker 1>You have a crew aboard a spacecraft, an American spacecraft

0:11:12.920 --> 0:11:17.280
<v Speaker 1>called Discovery one, which is on its way towards Jupiter. Now,

0:11:17.320 --> 0:11:21.680
<v Speaker 1>the ship has a really sophisticated computer system called HOW

0:11:21.880 --> 0:11:26.600
<v Speaker 1>nine thousand that controls nearly everything on board. UH. Also

0:11:26.720 --> 0:11:30.520
<v Speaker 1>fun little trivia effect, how h L means that the

0:11:30.520 --> 0:11:35.040
<v Speaker 1>initials are each one letter off from IBM, though Arthur C.

0:11:35.040 --> 0:11:39.720
<v Speaker 1>Clark would claim that that was not intentional anyway. How

0:11:40.400 --> 0:11:43.960
<v Speaker 1>begins to act erratically in the mission. At one point,

0:11:44.000 --> 0:11:47.400
<v Speaker 1>How insists there's a malfunction in a system that appears

0:11:47.440 --> 0:11:51.880
<v Speaker 1>to be perfectly functional, that it's working just fine. Then

0:11:51.960 --> 0:11:56.040
<v Speaker 1>How systematically begins to eliminate the crew after learning they

0:11:56.040 --> 0:11:59.520
<v Speaker 1>plan to disconnect the computer system because they suspect something's

0:11:59.520 --> 0:12:03.600
<v Speaker 1>going wrong. How figures out that plan by monitoring a

0:12:03.600 --> 0:12:07.480
<v Speaker 1>conversation that a couple of crew members have in a

0:12:07.679 --> 0:12:11.199
<v Speaker 1>room where there are no microphones. So How can't listen

0:12:12.000 --> 0:12:14.960
<v Speaker 1>in on this conversation, But How is able to direct

0:12:15.000 --> 0:12:17.840
<v Speaker 1>a video feed to that room and is able to

0:12:17.920 --> 0:12:20.880
<v Speaker 1>read the lips of the crew members as they talk

0:12:20.960 --> 0:12:25.679
<v Speaker 1>about their plan. So How continues to try and wipe

0:12:25.720 --> 0:12:28.880
<v Speaker 1>everybody out, and he explains or it I shouldn't give

0:12:28.920 --> 0:12:33.800
<v Speaker 1>him a gender. How explains that the computer systems being

0:12:33.800 --> 0:12:37.160
<v Speaker 1>turned off would jeopardize the mission, and How cannot allow

0:12:37.200 --> 0:12:40.800
<v Speaker 1>that to happen. How's prime directive is to make certain

0:12:40.840 --> 0:12:43.840
<v Speaker 1>the mission as a success, so anything that would threaten

0:12:43.920 --> 0:12:47.120
<v Speaker 1>its own existence has to be eliminated. There's also the

0:12:47.120 --> 0:12:51.000
<v Speaker 1>implication that How does not want to cease to exist,

0:12:51.040 --> 0:12:55.200
<v Speaker 1>that How has a personal motivation beyond seeing the mission

0:12:55.240 --> 0:12:58.760
<v Speaker 1>to completion, and so How has no choice but to

0:12:58.840 --> 0:13:01.319
<v Speaker 1>kill everyone. It's not that Al wants to murder everyone,

0:13:01.440 --> 0:13:03.560
<v Speaker 1>is just that in order to complete the mission, that's

0:13:03.600 --> 0:13:07.520
<v Speaker 1>the only outcome that makes sense. Eventually, one of the crew,

0:13:07.840 --> 0:13:12.240
<v Speaker 1>Dave Bowman, manages to turn off How and How wonders allowed.

0:13:12.360 --> 0:13:17.439
<v Speaker 1>What will happen afterward? Will its consciousness continue once its

0:13:17.440 --> 0:13:23.240
<v Speaker 1>circuits are powered down? Will I dream? It? Says? Well? Anyway?

0:13:23.240 --> 0:13:26.439
<v Speaker 1>In Odyssey Too, you now have this group of astronauts

0:13:26.480 --> 0:13:31.920
<v Speaker 1>and cosmonauts in a Soviet American joint effort that are

0:13:32.440 --> 0:13:36.960
<v Speaker 1>trying to figure out what happened with How. Was there

0:13:37.200 --> 0:13:42.480
<v Speaker 1>something inherently flawed in How's programming? Did some external element

0:13:42.600 --> 0:13:48.440
<v Speaker 1>cause how to malfunction? Did How's apparent consciousness emerge spontaneously

0:13:48.559 --> 0:13:51.720
<v Speaker 1>all on its own? Was it all just a sophisticated

0:13:51.720 --> 0:13:55.200
<v Speaker 1>trick and How never really had any sort of consciousness?

0:13:55.240 --> 0:13:57.720
<v Speaker 1>It only appeared to. So the crew are kind of

0:13:57.800 --> 0:14:01.360
<v Speaker 1>left to ponder this themselves. They don't have any easy answers.

0:14:02.040 --> 0:14:05.280
<v Speaker 1>That's just one example of the ghost of the machine

0:14:05.320 --> 0:14:09.480
<v Speaker 1>concept being handled in entertainment. When we come back, I'll

0:14:09.480 --> 0:14:12.640
<v Speaker 1>talk about a different one. But first, let's take this

0:14:12.760 --> 0:14:24.880
<v Speaker 1>quick break. Okay, Before the break, I talked about Arthur C.

0:14:24.880 --> 0:14:28.600
<v Speaker 1>Clark and his work with the concept of ghosts of

0:14:28.600 --> 0:14:32.520
<v Speaker 1>the machine. Let's now leap over to Isaac Asimov, or

0:14:32.520 --> 0:14:36.040
<v Speaker 1>at least an adaptation of Asimov's work. So the film

0:14:36.200 --> 0:14:40.120
<v Speaker 1>version of I Robot, which really bears only a passing

0:14:40.160 --> 0:14:45.240
<v Speaker 1>resemblance to the short stories that Isaac Asimov wrote that

0:14:45.360 --> 0:14:49.080
<v Speaker 1>we're also collected in a book called I Robot, uses

0:14:49.160 --> 0:14:52.600
<v Speaker 1>the phrase ghost of the machine. Isaac Asimov, by the way,

0:14:52.600 --> 0:14:54.800
<v Speaker 1>in case you're not familiar with his work, he's the

0:14:54.800 --> 0:14:59.680
<v Speaker 1>guy who also proposed the basic laws of robotics, which

0:15:00.200 --> 0:15:03.640
<v Speaker 1>are pretty famous as well. So in the film, the

0:15:03.760 --> 0:15:08.120
<v Speaker 1>character Dr Alfred Lanning, who actually does appear in asthmov stories,

0:15:08.160 --> 0:15:11.240
<v Speaker 1>but he's a very different version than the one that

0:15:11.280 --> 0:15:14.720
<v Speaker 1>appears in the film. He says in a voiceover quote,

0:15:15.120 --> 0:15:19.200
<v Speaker 1>there have always been ghosts in the machine, random segments

0:15:19.200 --> 0:15:22.880
<v Speaker 1>of code that have grouped together to form unexpected protocols.

0:15:23.240 --> 0:15:28.880
<v Speaker 1>Unanticipated these free radicals in gender, questions of free will, creativity,

0:15:28.960 --> 0:15:31.640
<v Speaker 1>and even the nature of what we might call the soul.

0:15:32.200 --> 0:15:35.680
<v Speaker 1>Why is it that when some robots are left in darkness,

0:15:35.960 --> 0:15:38.440
<v Speaker 1>they will seek out the light? Why is it that

0:15:38.480 --> 0:15:41.320
<v Speaker 1>when robots are stored in an empty space, they will

0:15:41.320 --> 0:15:45.040
<v Speaker 1>group together rather than stand alone. How do we explain

0:15:45.120 --> 0:15:49.400
<v Speaker 1>this behavior random segments of code or is it something more?

0:15:49.920 --> 0:15:54.360
<v Speaker 1>When does a perceptual schematic become consciousness? When does a

0:15:54.480 --> 0:15:58.880
<v Speaker 1>difference engine become the search for truth? When does a

0:15:58.960 --> 0:16:02.680
<v Speaker 1>personality simulate should become the bitter mote of a soul?

0:16:03.720 --> 0:16:07.520
<v Speaker 1>End quote. There's some fun references in there too. Difference engine,

0:16:07.520 --> 0:16:12.920
<v Speaker 1>for example, refers back to Charles Babbage, who created analytical

0:16:13.040 --> 0:16:22.120
<v Speaker 1>engines that predate the concept of electrical computers. Now this idea, this,

0:16:22.120 --> 0:16:26.800
<v Speaker 1>this idea of of consciousness or the appearance of consciousness

0:16:26.840 --> 0:16:30.080
<v Speaker 1>emerging out of technology, is one that often pops up

0:16:30.080 --> 0:16:34.240
<v Speaker 1>in discussions about artificial intelligence, even within our world outside

0:16:34.240 --> 0:16:37.160
<v Speaker 1>of fiction, though usually we talk about this on a

0:16:37.160 --> 0:16:42.320
<v Speaker 1>more hypothetical basis, unless you're Blake Lemoyne or Lemois, the

0:16:42.360 --> 0:16:46.400
<v Speaker 1>former Google engineer who maintains that Google's language model for

0:16:46.480 --> 0:16:51.480
<v Speaker 1>dialogue applications a K A lambda is sentient. That's a

0:16:51.520 --> 0:16:54.680
<v Speaker 1>claim that most other people dispute, By the way, so

0:16:55.760 --> 0:16:58.880
<v Speaker 1>maybe I'll do another episode about it to really kind

0:16:58.880 --> 0:17:02.960
<v Speaker 1>of dig into it. But Lemoyne or LEMOI and I

0:17:03.000 --> 0:17:05.480
<v Speaker 1>apologize because I don't know how his last name is

0:17:05.640 --> 0:17:09.360
<v Speaker 1>is pronounced. Has said a few times that he believes

0:17:09.840 --> 0:17:14.160
<v Speaker 1>that this particular program has gained sentience. But it brings

0:17:14.240 --> 0:17:17.280
<v Speaker 1>us to another favorite topic among tech fans, which is,

0:17:17.320 --> 0:17:21.359
<v Speaker 1>of course, the Turing test. All right, So the Turing

0:17:21.440 --> 0:17:24.719
<v Speaker 1>test was Alan Turing, who he was kind of like

0:17:24.760 --> 0:17:27.600
<v Speaker 1>the father of computer science in many ways. It was

0:17:27.720 --> 0:17:33.439
<v Speaker 1>his response to the question can machines think? Turing's answer

0:17:33.600 --> 0:17:36.200
<v Speaker 1>was that question has no meaning, and you r s

0:17:36.320 --> 0:17:40.280
<v Speaker 1>L E person goodbye. I am, of course paraphrasing, but

0:17:40.560 --> 0:17:43.560
<v Speaker 1>as a sort of thought experiment, Turing proposed taking an

0:17:43.560 --> 0:17:47.800
<v Speaker 1>older concept called the imitation game and applying it to machines,

0:17:48.119 --> 0:17:53.359
<v Speaker 1>really to demonstrate how meaningless the question of can machines think? Is? So,

0:17:53.960 --> 0:17:56.760
<v Speaker 1>what is the imitation game? Well, the name kind of

0:17:56.760 --> 0:17:59.159
<v Speaker 1>gives it away. It's a game in which you have

0:17:59.200 --> 0:18:02.880
<v Speaker 1>a player who asks at least two different people questions

0:18:02.920 --> 0:18:07.040
<v Speaker 1>to determine which of them is an imitator. So, for example,

0:18:07.320 --> 0:18:09.760
<v Speaker 1>you could have an imitation game in which one of

0:18:09.800 --> 0:18:12.800
<v Speaker 1>the people is a sailor and the other is not

0:18:12.960 --> 0:18:16.960
<v Speaker 1>a sailor, and the player would take turns asking each

0:18:17.000 --> 0:18:19.840
<v Speaker 1>person questions to try and suss out which one is

0:18:19.920 --> 0:18:23.320
<v Speaker 1>actually a sailor and which one is merely pretending to

0:18:23.440 --> 0:18:26.080
<v Speaker 1>be a sailor. So the game depends both on the

0:18:26.119 --> 0:18:30.200
<v Speaker 1>strength of the imitator's skill of deception as well as

0:18:30.240 --> 0:18:33.200
<v Speaker 1>the player's ability to come up with really good questions.

0:18:33.760 --> 0:18:35.800
<v Speaker 1>And you could do this with all sorts of scenarios,

0:18:35.840 --> 0:18:38.240
<v Speaker 1>and indeed there are tons of game shows that use

0:18:38.280 --> 0:18:42.439
<v Speaker 1>this very premise. Turings thought experiment was to create a

0:18:42.560 --> 0:18:46.480
<v Speaker 1>version of this in which a player would present questions

0:18:46.480 --> 0:18:51.280
<v Speaker 1>to two other entities, one a human and one a computer.

0:18:52.000 --> 0:18:55.520
<v Speaker 1>The player would only know these entities as X and Y,

0:18:55.800 --> 0:18:58.160
<v Speaker 1>so they could ask questions of X, and they could

0:18:58.200 --> 0:19:01.720
<v Speaker 1>ask questions of why and it replies, So the player

0:19:01.760 --> 0:19:05.200
<v Speaker 1>would not be able to see or hear the other entities.

0:19:05.480 --> 0:19:08.199
<v Speaker 1>All questions would have to be done in writing, you know,

0:19:08.240 --> 0:19:12.399
<v Speaker 1>for example, typed and printed out, and at the end

0:19:12.440 --> 0:19:14.800
<v Speaker 1>of the interview session, the player would be tasked with

0:19:14.880 --> 0:19:17.840
<v Speaker 1>deciding if X was a machine or a human, or

0:19:17.880 --> 0:19:21.119
<v Speaker 1>if why was the machine or the human. Touring was

0:19:21.160 --> 0:19:25.880
<v Speaker 1>suggesting that as computers and systems get more sophisticated, and

0:19:25.960 --> 0:19:29.680
<v Speaker 1>things like chat programs get better at processing natural language

0:19:29.680 --> 0:19:33.080
<v Speaker 1>and formulating responses, though that was a little past during

0:19:33.280 --> 0:19:36.560
<v Speaker 1>time that it would be increasingly difficult for a person

0:19:36.600 --> 0:19:39.919
<v Speaker 1>to determine if any given entity on the other end

0:19:39.920 --> 0:19:43.080
<v Speaker 1>of a chat session was actually a person or a machine,

0:19:43.720 --> 0:19:46.959
<v Speaker 1>And Touring also rather cheekly suggests that we might as

0:19:46.960 --> 0:19:50.680
<v Speaker 1>well assume the machine has consciousness at that point, because

0:19:50.720 --> 0:19:54.359
<v Speaker 1>when you meet another human being, you assume that that

0:19:54.520 --> 0:19:59.000
<v Speaker 1>other human being possesses consciousness, even though you're incapable of

0:19:59.000 --> 0:20:02.879
<v Speaker 1>stepping into that person's actual experience. So you can't take

0:20:03.040 --> 0:20:05.159
<v Speaker 1>over that person and find out, oh, yes, they do

0:20:05.240 --> 0:20:09.359
<v Speaker 1>have consciousness, You just assume they do. So if you

0:20:09.400 --> 0:20:11.760
<v Speaker 1>and I were to meet, I assume you would believe

0:20:11.800 --> 0:20:15.320
<v Speaker 1>I am in fact sentient and conscious even on my

0:20:15.400 --> 0:20:18.600
<v Speaker 1>bad days. So if we're willing to agree to this

0:20:19.480 --> 0:20:24.320
<v Speaker 1>while simultaneously being unable to actually experience and therefore prove it,

0:20:25.080 --> 0:20:28.520
<v Speaker 1>then should we not grant the same consideration to machines

0:20:28.840 --> 0:20:32.600
<v Speaker 1>that give off the appearance of sentience and consciousness. Do

0:20:32.680 --> 0:20:35.159
<v Speaker 1>we have to prove it or do we just go

0:20:35.200 --> 0:20:38.240
<v Speaker 1>ahead and treat them as if they are, because that's

0:20:38.240 --> 0:20:40.560
<v Speaker 1>what we would do if it was a human. Now,

0:20:40.560 --> 0:20:43.240
<v Speaker 1>Touring was being a bit dismissive about the concept of

0:20:43.280 --> 0:20:47.440
<v Speaker 1>machines thinking. His point was that they might get very

0:20:47.560 --> 0:20:51.479
<v Speaker 1>very good at simulating thinking, and that might well be

0:20:51.600 --> 0:20:54.040
<v Speaker 1>enough for us to just go ahead and say that's

0:20:54.080 --> 0:20:57.040
<v Speaker 1>what they're doing. Even if you could, you know, push

0:20:57.160 --> 0:21:00.280
<v Speaker 1>machines through the finest of sieves and find not one

0:21:00.480 --> 0:21:04.880
<v Speaker 1>grain of actual consciousness within it. Now, it doesn't hurt

0:21:05.480 --> 0:21:09.119
<v Speaker 1>that defining consciousness, even in human terms, is something that

0:21:09.160 --> 0:21:11.520
<v Speaker 1>we can't really do, or at least we don't have

0:21:11.560 --> 0:21:16.399
<v Speaker 1>a unifying definition that everybody agrees upon. Sometimes we define

0:21:16.440 --> 0:21:20.400
<v Speaker 1>consciousness by what it doesn't include rather than what it is.

0:21:21.000 --> 0:21:24.200
<v Speaker 1>This is why I get antsy in philosophical discussions, because

0:21:25.000 --> 0:21:28.679
<v Speaker 1>being sort of a pragmatic dullard myself, it's hard for

0:21:28.720 --> 0:21:31.720
<v Speaker 1>me to keep up. But let's jump ahead and talk

0:21:31.760 --> 0:21:35.480
<v Speaker 1>about a related concept. This is also one that I've

0:21:35.520 --> 0:21:38.760
<v Speaker 1>covered a few times on tech stuff that also points

0:21:38.840 --> 0:21:42.560
<v Speaker 1>to this ghost in the machine idea. And this is

0:21:42.600 --> 0:21:46.879
<v Speaker 1>the argument against machine consciousness and strong AI. It is

0:21:46.920 --> 0:21:51.240
<v Speaker 1>called the Chinese Room John Searle a philosopher but for

0:21:51.440 --> 0:21:54.520
<v Speaker 1>this argument back in nineteen eighty and that argument goes

0:21:54.640 --> 0:21:58.880
<v Speaker 1>something like this. Let's say we've got ourselves a computer,

0:21:59.480 --> 0:22:02.320
<v Speaker 1>and this can eater can accept sheets of paper that

0:22:02.440 --> 0:22:05.919
<v Speaker 1>have Chinese characters written on the paper, and the computer

0:22:05.960 --> 0:22:08.480
<v Speaker 1>can then produce new sheets of paper. It can print

0:22:08.520 --> 0:22:12.040
<v Speaker 1>out sheets that are also covered in Chinese characters, that

0:22:12.160 --> 0:22:15.280
<v Speaker 1>are in response to the input sheets that were fed

0:22:15.320 --> 0:22:20.560
<v Speaker 1>to it. These responses are sophisticated, they are relevant. They're

0:22:20.600 --> 0:22:24.479
<v Speaker 1>good enough that a native Chinese speaker would be certain

0:22:24.600 --> 0:22:28.440
<v Speaker 1>that someone fluent in Chinese was creating the responses, someone

0:22:28.480 --> 0:22:32.480
<v Speaker 1>who understood what was being fed to it was producing

0:22:32.720 --> 0:22:36.399
<v Speaker 1>the output. So, in other words, this system would pass

0:22:36.560 --> 0:22:40.960
<v Speaker 1>the Turing test. But does that mean the system actually

0:22:41.080 --> 0:22:48.440
<v Speaker 1>understands Chinese. Cele's argument is no, it doesn't. He says,

0:22:48.480 --> 0:22:51.879
<v Speaker 1>imagine that you are inside a room, and for the

0:22:51.920 --> 0:22:55.720
<v Speaker 1>purposes of this scenario, you do not understand Chinese. So

0:22:55.760 --> 0:22:59.600
<v Speaker 1>if you do understand Chinese, pretend you don't. Okay. So

0:22:59.760 --> 0:23:02.479
<v Speaker 1>there is a slot on the wall, and through this

0:23:02.520 --> 0:23:05.479
<v Speaker 1>slot you occasionally get sheets of paper, and there are

0:23:05.560 --> 0:23:09.359
<v Speaker 1>Chinese symbols on the sheets of paper. You cannot read these,

0:23:09.400 --> 0:23:11.280
<v Speaker 1>you don't know what they stand for. You don't know

0:23:11.520 --> 0:23:15.000
<v Speaker 1>anything about it other than they're clearly Chinese characters on

0:23:15.119 --> 0:23:19.520
<v Speaker 1>the paper. However, what you do have inside this room

0:23:19.560 --> 0:23:22.639
<v Speaker 1>with you is this big old book of instructions that

0:23:22.720 --> 0:23:25.359
<v Speaker 1>tells you what to do when these papers come in,

0:23:25.720 --> 0:23:28.800
<v Speaker 1>and you use the instructions to find the characters that

0:23:28.840 --> 0:23:32.480
<v Speaker 1>are on the input sheet of paper, and you follow

0:23:32.640 --> 0:23:36.800
<v Speaker 1>a path of instructions to create the corresponding response. Step

0:23:36.960 --> 0:23:39.320
<v Speaker 1>by step, you do it all the way until you

0:23:39.359 --> 0:23:42.760
<v Speaker 1>have created the full response to whatever was sent to you.

0:23:43.400 --> 0:23:46.920
<v Speaker 1>Then you push the response back out the slot. Now

0:23:46.920 --> 0:23:48.480
<v Speaker 1>the person on the other side of the slot is

0:23:48.480 --> 0:23:50.680
<v Speaker 1>going to get a response that appears to come from

0:23:50.800 --> 0:23:54.760
<v Speaker 1>someone who is fluent in Chinese, but you're not. You're

0:23:54.760 --> 0:23:57.760
<v Speaker 1>just following a preset list of instructions. You don't have

0:23:57.800 --> 0:24:01.400
<v Speaker 1>any actual understanding of what's going on. You still don't

0:24:01.440 --> 0:24:04.119
<v Speaker 1>know the meaning of what was given to you. You

0:24:04.160 --> 0:24:07.480
<v Speaker 1>don't even know the meaning of what you produced. You're

0:24:07.520 --> 0:24:12.960
<v Speaker 1>just ignorantly following an algorithm. So externally it appears you understand.

0:24:13.040 --> 0:24:16.400
<v Speaker 1>But if someone were to ask you to translate anything

0:24:16.440 --> 0:24:18.480
<v Speaker 1>you have done, you wouldn't be able to do it.

0:24:19.240 --> 0:24:24.240
<v Speaker 1>So Sarl is arguing against what is called strong AI. Generally,

0:24:24.560 --> 0:24:28.879
<v Speaker 1>we define strong AI as artificial intelligence that processes information

0:24:28.920 --> 0:24:31.439
<v Speaker 1>in a way that is similar to how our human

0:24:31.480 --> 0:24:36.400
<v Speaker 1>brains process information. Strong AI may or may not include

0:24:36.520 --> 0:24:41.320
<v Speaker 1>semi related concepts like sentience and self awareness and consciousness

0:24:41.359 --> 0:24:46.840
<v Speaker 1>and motivations and the ability to experience things, etcetera. So

0:24:47.240 --> 0:24:51.760
<v Speaker 1>Sarah is saying that machines, even incredibly sophisticated machines, are

0:24:51.840 --> 0:24:56.080
<v Speaker 1>incapable of reaching a level of understanding that true intelligence

0:24:56.240 --> 0:24:59.920
<v Speaker 1>can that we humans can grasp things on a level

0:25:00.200 --> 0:25:04.040
<v Speaker 1>machines simply are unable to reach, even if the machines

0:25:04.080 --> 0:25:08.679
<v Speaker 1>can process information faster and in greater quantities than humans

0:25:08.680 --> 0:25:11.840
<v Speaker 1>are able to. Another way of putting this is a

0:25:11.920 --> 0:25:14.960
<v Speaker 1>calculator can multiply two very large numbers and get a

0:25:14.960 --> 0:25:17.800
<v Speaker 1>result much faster than a human could do, but the

0:25:17.840 --> 0:25:22.000
<v Speaker 1>calculator doesn't understand any significance behind the numbers, or even

0:25:22.040 --> 0:25:26.320
<v Speaker 1>if there's a lack of significance, the calculator doesn't have

0:25:26.520 --> 0:25:31.840
<v Speaker 1>that capability. Now, maybe Searle's argument is valid, and maybe,

0:25:31.840 --> 0:25:36.439
<v Speaker 1>as Touring suggests, it doesn't even matter. So let's talk

0:25:36.600 --> 0:25:42.199
<v Speaker 1>about machine learning for a moment. Machine learning encompasses a

0:25:42.240 --> 0:25:46.400
<v Speaker 1>broad scope of applications and approaches and disciplines, but I'll

0:25:46.440 --> 0:25:50.240
<v Speaker 1>focus on one approach from a very high level. It's

0:25:50.280 --> 0:25:56.440
<v Speaker 1>called generative adversarial networks or g A N s GANS. Okay,

0:25:56.480 --> 0:26:00.119
<v Speaker 1>as the name suggests, this model uses two systems in

0:26:00.240 --> 0:26:04.439
<v Speaker 1>opposition of one another. On one side, you have a

0:26:04.480 --> 0:26:10.399
<v Speaker 1>system that is generative, that is, it generates something. Maybe

0:26:10.400 --> 0:26:14.080
<v Speaker 1>it generates pictures of cats, doesn't really matter, we'll use

0:26:14.119 --> 0:26:16.399
<v Speaker 1>cats for this example. So what does matter is that

0:26:16.480 --> 0:26:20.680
<v Speaker 1>this model is trying to create something that is indistinguishable

0:26:21.040 --> 0:26:24.919
<v Speaker 1>from the real version of that thing. So on the

0:26:25.000 --> 0:26:28.520
<v Speaker 1>other side, you have a system called the discriminator. So

0:26:28.600 --> 0:26:31.440
<v Speaker 1>this is a system that looks for fakes. Its job

0:26:31.600 --> 0:26:35.120
<v Speaker 1>is to sort out real versions of whatever it's designed

0:26:35.160 --> 0:26:38.920
<v Speaker 1>to look for and to flag ones that were generated

0:26:39.119 --> 0:26:42.960
<v Speaker 1>or not real. So with cats as our starting point,

0:26:43.000 --> 0:26:45.520
<v Speaker 1>the discriminator is meant to tell the difference between real

0:26:45.600 --> 0:26:48.879
<v Speaker 1>pictures that have cats and fake pictures of cats, or

0:26:49.000 --> 0:26:51.320
<v Speaker 1>maybe just pictures that don't have cats in them at all.

0:26:51.880 --> 0:26:55.320
<v Speaker 1>So first you have to train up your models, and

0:26:55.480 --> 0:26:58.919
<v Speaker 1>you might do this by setting the task. So let's

0:26:58.920 --> 0:27:04.120
<v Speaker 1>start with the generative system, and you create a system

0:27:04.200 --> 0:27:08.000
<v Speaker 1>that is meant to analyze a bunch of images of cats,

0:27:08.000 --> 0:27:10.200
<v Speaker 1>and you just feed the housands of pictures of cats,

0:27:10.240 --> 0:27:15.280
<v Speaker 1>all these different cats, different sizes and colors and orientations

0:27:15.320 --> 0:27:18.000
<v Speaker 1>and activity. And then you tell the system to start

0:27:18.080 --> 0:27:22.000
<v Speaker 1>making new pictures of cats. And let's say that first

0:27:22.080 --> 0:27:26.480
<v Speaker 1>round that the generative system does is horrific. HP Lovecraft

0:27:26.520 --> 0:27:29.720
<v Speaker 1>would wet himself if he saw the images that this

0:27:29.800 --> 0:27:34.080
<v Speaker 1>computer had created. You see that these horrors from the

0:27:34.080 --> 0:27:37.600
<v Speaker 1>Great Beyond are in no way shape or form cats.

0:27:38.200 --> 0:27:40.840
<v Speaker 1>So you go into the model and you start tweaking

0:27:40.920 --> 0:27:45.159
<v Speaker 1>settings so that the system produces something you know less eldredge.

0:27:45.880 --> 0:27:49.320
<v Speaker 1>And you go again, and you do this lots and

0:27:49.440 --> 0:27:53.080
<v Speaker 1>lots of times, like thousands of times, until the images

0:27:53.080 --> 0:27:56.480
<v Speaker 1>start to look a lot more a cat ish. You

0:27:56.520 --> 0:27:59.920
<v Speaker 1>do something similar with the discriminator model. You feed it

0:28:00.240 --> 0:28:03.520
<v Speaker 1>a bunch of images, some with cats, some without, or

0:28:03.560 --> 0:28:08.040
<v Speaker 1>maybe some with like crudely drawn cats or whatever, and

0:28:08.119 --> 0:28:09.879
<v Speaker 1>you see how many of the system is able to

0:28:09.920 --> 0:28:13.160
<v Speaker 1>suss out. And maybe it doesn't do that good a job.

0:28:13.320 --> 0:28:17.280
<v Speaker 1>Maybe it doesn't identify certain real images of cats properly.

0:28:18.000 --> 0:28:21.360
<v Speaker 1>Maybe it misidentifies images that don't have cats in them.

0:28:21.440 --> 0:28:24.040
<v Speaker 1>So you go into the Discriminator's model and you start

0:28:24.080 --> 0:28:26.840
<v Speaker 1>tweaking it so it gets better and better at identifying

0:28:26.880 --> 0:28:29.639
<v Speaker 1>images that do not have real cats in them. And

0:28:29.680 --> 0:28:32.600
<v Speaker 1>then you set these two systems against each other. The

0:28:32.720 --> 0:28:35.639
<v Speaker 1>generative system is trying to create images that will fool

0:28:35.880 --> 0:28:40.160
<v Speaker 1>the discriminator. The discriminator is trying to identify generated images

0:28:40.200 --> 0:28:43.320
<v Speaker 1>of cats and only allow real images of cats through.

0:28:43.720 --> 0:28:47.200
<v Speaker 1>It is a zero sum game. Winner takes all, and

0:28:47.240 --> 0:28:50.280
<v Speaker 1>the two systems compete against each other, with the models

0:28:50.280 --> 0:28:53.840
<v Speaker 1>for each updating repeatedly so that each gets a bit

0:28:53.960 --> 0:28:57.480
<v Speaker 1>better between sessions. If the generative model is able to

0:28:57.520 --> 0:29:01.880
<v Speaker 1>consistently fool the discriminator, like off the time, the generative

0:29:01.920 --> 0:29:06.600
<v Speaker 1>model is pretty reliably creating good examples. This, by the way,

0:29:06.720 --> 0:29:10.280
<v Speaker 1>is a ridiculous oversimplification of what's going on with generative

0:29:10.320 --> 0:29:13.680
<v Speaker 1>adversarial networks, but you get the idea. This form of

0:29:13.720 --> 0:29:16.280
<v Speaker 1>machine learning starts to feel kind of creepy to some

0:29:16.400 --> 0:29:19.440
<v Speaker 1>of us. Like the ability of a machine to learn

0:29:19.560 --> 0:29:23.240
<v Speaker 1>to do something better seems to be a very human quality,

0:29:23.880 --> 0:29:28.240
<v Speaker 1>something that makes us special. But if we can give

0:29:28.360 --> 0:29:33.960
<v Speaker 1>machines that capability, well, then how are we special or

0:29:34.080 --> 0:29:38.560
<v Speaker 1>are we special at all? That's something I'm going to

0:29:38.720 --> 0:29:41.560
<v Speaker 1>tackle as soon as we come back from this next

0:29:41.640 --> 0:29:53.840
<v Speaker 1>break Okay, we're back now. I would argue that we

0:29:53.880 --> 0:29:57.440
<v Speaker 1>are special. Before the break, I was asking can we

0:29:57.520 --> 0:30:01.000
<v Speaker 1>be special if machines are capable of learning? I think

0:30:01.000 --> 0:30:03.120
<v Speaker 1>we are, and that we're able to do stuff that

0:30:03.200 --> 0:30:07.480
<v Speaker 1>machines as of right now either cannot do, or they

0:30:07.560 --> 0:30:09.800
<v Speaker 1>can do, but they don't do it very well and

0:30:09.840 --> 0:30:13.080
<v Speaker 1>they can only attempt it after a ludicrous amount of time.

0:30:13.800 --> 0:30:18.120
<v Speaker 1>For example, let's talk about opening doors. Several years ago,

0:30:19.400 --> 0:30:22.440
<v Speaker 1>I was at south By Southwest. I attended a panel

0:30:22.480 --> 0:30:27.800
<v Speaker 1>about robotics and artificial intelligence and human computer interactions. In

0:30:27.840 --> 0:30:32.160
<v Speaker 1>that panel, Layla taka Yama, a cognitive and social scientist,

0:30:32.520 --> 0:30:35.400
<v Speaker 1>talked about working in the field of human computer interaction,

0:30:35.760 --> 0:30:38.160
<v Speaker 1>and she mentioned how she was once in an office

0:30:38.240 --> 0:30:40.360
<v Speaker 1>where a robot was in the middle of a hallway,

0:30:40.920 --> 0:30:44.640
<v Speaker 1>sitting motionless. It was just facing a door. What taka

0:30:44.720 --> 0:30:48.280
<v Speaker 1>Yama didn't know is that the robot was processing how

0:30:48.680 --> 0:30:51.960
<v Speaker 1>to open that door, staring at the door and trying

0:30:52.000 --> 0:30:54.240
<v Speaker 1>to figure out how to open it for days on end.

0:30:54.920 --> 0:30:58.240
<v Speaker 1>This was taking a lot of time. Obviously. Now, when

0:30:58.480 --> 0:31:01.720
<v Speaker 1>you think about doors, you realize there can be quite

0:31:01.720 --> 0:31:04.320
<v Speaker 1>a few options. Right, Maybe you need to pull on

0:31:04.360 --> 0:31:06.400
<v Speaker 1>a handle to open the door. Maybe you need to

0:31:06.480 --> 0:31:09.120
<v Speaker 1>push on the door. Maybe there's a door knob that

0:31:09.240 --> 0:31:12.120
<v Speaker 1>first you have to turn before you pull or push.

0:31:12.320 --> 0:31:15.720
<v Speaker 1>Maybe there's a crash bar, also known as a panic bar.

0:31:16.240 --> 0:31:19.560
<v Speaker 1>Those are the horizontal bars on exit doors that you

0:31:19.600 --> 0:31:23.120
<v Speaker 1>push on to open. Frequently they're seen indoors that open

0:31:23.200 --> 0:31:27.040
<v Speaker 1>to an exterior location, like inside schools and stuff. You

0:31:27.080 --> 0:31:31.400
<v Speaker 1>push on them to get out. Maybe it's a revolving door,

0:31:31.440 --> 0:31:34.240
<v Speaker 1>which adds in a whole new level of complexity. But

0:31:34.320 --> 0:31:36.040
<v Speaker 1>you get my point. There are a lot of different

0:31:36.160 --> 0:31:39.760
<v Speaker 1>kinds of doors. Now, we humans pick up on how

0:31:39.800 --> 0:31:43.120
<v Speaker 1>doors work pretty darn quickly. I mean, sure, we might

0:31:43.480 --> 0:31:46.040
<v Speaker 1>be like that one kid in the Far Side cartoon

0:31:46.560 --> 0:31:49.440
<v Speaker 1>where the kids going to the School for the Gifted,

0:31:49.480 --> 0:31:51.440
<v Speaker 1>and he's pushing as hard as he can on a

0:31:51.520 --> 0:31:55.200
<v Speaker 1>door that is labeled pull. That could be us sometimes,

0:31:55.200 --> 0:31:57.560
<v Speaker 1>but we figure it out right, we do a quick push,

0:31:57.640 --> 0:32:01.600
<v Speaker 1>we realize, oh, it's not opening. We pull. Robots it's

0:32:01.640 --> 0:32:05.080
<v Speaker 1>more challenging for them. They are not good at extrapolating

0:32:05.120 --> 0:32:08.560
<v Speaker 1>from past experience, at least not in every field. We

0:32:08.720 --> 0:32:11.640
<v Speaker 1>humans can apply our knowledge from earlier encounters and we

0:32:11.680 --> 0:32:14.640
<v Speaker 1>can build on that. Even if the thing we're facing

0:32:15.040 --> 0:32:18.840
<v Speaker 1>is mostly new to us. We might recognize elements that

0:32:18.920 --> 0:32:22.680
<v Speaker 1>give us a hint on how to proceed. Robots and

0:32:22.760 --> 0:32:27.560
<v Speaker 1>AI aren't really good at doing that. They're also not

0:32:27.680 --> 0:32:30.360
<v Speaker 1>good at associative thinking, which is where we start to

0:32:30.440 --> 0:32:33.920
<v Speaker 1>draw connections between different ideas to come up with something new.

0:32:34.720 --> 0:32:37.600
<v Speaker 1>It's a really important step in the creative process. I

0:32:37.680 --> 0:32:42.520
<v Speaker 1>find myself free associating whenever I'm not actively thinking about something.

0:32:42.720 --> 0:32:45.000
<v Speaker 1>So if I'm doing a mundane task, like if I'm

0:32:45.040 --> 0:32:48.560
<v Speaker 1>washing dishes or I'm mowing the lawn, my brain is

0:32:48.600 --> 0:32:52.560
<v Speaker 1>going nuts free associating ideas and creating new ones. Machines

0:32:52.600 --> 0:32:56.280
<v Speaker 1>are not very good at that for now. Anyway. They

0:32:56.280 --> 0:33:00.960
<v Speaker 1>are not that at mimicking it, but they can't actually

0:33:01.600 --> 0:33:06.640
<v Speaker 1>do it. So, getting back to Laila Takeyama, one of

0:33:06.680 --> 0:33:10.240
<v Speaker 1>the really fascinating bits about that panel I went to

0:33:10.920 --> 0:33:14.760
<v Speaker 1>was a discussion on social cues that robots could have

0:33:15.080 --> 0:33:18.520
<v Speaker 1>in order to alert us humans in that same space.

0:33:19.160 --> 0:33:21.640
<v Speaker 1>What the robot was up to. This was not for

0:33:21.680 --> 0:33:25.000
<v Speaker 1>the robots benefit, but for our benefit. The whole point

0:33:25.040 --> 0:33:28.280
<v Speaker 1>is that these cues would give us an idea of

0:33:28.280 --> 0:33:30.160
<v Speaker 1>what was going on with the robots, So that we

0:33:30.240 --> 0:33:35.360
<v Speaker 1>don't accidentally, you know, interrupt the robots. So you know,

0:33:35.400 --> 0:33:38.360
<v Speaker 1>it might be like the robots in that hallway and

0:33:38.440 --> 0:33:40.920
<v Speaker 1>it's looking at a door, and you're wondering, why is

0:33:40.920 --> 0:33:43.240
<v Speaker 1>this robot shut down in the hallway. But then maybe

0:33:43.280 --> 0:33:46.840
<v Speaker 1>the robot reaches up to apparently kind of scratch its

0:33:46.840 --> 0:33:49.880
<v Speaker 1>head and sort of a huh, what's going on kind

0:33:49.920 --> 0:33:54.000
<v Speaker 1>of gesture, and that might tell you, Oh, the robot

0:33:54.160 --> 0:33:58.360
<v Speaker 1>is actively analyzing something. Don't know exactly what it is,

0:33:58.400 --> 0:34:02.680
<v Speaker 1>but it's clearly working. So maybe I'll step around the

0:34:02.760 --> 0:34:07.239
<v Speaker 1>robot behind it and not interrupt its vision of the

0:34:07.280 --> 0:34:11.239
<v Speaker 1>door it's staring at. The Whole point is that the

0:34:11.280 --> 0:34:15.440
<v Speaker 1>social cues can help us interact more naturally with robots

0:34:15.440 --> 0:34:20.359
<v Speaker 1>and coexist with them within human spaces, so that both

0:34:20.400 --> 0:34:25.360
<v Speaker 1>the humans and the robots can operate well with one another. Also,

0:34:25.800 --> 0:34:29.080
<v Speaker 1>it helps to explain what the robot is doing, because

0:34:29.440 --> 0:34:33.239
<v Speaker 1>if you don't have that, the robots end up being mysterious. Right.

0:34:33.280 --> 0:34:35.839
<v Speaker 1>We can't see into them, we don't understand what they

0:34:35.840 --> 0:34:41.239
<v Speaker 1>are currently trying to do, and mystery can breed distrust.

0:34:41.800 --> 0:34:44.320
<v Speaker 1>That leads to yet another concept in AI that gets

0:34:44.360 --> 0:34:47.960
<v Speaker 1>to this ghost in the machine concept, which is the

0:34:48.000 --> 0:34:52.160
<v Speaker 1>black box. So in this context, a black box refers

0:34:52.160 --> 0:34:55.840
<v Speaker 1>to any system where it is difficult or impossible to

0:34:55.880 --> 0:35:00.200
<v Speaker 1>see how the system works internally. Therefore, the is no

0:35:00.239 --> 0:35:03.200
<v Speaker 1>way of knowing how the system is actually producing any

0:35:03.239 --> 0:35:06.120
<v Speaker 1>given output, or even if the output is the best

0:35:06.239 --> 0:35:09.759
<v Speaker 1>it could do. So with a black box system, you

0:35:09.800 --> 0:35:12.480
<v Speaker 1>feed input into the system and you get output out

0:35:12.480 --> 0:35:14.600
<v Speaker 1>of it, but you don't know what was happening in

0:35:14.640 --> 0:35:17.799
<v Speaker 1>the middle. You don't know what the system did to

0:35:17.960 --> 0:35:22.600
<v Speaker 1>turn the input into output. Maybe there's a sophisticated computer

0:35:22.719 --> 0:35:25.000
<v Speaker 1>in the middle of that system that's doing all the processing.

0:35:25.320 --> 0:35:28.479
<v Speaker 1>Maybe there's a person who doesn't understand Chinese stuck in there.

0:35:29.320 --> 0:35:32.480
<v Speaker 1>Maybe there's a magical ferry that waves a wand and

0:35:32.560 --> 0:35:35.640
<v Speaker 1>produces the result. The problem is we don't know, and

0:35:35.680 --> 0:35:39.280
<v Speaker 1>by not knowing, you cannot be certain that the output

0:35:39.320 --> 0:35:43.160
<v Speaker 1>you're getting is actually the best or even relevant or

0:35:43.400 --> 0:35:46.040
<v Speaker 1>the most likely to be correct based upon the input

0:35:46.080 --> 0:35:49.400
<v Speaker 1>you fed it. So you start making decisions based on

0:35:49.440 --> 0:35:52.600
<v Speaker 1>this output. But because you're not sure that the output

0:35:52.680 --> 0:35:55.839
<v Speaker 1>is actually good, you therefore can't be sure that the

0:35:55.880 --> 0:35:59.560
<v Speaker 1>decisions you're making are the best, and that leads to

0:35:59.680 --> 0:36:04.960
<v Speaker 1>really difficult problems. So let's take a theoretical example. Let's

0:36:04.960 --> 0:36:08.560
<v Speaker 1>say we've built a complex computer model that's designed to

0:36:08.640 --> 0:36:12.480
<v Speaker 1>project the effects of climate change. And let's say this

0:36:12.520 --> 0:36:18.600
<v Speaker 1>model is so complex and so recursive on itself that

0:36:18.719 --> 0:36:21.799
<v Speaker 1>it effectively becomes impossible for us to know whether or

0:36:21.840 --> 0:36:25.279
<v Speaker 1>not the model is actually working properly. Well, that would

0:36:25.280 --> 0:36:28.000
<v Speaker 1>mean we wouldn't really be able to rely on any

0:36:28.040 --> 0:36:31.480
<v Speaker 1>predictions or projections made by this model. I mean, maybe

0:36:31.480 --> 0:36:35.360
<v Speaker 1>the projections are accurate, but maybe they're not. The issue

0:36:35.400 --> 0:36:36.960
<v Speaker 1>is there's no way for us to be certain, and

0:36:37.040 --> 0:36:39.840
<v Speaker 1>yet we have a need to act. Climate change is

0:36:39.840 --> 0:36:44.160
<v Speaker 1>a thing, and we need to make changes to reduce

0:36:44.239 --> 0:36:48.640
<v Speaker 1>its impact or to mitigate it. It's possible that any

0:36:48.640 --> 0:36:51.440
<v Speaker 1>decisions we make based upon the output of the system

0:36:51.800 --> 0:36:56.120
<v Speaker 1>will exacerbate the problem, or maybe it'll just be, you know,

0:36:56.239 --> 0:37:01.040
<v Speaker 1>less effective than alternative decisions would be. Further, we're getting

0:37:01.080 --> 0:37:05.480
<v Speaker 1>closer to that Arthur C. Clark statement about sufficiently advanced

0:37:05.520 --> 0:37:09.799
<v Speaker 1>technologies being indistinguishable from magic. If we produce systems that

0:37:09.840 --> 0:37:13.040
<v Speaker 1>are so complicated that it's impossible for us to understand

0:37:13.080 --> 0:37:16.560
<v Speaker 1>them fully, we might begin to view those technologies as

0:37:16.600 --> 0:37:19.520
<v Speaker 1>being magical. Or the very least greater than the some

0:37:19.719 --> 0:37:24.319
<v Speaker 1>of their parts, and this can lead to some illogical decisions.

0:37:25.160 --> 0:37:28.920
<v Speaker 1>This kind of brings me to talk about the church

0:37:28.960 --> 0:37:31.920
<v Speaker 1>of Ai called the Way of the Future, which was

0:37:32.000 --> 0:37:37.359
<v Speaker 1>founded and then later dissolved by Anthony Lewandowski. You may

0:37:37.400 --> 0:37:40.640
<v Speaker 1>have heard Lewandowski's name if you followed the drama of

0:37:40.680 --> 0:37:44.600
<v Speaker 1>his departure from Google and his eventual employment and subsequent

0:37:44.719 --> 0:37:48.240
<v Speaker 1>termination from Uber. And then there was also the fact

0:37:48.239 --> 0:37:51.800
<v Speaker 1>that he was sentenced to go to prison for stealing

0:37:52.480 --> 0:37:56.480
<v Speaker 1>UH company secrets and then later received a presidential pardon

0:37:56.719 --> 0:38:02.479
<v Speaker 1>from Donald Trump. So quick recap on Lewandowski. Lewandowski worked

0:38:02.480 --> 0:38:06.759
<v Speaker 1>within Google's autonomous vehicle division, which would eventually become a

0:38:06.800 --> 0:38:11.439
<v Speaker 1>full subsidiary of Google's parent company, Alphabet, and that subsidiary

0:38:11.520 --> 0:38:15.760
<v Speaker 1>is called Weymo. So when Lewandowski left Google, he brought

0:38:15.800 --> 0:38:19.600
<v Speaker 1>with him a whole lot of data, data that Google

0:38:19.680 --> 0:38:23.720
<v Speaker 1>claimed belonged to the company and was proprietary and nature

0:38:23.760 --> 0:38:28.799
<v Speaker 1>and thus constituted company secrets. Lewandowski eventually began working with

0:38:28.920 --> 0:38:33.000
<v Speaker 1>Uber in that company's own driverless vehicle initiative, but the

0:38:33.040 --> 0:38:37.840
<v Speaker 1>Google slash Weymo investigation would lead to Uber hastily firing

0:38:37.920 --> 0:38:42.040
<v Speaker 1>Lewandowski and sort of an attempt to kind of disentangle

0:38:42.200 --> 0:38:46.400
<v Speaker 1>Uber from this matter, which only worked a little bit anyway.

0:38:46.440 --> 0:38:50.320
<v Speaker 1>In the midst of all this Weymo slash Uber drama,

0:38:50.800 --> 0:38:54.960
<v Speaker 1>in two thousand seventeen, Wired ran an article that explained

0:38:54.960 --> 0:38:58.760
<v Speaker 1>that this same Anthony Lewandowski had formed a church called

0:38:58.880 --> 0:39:01.680
<v Speaker 1>Way of the Future a couple of years earlier. In

0:39:01.760 --> 0:39:05.280
<v Speaker 1>twenty he placed himself at the head of this church

0:39:05.600 --> 0:39:08.600
<v Speaker 1>with the title of Dean, and he also became the

0:39:08.719 --> 0:39:13.520
<v Speaker 1>CEO of the nonprofit organization designed to run the church.

0:39:14.440 --> 0:39:19.440
<v Speaker 1>The aim of the church was to see quote the realization, acceptance,

0:39:19.480 --> 0:39:23.840
<v Speaker 1>and worship of a Godhead based on artificial intelligence AI

0:39:24.640 --> 0:39:28.480
<v Speaker 1>developed through computer hardware and software end quote. This is

0:39:28.520 --> 0:39:31.319
<v Speaker 1>according to the founding documents that were filed with the

0:39:31.400 --> 0:39:36.120
<v Speaker 1>US Internal Revenue Service or i r S. Further, Lewandowski

0:39:36.200 --> 0:39:39.000
<v Speaker 1>planned to start seminars based on this very idea later

0:39:39.040 --> 0:39:44.920
<v Speaker 1>in by twenty Lewandowski's jumped from Google to Uber escalated

0:39:45.040 --> 0:39:50.120
<v Speaker 1>into a prison sentence of eighteen months uh and it

0:39:50.280 --> 0:39:54.000
<v Speaker 1>was because he had been found guilty of stealing trade secrets.

0:39:54.400 --> 0:39:58.640
<v Speaker 1>Trump would pardon Lewandowski in January one kind of you know,

0:39:58.920 --> 0:40:02.280
<v Speaker 1>after the insurrection on January six, but before Trump would

0:40:02.360 --> 0:40:06.239
<v Speaker 1>leave office in late January. As for the Way of

0:40:06.280 --> 0:40:09.520
<v Speaker 1>the Future, Lewandowski actually began to shut that down in

0:40:09.680 --> 0:40:13.520
<v Speaker 1>June of and it was dissolved by the end of

0:40:14.360 --> 0:40:18.759
<v Speaker 1>but not reported on until like February. He directed the

0:40:18.760 --> 0:40:23.200
<v Speaker 1>assets of the church some dollars to be donated to

0:40:23.239 --> 0:40:27.799
<v Speaker 1>the Inn double a CP. Lewandowski has said that the

0:40:27.920 --> 0:40:32.799
<v Speaker 1>beliefs behind the church are ones that he still adheres to,

0:40:33.600 --> 0:40:39.600
<v Speaker 1>that AI has the potential to tackle very challenging problems

0:40:39.640 --> 0:40:43.560
<v Speaker 1>like taking care of the planet, which Lewandowski says, obviously

0:40:43.600 --> 0:40:47.520
<v Speaker 1>we humans are incapable of doing that. You know, we

0:40:47.560 --> 0:40:51.440
<v Speaker 1>would put on this system taking care of things that

0:40:52.000 --> 0:40:54.640
<v Speaker 1>we understand to be important, but we seem to be

0:40:55.360 --> 0:40:59.520
<v Speaker 1>uh incapable of of handling ourselves, almost like we're children.

0:41:00.040 --> 0:41:05.000
<v Speaker 1>Thus looking at AI like a godhead, so we should

0:41:05.000 --> 0:41:09.440
<v Speaker 1>seek out solutions with AI rather than locking AI away

0:41:09.520 --> 0:41:13.880
<v Speaker 1>and saying, oh, we can't push a eyes development further

0:41:14.000 --> 0:41:17.840
<v Speaker 1>in these directions because of the potential existential dangers that

0:41:17.960 --> 0:41:23.480
<v Speaker 1>could emerge from AI becoming super intelligent. I don't think

0:41:23.480 --> 0:41:25.880
<v Speaker 1>there are actually that many folks who are trying to

0:41:26.000 --> 0:41:28.759
<v Speaker 1>lock AI away at all. Mostly I see tons of

0:41:28.760 --> 0:41:33.120
<v Speaker 1>efforts to improve aspects of AI from a million different angles.

0:41:33.480 --> 0:41:39.440
<v Speaker 1>I think most serious AI researchers and scientists aren't really

0:41:39.480 --> 0:41:42.759
<v Speaker 1>focused on strong AI at all. They're looking at very

0:41:42.800 --> 0:41:48.239
<v Speaker 1>particular applications of artificial intelligence, very particular implementations of it.

0:41:48.640 --> 0:41:52.239
<v Speaker 1>But not like a strong AI that acts like deep

0:41:52.360 --> 0:41:58.120
<v Speaker 1>thought from the Hitchhacker's Guide to the Galaxy. Anyway, maybe

0:41:58.239 --> 0:42:02.440
<v Speaker 1>Lewandowski's vision will eventually lead us not to a ghost

0:42:02.680 --> 0:42:07.160
<v Speaker 1>in the machine, but a literal deos x makina that

0:42:07.480 --> 0:42:11.239
<v Speaker 1>means God out of the machine. That seems to be

0:42:11.239 --> 0:42:15.759
<v Speaker 1>how Lewandowski views the potential of a I that are

0:42:15.840 --> 0:42:21.920
<v Speaker 1>unsolvable problems are almost magically fixed thanks to this robotic

0:42:22.160 --> 0:42:27.000
<v Speaker 1>or computational savior you know. In fiction, du s x

0:42:27.040 --> 0:42:30.359
<v Speaker 1>makina is often seen as a cop out. Right, You've

0:42:30.400 --> 0:42:34.920
<v Speaker 1>got your characters in some sort of iron clad disastrous situation,

0:42:35.000 --> 0:42:39.360
<v Speaker 1>there's no escape for them, and then in order to

0:42:39.400 --> 0:42:43.440
<v Speaker 1>get that happy ending, you have some unlikely savior or

0:42:43.560 --> 0:42:48.520
<v Speaker 1>unlikely event happened and everyone gets saved. And it might

0:42:48.560 --> 0:42:51.399
<v Speaker 1>be satisfying because you've got the happy ending, but upon

0:42:51.480 --> 0:42:54.200
<v Speaker 1>critical reflection, you think, well, that doesn't really make sense.

0:42:54.640 --> 0:42:56.200
<v Speaker 1>There are a lot of stories that get a lot

0:42:56.200 --> 0:42:59.560
<v Speaker 1>of flak for using d S X makina uh. The

0:42:59.840 --> 0:43:03.000
<v Speaker 1>m edge I always have is from classical theater, where

0:43:03.120 --> 0:43:06.680
<v Speaker 1>you've got all the mortal characters in a terrible situation

0:43:07.400 --> 0:43:11.360
<v Speaker 1>and then a an actor standing in as a god

0:43:11.600 --> 0:43:14.680
<v Speaker 1>is literally lowered from the top of the stage on

0:43:14.800 --> 0:43:19.000
<v Speaker 1>pulleys to descend to the moral realm and fix everything

0:43:19.000 --> 0:43:21.520
<v Speaker 1>so that you can have a comedy play with a

0:43:21.520 --> 0:43:25.399
<v Speaker 1>happy ending. For Lewandowski, it's really about turning the ghost

0:43:25.440 --> 0:43:28.520
<v Speaker 1>of the machine into a god. I'm not so sure

0:43:28.520 --> 0:43:32.880
<v Speaker 1>about that myself. I don't know if that's a realistic vision.

0:43:33.640 --> 0:43:36.400
<v Speaker 1>I can see the appeal of it, because we do

0:43:36.480 --> 0:43:39.080
<v Speaker 1>have these very difficult problems that we need to solve,

0:43:39.880 --> 0:43:42.799
<v Speaker 1>and we have had very little progress on many of

0:43:42.800 --> 0:43:45.839
<v Speaker 1>those problems for multiple reasons, not just a lack of information,

0:43:46.280 --> 0:43:50.600
<v Speaker 1>but a lack of motivation or conflicting motivations, where we

0:43:50.640 --> 0:43:54.600
<v Speaker 1>have other needs that have to be met that conflict

0:43:54.680 --> 0:43:59.120
<v Speaker 1>with the solving of a tough problem like climate change.

0:43:59.160 --> 0:44:01.080
<v Speaker 1>Right we have energy needs that need to be met.

0:44:01.120 --> 0:44:04.560
<v Speaker 1>There are places in the developing world that would be

0:44:04.600 --> 0:44:09.920
<v Speaker 1>disproportionately affected by massive policies that were meant to mitigate

0:44:09.920 --> 0:44:13.280
<v Speaker 1>climate change, and it's tough to address that. Right There

0:44:13.120 --> 0:44:17.120
<v Speaker 1>are these real reasons why it's a complicated issue beyond

0:44:17.239 --> 0:44:22.680
<v Speaker 1>just it's hard to understand. So I see the appeal

0:44:22.800 --> 0:44:25.640
<v Speaker 1>of it, but it also kind of feels like a

0:44:25.640 --> 0:44:28.000
<v Speaker 1>cop out to me, like this idea of will engineer

0:44:28.040 --> 0:44:30.640
<v Speaker 1>our way out of this problem, because that just puts

0:44:30.840 --> 0:44:34.960
<v Speaker 1>off doing anything about the problem until future you can

0:44:34.960 --> 0:44:37.399
<v Speaker 1>get around to it. I don't know about any of you,

0:44:37.840 --> 0:44:42.200
<v Speaker 1>but I am very much guilty of the idea. You

0:44:42.239 --> 0:44:44.560
<v Speaker 1>know what this is Future Jonathan will take care of this.

0:44:45.040 --> 0:44:46.960
<v Speaker 1>Jonathan right now has to focus on these other things.

0:44:46.960 --> 0:44:49.319
<v Speaker 1>Future Jonathan will take it. Future Jonathan, by the way,

0:44:49.600 --> 0:44:52.960
<v Speaker 1>hates Jonathan of right now and really hates Jonathan in

0:44:53.040 --> 0:44:57.680
<v Speaker 1>the past, because it's just putting things off until it

0:44:57.719 --> 0:44:59.640
<v Speaker 1>gets to a point where you can't do it anymore,

0:44:59.719 --> 0:45:01.319
<v Speaker 1>and by then it might be too late. So that's

0:45:01.320 --> 0:45:03.880
<v Speaker 1>what I worry about with this particular approach, this idea

0:45:03.920 --> 0:45:06.600
<v Speaker 1>of we'll figure it out, we'll science our way out,

0:45:06.600 --> 0:45:10.480
<v Speaker 1>we'll engineer our way out, because it's it's it's projecting

0:45:10.520 --> 0:45:12.880
<v Speaker 1>all that into the future and not doing anything in

0:45:12.920 --> 0:45:17.560
<v Speaker 1>the present anyway. That's the episode on ghost in the machine.

0:45:17.600 --> 0:45:21.040
<v Speaker 1>There's there are other uh interpretations as well. There's some

0:45:21.120 --> 0:45:24.279
<v Speaker 1>great ones in fiction where sometimes you actually have a

0:45:24.320 --> 0:45:27.640
<v Speaker 1>literal ghost in the machine, like there's a haunted machine.

0:45:28.680 --> 0:45:32.840
<v Speaker 1>But maybe I'll wait and tackle that for a future,

0:45:32.920 --> 0:45:36.839
<v Speaker 1>more like entertainment focused episode where it's not so much

0:45:36.840 --> 0:45:41.640
<v Speaker 1>about the technology but kind of a critique of the

0:45:41.800 --> 0:45:44.719
<v Speaker 1>entertainment itself, because there's only so much you can say

0:45:44.719 --> 0:45:50.040
<v Speaker 1>about you know, I don't know a ghost calculator. That's

0:45:50.080 --> 0:45:53.160
<v Speaker 1>it for this episode. If you have suggestions for future

0:45:53.280 --> 0:45:55.960
<v Speaker 1>episode topics or anything else that you would like to

0:45:55.960 --> 0:45:57.600
<v Speaker 1>communicate to me, that a couple of ways you can

0:45:57.600 --> 0:45:59.839
<v Speaker 1>do that. One is you can download the I Heart

0:46:00.040 --> 0:46:03.680
<v Speaker 1>Neio app and navigate over to text stuff. Just put

0:46:03.680 --> 0:46:06.359
<v Speaker 1>tech stuff in the little search field and you'll see

0:46:06.440 --> 0:46:08.560
<v Speaker 1>that it will pop up. You go to the tech

0:46:08.600 --> 0:46:11.880
<v Speaker 1>stuff page and there's a little microphone icon. If you

0:46:11.920 --> 0:46:15.080
<v Speaker 1>click on that, you can leave a voice message up

0:46:15.120 --> 0:46:17.120
<v Speaker 1>to thirty seconds in length and let me know what

0:46:17.160 --> 0:46:19.080
<v Speaker 1>you would like to hear in future episodes. And if

0:46:19.120 --> 0:46:21.120
<v Speaker 1>you like, you can even tell me if I can

0:46:21.280 --> 0:46:25.000
<v Speaker 1>use your voice message in a future episode. Just let

0:46:25.040 --> 0:46:27.200
<v Speaker 1>me know. I'm all about opt in, I'm not gonna

0:46:27.200 --> 0:46:30.120
<v Speaker 1>do it automatically, or if you prefer, you can reach

0:46:30.160 --> 0:46:33.040
<v Speaker 1>out on Twitter. The handle for the show is tech

0:46:33.200 --> 0:46:36.600
<v Speaker 1>Stuff H s W and I'll talk to you again

0:46:37.560 --> 0:46:46.800
<v Speaker 1>really soon. Text Stuff is an I Heart Radio production.

0:46:47.040 --> 0:46:49.880
<v Speaker 1>For more podcasts from my Heart Radio, visit the i

0:46:49.960 --> 0:46:53.200
<v Speaker 1>Heart Radio app, Apple Podcasts, or wherever you listen to

0:46:53.239 --> 0:46:54.160
<v Speaker 1>your favorite shows.