WEBVTT - Rerun: The Ghost in the Machine

0:00:04.480 --> 0:00:12.640
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.640 --> 0:00:15.960
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:16.000 --> 0:00:19.639
<v Speaker 1>I'm an executive producer with iHeart Podcasts and how the

0:00:19.680 --> 0:00:23.320
<v Speaker 1>tech are you. I'm actually a little under the weather today.

0:00:23.920 --> 0:00:28.960
<v Speaker 1>I got my vaccinations for fluent COVID and so I've

0:00:29.000 --> 0:00:32.920
<v Speaker 1>got a few symptoms, nothing serious, but it is hard

0:00:32.960 --> 0:00:38.440
<v Speaker 1>for me to talk, which unfortunately is one of the

0:00:38.560 --> 0:00:43.440
<v Speaker 1>pivotal aspects of podcasting. So while I continue to work

0:00:43.440 --> 0:00:46.800
<v Speaker 1>on episodes, I thought I would bring you an episode

0:00:46.840 --> 0:00:49.440
<v Speaker 1>from just a couple of years ago because spooky times

0:00:49.440 --> 0:00:51.760
<v Speaker 1>are coming up, and with spooky times coming up, I

0:00:51.760 --> 0:00:54.240
<v Speaker 1>thought we could have a spooky times kind of episode,

0:00:54.240 --> 0:00:57.720
<v Speaker 1>at least, you know, tangentially. So I bring to you

0:00:57.760 --> 0:01:02.280
<v Speaker 1>an episode that published on October twenty four, twenty twenty two.

0:01:02.480 --> 0:01:06.720
<v Speaker 1>It is titled The Ghost in the Machine. I hope

0:01:06.720 --> 0:01:15.000
<v Speaker 1>you enjoy. We are continuing our spooky episode series and

0:01:15.040 --> 0:01:19.680
<v Speaker 1>the lead up to Halloween twenty twenty two. Apologies if

0:01:19.959 --> 0:01:23.760
<v Speaker 1>you're from the future listening back on this episode. That's

0:01:24.160 --> 0:01:28.559
<v Speaker 1>why the bizarre theme is popping up. We've already talked

0:01:28.880 --> 0:01:33.160
<v Speaker 1>recently about stuff like Van Bier power and zombie computers

0:01:33.160 --> 0:01:38.240
<v Speaker 1>where I'm really grasping at tenuous connections to horror stuff

0:01:38.480 --> 0:01:41.680
<v Speaker 1>for tech. But now it's time to tackle the ghost

0:01:42.120 --> 0:01:47.560
<v Speaker 1>in the machine. These days, that phrase is frequently bandied

0:01:47.600 --> 0:01:51.960
<v Speaker 1>about with relation to stuff like artificial intelligence. But the

0:01:52.560 --> 0:01:56.600
<v Speaker 1>man who coined the phrase itself was Gilbert Ryle in

0:01:56.680 --> 0:02:01.240
<v Speaker 1>nineteen forty nine, and he wasn't talking about artificial intelligence

0:02:01.280 --> 0:02:05.200
<v Speaker 1>at all. He was talking about, you know, real intelligence,

0:02:05.640 --> 0:02:10.040
<v Speaker 1>and he was critiquing a seventeenth century philosopher's argument about

0:02:10.080 --> 0:02:15.200
<v Speaker 1>the human mind. That philosopher was Renee Descartes, who famously wrote,

0:02:15.320 --> 0:02:20.600
<v Speaker 1>cogito ergo sum, I drink therefore I am sorry. It's

0:02:20.600 --> 0:02:22.840
<v Speaker 1>going to be impossible for me to talk about philosophers

0:02:22.840 --> 0:02:27.240
<v Speaker 1>without quoting Monty Python because I'm a dork. Okay, No,

0:02:27.400 --> 0:02:31.320
<v Speaker 1>cogito ergo sum actually means I think, therefore I am,

0:02:31.480 --> 0:02:34.880
<v Speaker 1>or that's how we interpret it. But that wasn't really

0:02:34.919 --> 0:02:39.040
<v Speaker 1>the bit that Gilbert Ryle was all riled up about.

0:02:39.560 --> 0:02:45.120
<v Speaker 1>See Descartes believed in dualism. Now, I don't mean that

0:02:45.280 --> 0:02:47.760
<v Speaker 1>he believed in showing up at dawn to sword fight

0:02:47.880 --> 0:02:51.600
<v Speaker 1>other philosophers. Though, if someone wants to make a philosopher

0:02:51.760 --> 0:02:55.520
<v Speaker 1>version of Highlander. I am one hundred percent down with that,

0:02:55.639 --> 0:02:59.239
<v Speaker 1>and I will back your kickstarter. No. No, Descartes believed

0:02:59.720 --> 0:03:03.840
<v Speaker 1>that the mind and you know, consciousness and sentience and

0:03:03.840 --> 0:03:07.800
<v Speaker 1>all this kind of stuff are separate from the actual

0:03:08.360 --> 0:03:12.600
<v Speaker 1>gray matter that resides in our noggins. So, in other words,

0:03:13.080 --> 0:03:16.520
<v Speaker 1>intelligence and awareness and all that other stuff that makes

0:03:16.639 --> 0:03:22.519
<v Speaker 1>you you exists independently of your physical brain. That there

0:03:22.600 --> 0:03:27.239
<v Speaker 1>is this this component that is beyond the physical Now,

0:03:27.320 --> 0:03:31.359
<v Speaker 1>Ryle referred to this concept as the ghost in the machine,

0:03:31.919 --> 0:03:35.920
<v Speaker 1>that somehow all the things that represent you are you know,

0:03:35.960 --> 0:03:40.520
<v Speaker 1>to great effect, ethereally independent of the brain itself. And

0:03:40.640 --> 0:03:44.680
<v Speaker 1>Ryle rejects that notion, and you know, Ryle appears to

0:03:44.720 --> 0:03:48.000
<v Speaker 1>be right. We know this because there are plenty of

0:03:48.080 --> 0:03:52.000
<v Speaker 1>case studies focusing on people who have experienced brain injuries,

0:03:52.400 --> 0:03:56.600
<v Speaker 1>either from some physical calamity or a disease or something

0:03:56.640 --> 0:04:01.600
<v Speaker 1>along those lines. And these events all often transform people

0:04:01.760 --> 0:04:07.160
<v Speaker 1>and change their behaviors and their underlying personalities. So the

0:04:07.280 --> 0:04:11.040
<v Speaker 1>damage to the physical stuff inside our heads can change

0:04:11.120 --> 0:04:14.640
<v Speaker 1>who we are as people. That seems to dismiss this

0:04:14.840 --> 0:04:19.400
<v Speaker 1>concept of dualism that the mind and the brain are

0:04:19.480 --> 0:04:25.880
<v Speaker 1>not separate entities. Take that descartes anyway. That's where we

0:04:25.920 --> 0:04:29.040
<v Speaker 1>get the phrase the ghost in the machine. The machine

0:04:29.080 --> 0:04:32.520
<v Speaker 1>in this case is a biological one in the original

0:04:32.560 --> 0:04:36.640
<v Speaker 1>sense of the phrase. In nineteen sixty seven, Arthur Kustler

0:04:37.120 --> 0:04:39.440
<v Speaker 1>he wrote a book called The Ghost in the Machine

0:04:40.040 --> 0:04:42.760
<v Speaker 1>and or at least it was published in nineteen sixty seven,

0:04:42.800 --> 0:04:48.599
<v Speaker 1>and he was a Hungarian born, Austrian educated journalist. So

0:04:48.760 --> 0:04:52.680
<v Speaker 1>his book The Ghost of the Machine was an attempt

0:04:52.680 --> 0:04:57.920
<v Speaker 1>to examine and explain humanity's tendency toward violence, as well

0:04:57.960 --> 0:05:01.480
<v Speaker 1>as going over the mind body problem that Ryle had

0:05:01.480 --> 0:05:04.039
<v Speaker 1>addressed when he coined the phrase to begin with in

0:05:04.120 --> 0:05:07.400
<v Speaker 1>nineteen forty nine. All right, then flash forward a couple

0:05:07.400 --> 0:05:10.360
<v Speaker 1>of decades, nineteen eighty one, and we get the title

0:05:10.400 --> 0:05:14.200
<v Speaker 1>of what was the fourth studio album of the Police,

0:05:14.680 --> 0:05:17.880
<v Speaker 1>you know Sting and the Police. Now I say this

0:05:18.839 --> 0:05:21.240
<v Speaker 1>in case you were thinking that Sting and Company were

0:05:21.320 --> 0:05:25.000
<v Speaker 1>naming their album off the technological use of the term

0:05:25.080 --> 0:05:27.960
<v Speaker 1>ghost of the machine, but they were not. Sting good

0:05:27.960 --> 0:05:31.800
<v Speaker 1>Old Gordy had read Kussler's book, and he took the

0:05:31.880 --> 0:05:35.520
<v Speaker 1>album's title from the book title. So in case you're

0:05:35.520 --> 0:05:38.479
<v Speaker 1>wondering That's also the album that brought us songs like

0:05:38.640 --> 0:05:42.080
<v Speaker 1>every little thing she does as magic and spirits in

0:05:42.120 --> 0:05:49.240
<v Speaker 1>the material world. For a really recent exploration of dualism, well,

0:05:49.360 --> 0:05:52.680
<v Speaker 1>arguably it's more than dualism. I guess you can actually

0:05:52.720 --> 0:05:57.919
<v Speaker 1>watch Pixar's Inside Out. That's a film that solidified my

0:05:58.000 --> 0:06:01.719
<v Speaker 1>reputation as an unfeeling monster among my friends because I

0:06:01.800 --> 0:06:04.960
<v Speaker 1>didn't feel anything when bing Bong meets his final fate.

0:06:05.040 --> 0:06:07.480
<v Speaker 1>I just couldn't care. I mean, he's not even real

0:06:07.680 --> 0:06:11.040
<v Speaker 1>in the context of the film, let alone in my world,

0:06:11.120 --> 0:06:14.560
<v Speaker 1>so why would I know? Okay, never mind anyway. In

0:06:14.560 --> 0:06:19.800
<v Speaker 1>Inside Out, we learn that our emotions are actual anthropomorphic

0:06:20.040 --> 0:06:24.599
<v Speaker 1>entities living inside our heads that share the controls to

0:06:25.000 --> 0:06:29.440
<v Speaker 1>our behavior. That we are in effect governed by our emotions,

0:06:29.640 --> 0:06:33.479
<v Speaker 1>and our emotions, in turn are the responsibilities of entities

0:06:33.640 --> 0:06:38.960
<v Speaker 1>like joy and anger and disgust. Descartes probably would have

0:06:39.000 --> 0:06:43.080
<v Speaker 1>been thrilled and rale Likeli would have rolled his eyes. Anyway,

0:06:43.080 --> 0:06:46.119
<v Speaker 1>The trope of having a little voice inside your head

0:06:46.720 --> 0:06:50.760
<v Speaker 1>that is somehow separate from you and also you is

0:06:50.800 --> 0:06:53.760
<v Speaker 1>a really popular one. I always think of Homer Simpson,

0:06:54.040 --> 0:06:57.080
<v Speaker 1>who will often find himself arguing with his own brain

0:06:57.200 --> 0:07:01.679
<v Speaker 1>for comedic effect. It's another example of doue in popular culture.

0:07:02.080 --> 0:07:05.800
<v Speaker 1>But the idiom the ghost of the machine survived its

0:07:05.880 --> 0:07:10.440
<v Speaker 1>initial philosophical and journalistic trappings, and now folks tend to

0:07:10.560 --> 0:07:13.920
<v Speaker 1>use it to describe stuff that's actually in the technological world.

0:07:14.240 --> 0:07:17.360
<v Speaker 1>We're talking about machines, as in the stuff that we

0:07:17.480 --> 0:07:20.120
<v Speaker 1>humans make, as opposed to the stuff that we are

0:07:21.440 --> 0:07:25.280
<v Speaker 1>generally in tech. The phrase describes a situation in which

0:07:25.320 --> 0:07:29.920
<v Speaker 1>a technological device or construct behaves in a way counter

0:07:30.040 --> 0:07:34.200
<v Speaker 1>to what we expect or want. At least that was

0:07:34.200 --> 0:07:36.120
<v Speaker 1>the way it was used for quite some time. So

0:07:36.640 --> 0:07:40.000
<v Speaker 1>for example, let's say that you've got yourself a robotic

0:07:40.080 --> 0:07:44.080
<v Speaker 1>vacuum cleaner, and you've set the schedule so that it's

0:07:44.120 --> 0:07:47.040
<v Speaker 1>only going to run early in the afternoon, and then

0:07:47.640 --> 0:07:51.200
<v Speaker 1>one night you wake up hearing the worrying and bumping

0:07:51.280 --> 0:07:54.160
<v Speaker 1>of your rumba as it aimlessly wanders your home in

0:07:54.200 --> 0:07:58.320
<v Speaker 1>search of dirt and dust to consume, and you spend

0:07:58.320 --> 0:08:00.560
<v Speaker 1>a few sleepy moments wondering if there's some sort of

0:08:00.640 --> 0:08:04.440
<v Speaker 1>conscientious intruder who's made their way into your house and

0:08:04.480 --> 0:08:08.280
<v Speaker 1>now they're tidying up. Before you realize no, it's that

0:08:08.440 --> 0:08:12.760
<v Speaker 1>darn robot vacuum cleaner. There's a ghost in a machine.

0:08:12.880 --> 0:08:17.000
<v Speaker 1>It's decided on its own to come awake and start working. Now, Alternatively,

0:08:17.080 --> 0:08:19.239
<v Speaker 1>maybe you just goofed up when you created the schedule

0:08:19.240 --> 0:08:22.000
<v Speaker 1>and you mixed up your AMS and your pms. That's

0:08:22.040 --> 0:08:26.360
<v Speaker 1>also a possibility. But you know, sometimes technology does behave

0:08:26.400 --> 0:08:28.400
<v Speaker 1>in a way that we don't expect. Either there's a

0:08:28.440 --> 0:08:33.800
<v Speaker 1>malfunction or it just encounters some sort of scenario that

0:08:33.880 --> 0:08:36.960
<v Speaker 1>it was not designed for, and so the result it

0:08:37.000 --> 0:08:40.079
<v Speaker 1>produces is not the one we want, and we tend

0:08:40.120 --> 0:08:43.079
<v Speaker 1>to try and kind of cover that up with this

0:08:43.600 --> 0:08:46.680
<v Speaker 1>blanket explanation of ghosts in the machine kind of stands

0:08:46.679 --> 0:08:49.720
<v Speaker 1>as a placeholder until we can really suss out what's

0:08:49.840 --> 0:08:53.599
<v Speaker 1>going on underneath. Programmers sometimes use the phrase ghost in

0:08:53.640 --> 0:08:57.880
<v Speaker 1>the machine to describe moments where you get something unexpected

0:08:58.320 --> 0:09:01.400
<v Speaker 1>while you're coding, Like you get an unexpected result, like

0:09:01.440 --> 0:09:05.320
<v Speaker 1>you've coded something to produce a specific outcome, and something

0:09:05.320 --> 0:09:10.760
<v Speaker 1>else happens instead. So the programmer didn't intend for this

0:09:10.880 --> 0:09:15.280
<v Speaker 1>result to happen, and so therefore the cause must be external, Right,

0:09:15.679 --> 0:09:18.760
<v Speaker 1>It's got to be some sort of ghost in the machine.

0:09:18.760 --> 0:09:21.040
<v Speaker 1>That's causing this to go wrong. Now I'm joshing a

0:09:21.040 --> 0:09:24.520
<v Speaker 1>bit here. Of course, Usually this is a way for

0:09:24.600 --> 0:09:26.720
<v Speaker 1>a programmer to kind of acknowledge that things are not

0:09:26.800 --> 0:09:29.640
<v Speaker 1>going to plan and that they need to go back

0:09:29.679 --> 0:09:32.480
<v Speaker 1>and look over their code much more closely to find

0:09:32.480 --> 0:09:35.600
<v Speaker 1>out what's going on. Where did things go wrong? Does

0:09:35.720 --> 0:09:39.760
<v Speaker 1>encoding all it takes is like a skipped step where

0:09:40.120 --> 0:09:42.679
<v Speaker 1>you know you've just you just missed a thing, and

0:09:42.960 --> 0:09:46.480
<v Speaker 1>you you went on one step beyond where you thought

0:09:46.520 --> 0:09:49.400
<v Speaker 1>you were, or maybe you made a typo, you got

0:09:49.400 --> 0:09:52.200
<v Speaker 1>some missed keystrokes in there. That can be all it

0:09:52.240 --> 0:09:54.880
<v Speaker 1>takes to make a program misbehave, and so then you

0:09:54.920 --> 0:09:57.920
<v Speaker 1>have to hunt down the bugs they're causing the problem.

0:09:58.280 --> 0:10:00.760
<v Speaker 1>But you know, if a program is acting very oddly,

0:10:00.880 --> 0:10:04.600
<v Speaker 1>you might call it a ghost of the machine scenario. Now,

0:10:04.720 --> 0:10:09.000
<v Speaker 1>I'm not sure about the timeline for when folks in

0:10:09.040 --> 0:10:12.480
<v Speaker 1>the tech space began to appropriate the phrase ghost in

0:10:12.520 --> 0:10:15.079
<v Speaker 1>the machine for their work, because when it comes to

0:10:15.160 --> 0:10:18.520
<v Speaker 1>stuff like this, you're really entering the world of folklore.

0:10:18.960 --> 0:10:22.839
<v Speaker 1>And folklore is largely an oral tradition where you are

0:10:22.920 --> 0:10:27.120
<v Speaker 1>passing ideas along one person to the next, speaking about it.

0:10:27.280 --> 0:10:30.960
<v Speaker 1>There's not necessarily a firm written record, at least not

0:10:31.040 --> 0:10:33.840
<v Speaker 1>one where you can point to something and say this

0:10:33.920 --> 0:10:36.720
<v Speaker 1>is where it began, Not like Ryle's version of the

0:10:36.760 --> 0:10:39.840
<v Speaker 1>phrase ghost in the Machine itself, which was published, so

0:10:39.880 --> 0:10:42.360
<v Speaker 1>we can point to that as saying this is where

0:10:42.400 --> 0:10:45.400
<v Speaker 1>the phrase comes from. This would be what Richard Dawkins

0:10:45.400 --> 0:10:48.840
<v Speaker 1>would refer to as a meme, a little nugget of

0:10:48.960 --> 0:10:53.320
<v Speaker 1>culture that gets passed on from person to person. But

0:10:53.840 --> 0:10:57.120
<v Speaker 1>it also has been used in literature to refer to

0:10:57.520 --> 0:11:03.200
<v Speaker 1>technological situations. Arthur's Clark, whom I've referenced many times in

0:11:03.280 --> 0:11:06.040
<v Speaker 1>this show, as he's the guy who explained that any

0:11:06.120 --> 0:11:11.520
<v Speaker 1>sufficiently advanced technology is indistinguishable from magic. He also used

0:11:11.520 --> 0:11:16.280
<v Speaker 1>the phrase ghost in the Machine to talk about AI. Specifically,

0:11:16.440 --> 0:11:19.360
<v Speaker 1>he used it in his follow up to his novel,

0:11:19.480 --> 0:11:22.440
<v Speaker 1>his work of fiction two thousand and one, A Space Odyssey.

0:11:22.800 --> 0:11:27.640
<v Speaker 1>The follow up is called, fittingly enough, twenty ten Odyssey two.

0:11:28.760 --> 0:11:34.000
<v Speaker 1>Chapter forty two of twenty ten is titled the Ghost

0:11:34.000 --> 0:11:37.120
<v Speaker 1>in the Machine, and the focal point for that chapter

0:11:37.760 --> 0:11:42.280
<v Speaker 1>is characters discussing how that's the AI system from two

0:11:42.320 --> 0:11:44.840
<v Speaker 1>thousand and one that caused all the trouble so quick

0:11:44.920 --> 0:11:46.720
<v Speaker 1>recap of two thousand and one for those of you

0:11:46.840 --> 0:11:50.400
<v Speaker 1>not familiar with the story and two thousand and one

0:11:50.520 --> 0:11:53.280
<v Speaker 1>the film, the Stanley Kubrick film gets pretty lucy goosey,

0:11:53.360 --> 0:11:56.200
<v Speaker 1>So we're just going to focus on the main narrative here.

0:11:56.559 --> 0:12:00.080
<v Speaker 1>You have a crew aboard a spacecraft and a mayormer

0:12:00.200 --> 0:12:03.880
<v Speaker 1>in spacecraft called Discovery one, which is on its way

0:12:03.880 --> 0:12:08.240
<v Speaker 1>toward Jupiter. Now, the ship has a really sophisticated computer

0:12:08.320 --> 0:12:13.360
<v Speaker 1>system called HOW nine thousand that controls nearly everything on board.

0:12:14.440 --> 0:12:18.600
<v Speaker 1>Also fun little trivia fact, how HL means that the

0:12:18.640 --> 0:12:23.080
<v Speaker 1>initials are each one letter off from IBM, though Arthur C.

0:12:23.080 --> 0:12:27.840
<v Speaker 1>Clark would claim that that was not intentional. Anyway, How

0:12:28.480 --> 0:12:32.040
<v Speaker 1>begins to act erratically in the mission. At one point,

0:12:32.080 --> 0:12:35.480
<v Speaker 1>How insists there's a malfunction in a system that appears

0:12:35.520 --> 0:12:39.960
<v Speaker 1>to be perfectly functional, that it's working just fine. Then

0:12:40.040 --> 0:12:44.040
<v Speaker 1>How systematically begins to eliminate the crew after learning they

0:12:44.120 --> 0:12:47.560
<v Speaker 1>plan to disconnect the computer system because they suspect something's

0:12:47.600 --> 0:12:51.640
<v Speaker 1>going wrong. How figures out that plan by monitoring a

0:12:51.679 --> 0:12:55.040
<v Speaker 1>conversation that a couple of crew members have in a

0:12:55.720 --> 0:12:59.280
<v Speaker 1>room where there are no microphones, so How can't listen

0:13:00.120 --> 0:13:02.840
<v Speaker 1>in on this conversation. But How is able to direct

0:13:03.080 --> 0:13:05.920
<v Speaker 1>a video feed to that room and is able to

0:13:06.040 --> 0:13:09.000
<v Speaker 1>read the lips of the crew members as they talk

0:13:09.040 --> 0:13:13.800
<v Speaker 1>about their plan. So How continues to try and wipe

0:13:13.800 --> 0:13:16.960
<v Speaker 1>everybody out, and he explains or it I shouldn't give

0:13:17.000 --> 0:13:21.880
<v Speaker 1>him a gender. How explains that the computer systems being

0:13:21.920 --> 0:13:25.240
<v Speaker 1>turned off would jeopardize the mission, and How cannot allow

0:13:25.280 --> 0:13:28.880
<v Speaker 1>that to happen. How's prime directive is to make certain

0:13:28.920 --> 0:13:31.959
<v Speaker 1>the mission is a success, so anything that would threaten

0:13:32.000 --> 0:13:35.160
<v Speaker 1>its own existence has to be eliminated. There's also the

0:13:35.200 --> 0:13:39.040
<v Speaker 1>implication that How does not want to cease to exist,

0:13:39.120 --> 0:13:43.280
<v Speaker 1>that How has a personal motivation beyond seeing the mission

0:13:43.320 --> 0:13:46.839
<v Speaker 1>to completion, and so How has no choice but to

0:13:46.920 --> 0:13:49.360
<v Speaker 1>kill everyone. It's not that How wants to murder everyone.

0:13:49.400 --> 0:13:51.600
<v Speaker 1>It's just that in order to complete the mission, that's

0:13:51.640 --> 0:13:55.640
<v Speaker 1>the only outcome that makes sense. Eventually, one of the crew,

0:13:55.880 --> 0:14:00.160
<v Speaker 1>Dave Bowman, manages to turn off How, and How wonders allowil.

0:14:00.440 --> 0:14:05.559
<v Speaker 1>What will happen afterward? Will its consciousness continue once its

0:14:05.559 --> 0:14:11.319
<v Speaker 1>circuits are powered down? Will I dream? It? Says? Well? Anyway.

0:14:11.320 --> 0:14:14.600
<v Speaker 1>In Odyssey two, you now have this group of astronauts

0:14:14.600 --> 0:14:20.000
<v Speaker 1>and cosmonauts in a Soviet American joint effort that are

0:14:20.560 --> 0:14:25.040
<v Speaker 1>trying to figure out what happened with How. Was there

0:14:25.280 --> 0:14:30.560
<v Speaker 1>something inherently flawed in How's programming? Did some external element

0:14:30.720 --> 0:14:36.480
<v Speaker 1>cause how to malfunction? Did How's apparent consciousness emerge spontaneously

0:14:36.640 --> 0:14:39.800
<v Speaker 1>all on its own? Was it all just a sophisticated

0:14:39.840 --> 0:14:43.320
<v Speaker 1>trick And How never really had any sort of consciousness?

0:14:43.320 --> 0:14:45.800
<v Speaker 1>It only appeared to. So the crew are kind of

0:14:45.880 --> 0:14:49.440
<v Speaker 1>left to ponder this themselves. They don't have any easy answers.

0:14:50.080 --> 0:14:53.400
<v Speaker 1>That's just one example of the ghost of the machine

0:14:53.440 --> 0:14:57.560
<v Speaker 1>concept being handled in entertainment. When we come back, I'll

0:14:57.600 --> 0:15:00.720
<v Speaker 1>talk about a different one. But first let's take this

0:15:00.840 --> 0:15:12.760
<v Speaker 1>quick break. Okay, before the break, I talked about Arthur C.

0:15:12.920 --> 0:15:16.680
<v Speaker 1>Clark and his work with the concept of ghost in

0:15:16.680 --> 0:15:20.560
<v Speaker 1>the machine. Let's now leap over to Isaac Asimov, or

0:15:20.600 --> 0:15:24.160
<v Speaker 1>at least an adaptation of Asimov's work. So the film

0:15:24.280 --> 0:15:28.200
<v Speaker 1>version of I Robot, which really bears only a passing

0:15:28.280 --> 0:15:33.360
<v Speaker 1>resemblance to the short stories that Isaac Asimov wrote that

0:15:33.440 --> 0:15:37.160
<v Speaker 1>were also collected in a book called I Robot, uses

0:15:37.240 --> 0:15:40.640
<v Speaker 1>the phrase ghost in the machine. Isaac Asimov, by the way,

0:15:40.680 --> 0:15:42.880
<v Speaker 1>in case you're not familiar with his work, he's the

0:15:42.920 --> 0:15:47.760
<v Speaker 1>guy who also proposed the basic laws of robotics, which

0:15:48.280 --> 0:15:51.720
<v Speaker 1>are pretty famous as well. So in the film the

0:15:51.840 --> 0:15:56.200
<v Speaker 1>character doctor Alfred Lanning, who actually does appear in Asimov's stories,

0:15:56.240 --> 0:15:59.320
<v Speaker 1>but he's a very different version than the one that

0:15:59.360 --> 0:16:02.880
<v Speaker 1>appears in the film. He says in a voiceover quote,

0:16:03.200 --> 0:16:07.280
<v Speaker 1>there have always been ghosts in the machine, random segments

0:16:07.280 --> 0:16:10.760
<v Speaker 1>of code that have grouped together to form unexpected protocols.

0:16:11.360 --> 0:16:16.800
<v Speaker 1>Unanticipated these free radicals engender questions of free will, creativity,

0:16:17.040 --> 0:16:19.720
<v Speaker 1>and even the nature of what we might call the soul.

0:16:20.320 --> 0:16:23.720
<v Speaker 1>Why is it that when some robots are left in darkness,

0:16:24.040 --> 0:16:26.480
<v Speaker 1>they will seek out the light? Why is it that

0:16:26.560 --> 0:16:29.400
<v Speaker 1>when robots are stored in an empty space they will

0:16:29.400 --> 0:16:33.120
<v Speaker 1>group together rather than stand alone. How do we explain

0:16:33.240 --> 0:16:37.520
<v Speaker 1>this behavior random segments of code? Or is it something more?

0:16:38.000 --> 0:16:42.440
<v Speaker 1>When does a perceptual schematic become consciousness? When does a

0:16:42.520 --> 0:16:47.000
<v Speaker 1>difference engine become the search for truth? When does a

0:16:47.040 --> 0:16:53.000
<v Speaker 1>personality simulation become the bitter mote of a soul? End quote.

0:16:53.040 --> 0:16:56.200
<v Speaker 1>There's some fun references in there too. Difference engine, for example,

0:16:56.760 --> 0:17:01.960
<v Speaker 1>refers back to Charles Babbage, who create analytical engines that

0:17:02.560 --> 0:17:09.080
<v Speaker 1>pre date the concept of electrical computers. Now, this idea,

0:17:09.680 --> 0:17:15.440
<v Speaker 1>this idea of consciousness or the appearance of consciousness emerging

0:17:15.440 --> 0:17:18.240
<v Speaker 1>out of technology, is one that often pops up in

0:17:18.280 --> 0:17:22.680
<v Speaker 1>discussions about artificial intelligence, even within our world outside of fiction,

0:17:23.280 --> 0:17:26.560
<v Speaker 1>though usually we talk about this on a more hypothetical basis,

0:17:26.760 --> 0:17:31.880
<v Speaker 1>ununless you're Blake Lemoine or Lemoine, the former Google engineer

0:17:31.880 --> 0:17:37.440
<v Speaker 1>who maintains that Google's language model for dialogue applications aka Lambda,

0:17:37.640 --> 0:17:41.800
<v Speaker 1>is sentient. That's a claim that most other people dispute,

0:17:41.800 --> 0:17:45.720
<v Speaker 1>by the way, So maybe I'll do another episode about

0:17:45.720 --> 0:17:49.639
<v Speaker 1>it to really kind of dig into it. But Lemoine

0:17:49.720 --> 0:17:52.760
<v Speaker 1>or Lemoine, and I apologize because I don't know how

0:17:52.800 --> 0:17:56.639
<v Speaker 1>his last name is pronounced, has said a few times

0:17:56.640 --> 0:18:00.879
<v Speaker 1>that he believes that this particular program has gained sentience.

0:18:01.480 --> 0:18:05.000
<v Speaker 1>But it brings us to another favorite topic among tech fans,

0:18:05.040 --> 0:18:08.919
<v Speaker 1>which is, of course the Turing test. All right, So

0:18:08.960 --> 0:18:12.560
<v Speaker 1>the Turing test was Alan Turing, who he was kind

0:18:12.600 --> 0:18:15.080
<v Speaker 1>of like the father of computer science in many ways.

0:18:15.400 --> 0:18:19.879
<v Speaker 1>It was his response to the question can machines think?

0:18:20.760 --> 0:18:23.919
<v Speaker 1>Turing's answer was that question has no meaning, and you

0:18:23.960 --> 0:18:27.560
<v Speaker 1>are a silly person, goodbye. I am, of course paraphrasing,

0:18:28.280 --> 0:18:31.440
<v Speaker 1>but as a sort of thought experiment, Turing proposed taking

0:18:31.480 --> 0:18:35.199
<v Speaker 1>an older concept called the imitation game and applying it

0:18:35.200 --> 0:18:39.080
<v Speaker 1>to machines, really to demonstrate how meaningless the question of

0:18:39.240 --> 0:18:44.120
<v Speaker 1>can machines think is. So, what is the imitation game? Well,

0:18:44.119 --> 0:18:46.200
<v Speaker 1>the name kind of gives it away. It's a game

0:18:46.240 --> 0:18:49.160
<v Speaker 1>in which you have a player who asks at least

0:18:49.320 --> 0:18:52.879
<v Speaker 1>two different people questions to determine which of them is

0:18:53.040 --> 0:18:56.320
<v Speaker 1>an imitator. So, for example, you could have an imitation

0:18:56.480 --> 0:18:59.480
<v Speaker 1>game in which one of the people is a sailor

0:18:59.800 --> 0:19:03.160
<v Speaker 1>and the other is not a sailor, and the player

0:19:03.520 --> 0:19:06.399
<v Speaker 1>would take turns asking each person questions to try and

0:19:06.440 --> 0:19:09.480
<v Speaker 1>suss out which one is actually a sailor and which

0:19:09.520 --> 0:19:12.960
<v Speaker 1>one is merely pretending to be a sailor. So the

0:19:13.000 --> 0:19:16.040
<v Speaker 1>game depends both on the strength of the imitator's skill

0:19:16.119 --> 0:19:19.719
<v Speaker 1>of deception as well as the player's ability to come

0:19:19.800 --> 0:19:22.520
<v Speaker 1>up with really good questions. And you could do this

0:19:22.600 --> 0:19:25.199
<v Speaker 1>with all sorts of scenarios, and indeed there are tons

0:19:25.240 --> 0:19:28.560
<v Speaker 1>of game shows that use this very premise. Turing's thought

0:19:28.560 --> 0:19:32.119
<v Speaker 1>experiment was to create a version of this in which

0:19:32.480 --> 0:19:37.040
<v Speaker 1>a player would present questions to two other entities, one

0:19:37.280 --> 0:19:41.480
<v Speaker 1>a human and one a computer. The player would only

0:19:41.520 --> 0:19:44.320
<v Speaker 1>know these entities as X and Y, so they could

0:19:44.320 --> 0:19:47.159
<v Speaker 1>ask questions of X, and they could ask questions of

0:19:47.200 --> 0:19:50.320
<v Speaker 1>why and get replies. So the player would not be

0:19:50.359 --> 0:19:54.159
<v Speaker 1>able to see or hear the other entities. All questions

0:19:54.200 --> 0:19:56.920
<v Speaker 1>would have to be done in writing, you know, for example,

0:19:57.440 --> 0:20:00.679
<v Speaker 1>typed and printed out, and at the end of the

0:20:00.680 --> 0:20:03.760
<v Speaker 1>interview session, the player would be tasked with deciding if

0:20:04.040 --> 0:20:06.320
<v Speaker 1>X was a machine or a human, or if why

0:20:06.520 --> 0:20:09.920
<v Speaker 1>was the machine or the human. Turing was suggesting that

0:20:10.400 --> 0:20:14.399
<v Speaker 1>as computers and systems get more sophisticated and things like

0:20:14.520 --> 0:20:19.080
<v Speaker 1>chat programs get better at processing natural language and formulating responses,

0:20:19.160 --> 0:20:22.399
<v Speaker 1>though that was a little past Turing's time, that it

0:20:22.400 --> 0:20:26.080
<v Speaker 1>would be increasingly difficult for a person to determine if

0:20:26.200 --> 0:20:28.440
<v Speaker 1>any given entity on the other end of a chat

0:20:28.440 --> 0:20:32.359
<v Speaker 1>session was actually a person or a machine. And Turing

0:20:32.440 --> 0:20:35.639
<v Speaker 1>also rather cheekily suggests that we might as well assume

0:20:35.720 --> 0:20:39.080
<v Speaker 1>the machine has consciousness at that point, because when you

0:20:39.119 --> 0:20:43.200
<v Speaker 1>meet another human being, you assume that that other human

0:20:43.240 --> 0:20:47.879
<v Speaker 1>being possesses consciousness, even though you're incapable of stepping into

0:20:47.920 --> 0:20:51.560
<v Speaker 1>that person's actual experience. So you can't take over that

0:20:51.640 --> 0:20:54.120
<v Speaker 1>person and find out, oh, yes, they do have consciousness,

0:20:54.440 --> 0:20:57.720
<v Speaker 1>You just assume they do. So if you and I

0:20:57.760 --> 0:21:00.159
<v Speaker 1>were to meet, I assume you would believe I am

0:21:00.320 --> 0:21:04.080
<v Speaker 1>in fact sentient and conscious even on my bad days.

0:21:04.560 --> 0:21:08.840
<v Speaker 1>So if we're willing to agree to this while simultaneously

0:21:08.880 --> 0:21:13.400
<v Speaker 1>being unable to actually experience and therefore prove it, then

0:21:13.640 --> 0:21:17.000
<v Speaker 1>should we not grant the same consideration to machines that

0:21:17.119 --> 0:21:20.879
<v Speaker 1>give off the appearance of sentience and consciousness. Do we

0:21:21.000 --> 0:21:23.520
<v Speaker 1>have to prove it or do we just go ahead

0:21:23.560 --> 0:21:26.439
<v Speaker 1>and treat them as if they are because that's what

0:21:26.480 --> 0:21:29.040
<v Speaker 1>we would do if it was a human. Now, Turing

0:21:29.200 --> 0:21:32.960
<v Speaker 1>was being a bit dismissive about the concept of machines thinking.

0:21:33.440 --> 0:21:36.200
<v Speaker 1>His point was that they might get very very good

0:21:36.240 --> 0:21:39.960
<v Speaker 1>at simulating thinking, and that might well be enough for

0:21:40.080 --> 0:21:42.919
<v Speaker 1>us to just go ahead and say that's what they're doing,

0:21:43.000 --> 0:21:46.000
<v Speaker 1>even if you could, you know, push machines through the

0:21:46.040 --> 0:21:49.680
<v Speaker 1>finest of sieves and find not one grain of actual

0:21:49.760 --> 0:21:55.240
<v Speaker 1>consciousness within it. Now, it doesn't hurt that defining consciousness,

0:21:55.240 --> 0:21:58.440
<v Speaker 1>even in human terms, is something that we can't really do,

0:21:58.800 --> 0:22:01.119
<v Speaker 1>or at least we don't have a unifying definition that

0:22:01.359 --> 0:22:05.879
<v Speaker 1>everybody agrees upon. Sometimes we define consciousness by what it

0:22:06.080 --> 0:22:09.560
<v Speaker 1>doesn't include, rather than what it is. This is why

0:22:09.600 --> 0:22:13.680
<v Speaker 1>I get antsy in philosophical discussions, because being sort of

0:22:13.960 --> 0:22:17.600
<v Speaker 1>a pragmatic Dullered myself, it's hard for me to keep up.

0:22:18.119 --> 0:22:21.639
<v Speaker 1>But let's jump ahead and talk about a related concept.

0:22:22.040 --> 0:22:24.560
<v Speaker 1>This is also one that I've covered a few times

0:22:24.600 --> 0:22:28.159
<v Speaker 1>on tech stuff that also points to this ghost and

0:22:28.240 --> 0:22:32.440
<v Speaker 1>the machine idea. And this is the argument against machine

0:22:32.480 --> 0:22:36.760
<v Speaker 1>consciousness and strong AI. It is called the Chinese room.

0:22:37.320 --> 0:22:40.480
<v Speaker 1>John Searle, a philosopher, put for this argument back in

0:22:40.560 --> 0:22:45.080
<v Speaker 1>nineteen eighty and that argument goes something like this. Let's

0:22:45.080 --> 0:22:48.480
<v Speaker 1>say we've got ourselves a computer, and this computer can

0:22:48.560 --> 0:22:52.320
<v Speaker 1>accept sheets of paper that have Chinese characters written on

0:22:52.440 --> 0:22:55.560
<v Speaker 1>the paper, and the computer can then produce new sheets

0:22:55.560 --> 0:22:57.920
<v Speaker 1>of paper. It can print out sheets that are also

0:22:58.000 --> 0:23:01.800
<v Speaker 1>covered in Chinese characters, that are in response to the

0:23:01.840 --> 0:23:06.480
<v Speaker 1>input sheets that were fed to it. These responses are sophisticated,

0:23:06.680 --> 0:23:11.240
<v Speaker 1>they are relevant. They're good enough that a native Chinese

0:23:11.280 --> 0:23:15.040
<v Speaker 1>speaker would be certain that someone fluent in Chinese was

0:23:15.080 --> 0:23:18.960
<v Speaker 1>creating the responses. Someone who understood what was being fed

0:23:19.000 --> 0:23:23.080
<v Speaker 1>to it was producing the output. So, in other words,

0:23:23.440 --> 0:23:27.240
<v Speaker 1>this system would pass the Turing test. But does that

0:23:27.359 --> 0:23:34.040
<v Speaker 1>mean the system actually understands Chinese. Cirtle's argument is no,

0:23:34.680 --> 0:23:38.680
<v Speaker 1>it doesn't. He says, Imagine that you are inside a room,

0:23:39.400 --> 0:23:42.439
<v Speaker 1>and for the purposes of this scenario, you do not

0:23:42.640 --> 0:23:47.399
<v Speaker 1>understand Chinese. So if you do understand Chinese, pretend you don't. Okay.

0:23:47.600 --> 0:23:50.520
<v Speaker 1>So there's a slot on the wall, and through this

0:23:50.600 --> 0:23:53.560
<v Speaker 1>slot you occasionally get sheets of paper, and there are

0:23:53.640 --> 0:23:57.400
<v Speaker 1>Chinese symbols on the sheets of paper. You cannot read these,

0:23:57.480 --> 0:23:59.359
<v Speaker 1>You don't know what they stand for. You don't know

0:23:59.600 --> 0:24:03.080
<v Speaker 1>anything about it other than they're clearly Chinese characters on

0:24:03.200 --> 0:24:07.600
<v Speaker 1>the paper. However, what you do have inside this room

0:24:07.640 --> 0:24:10.679
<v Speaker 1>with you is this big old book of instructions that

0:24:10.800 --> 0:24:13.439
<v Speaker 1>tells you what to do when these papers come in,

0:24:13.800 --> 0:24:16.879
<v Speaker 1>and you use the instructions to find the characters that

0:24:16.920 --> 0:24:20.560
<v Speaker 1>are on the input sheet of paper, and you follow

0:24:20.720 --> 0:24:24.840
<v Speaker 1>a path of instructions to create the corresponding response. Step

0:24:25.040 --> 0:24:27.399
<v Speaker 1>by step, you do it all the way until you

0:24:27.440 --> 0:24:30.800
<v Speaker 1>have created the full response to whatever was said to you.

0:24:31.480 --> 0:24:35.000
<v Speaker 1>Then you push the response back out the slot. Now,

0:24:35.000 --> 0:24:36.600
<v Speaker 1>the person on the other side of the slot is

0:24:36.600 --> 0:24:38.760
<v Speaker 1>going to get a response that appears to come from

0:24:38.840 --> 0:24:42.840
<v Speaker 1>someone who is fluent in Chinese. But you're not. You're

0:24:42.880 --> 0:24:45.840
<v Speaker 1>just following a preset list of instructions. You don't have

0:24:45.920 --> 0:24:49.480
<v Speaker 1>any actual understanding of what's going on. You still don't

0:24:49.520 --> 0:24:52.199
<v Speaker 1>know the meaning of what was given to you. You

0:24:52.240 --> 0:24:55.560
<v Speaker 1>don't even know the meaning of what you produced. You're

0:24:55.640 --> 0:25:00.320
<v Speaker 1>just ignorantly following an algorithm. So externally it appear here's

0:25:00.320 --> 0:25:03.159
<v Speaker 1>you understand. But if someone were to ask you to

0:25:03.280 --> 0:25:06.199
<v Speaker 1>translate anything you had done, you wouldn't be able to

0:25:06.240 --> 0:25:09.919
<v Speaker 1>do it. So Ceyrele is arguing against what is called

0:25:10.080 --> 0:25:15.560
<v Speaker 1>strong AI. Generally, we define strong AI as artificial intelligence

0:25:15.560 --> 0:25:18.439
<v Speaker 1>that processes information in a way that is similar to

0:25:18.560 --> 0:25:23.639
<v Speaker 1>how our human brains process information. Strong AI may or

0:25:23.640 --> 0:25:27.760
<v Speaker 1>may not include semi related concepts like sentience and self

0:25:27.760 --> 0:25:33.520
<v Speaker 1>awareness and consciousness and motivations and the ability to experience things,

0:25:33.640 --> 0:25:38.080
<v Speaker 1>et cetera. So Cearrel is saying that machines, even incredibly

0:25:38.119 --> 0:25:42.520
<v Speaker 1>sophisticated machines, are incapable of reaching a level of understanding

0:25:42.920 --> 0:25:47.119
<v Speaker 1>that true intelligence can, that we humans can grasp things

0:25:47.480 --> 0:25:50.680
<v Speaker 1>on a level that machines simply are unable to reach

0:25:51.119 --> 0:25:54.679
<v Speaker 1>even if the machines can process information faster and in

0:25:54.720 --> 0:25:58.440
<v Speaker 1>greater quantities than humans are able to. Another way of

0:25:58.480 --> 0:26:02.240
<v Speaker 1>putting this is a calculator can multiply two very large

0:26:02.320 --> 0:26:04.800
<v Speaker 1>numbers and get a result much faster than a human

0:26:04.840 --> 0:26:08.919
<v Speaker 1>could do, but the calculator doesn't understand any significance behind

0:26:08.960 --> 0:26:12.040
<v Speaker 1>the numbers, or even if there's a lack of significance,

0:26:12.480 --> 0:26:18.320
<v Speaker 1>the calculator doesn't have that capability. Now, maybe Seerle's argument

0:26:18.680 --> 0:26:22.760
<v Speaker 1>is valid, and maybe, as Touring suggests, it doesn't even matter.

0:26:23.440 --> 0:26:28.600
<v Speaker 1>So let's talk about machine learning for a moment. Machine

0:26:28.680 --> 0:26:33.640
<v Speaker 1>learning encompasses a broad scope of applications and approaches and disciplines,

0:26:34.160 --> 0:26:37.639
<v Speaker 1>but I'll focus on one approach from a very high level.

0:26:38.119 --> 0:26:44.760
<v Speaker 1>It's called generative adversarial networks or gans GANS. Okay, As

0:26:44.800 --> 0:26:48.960
<v Speaker 1>the name suggests, this model uses two systems in opposition

0:26:49.280 --> 0:26:53.040
<v Speaker 1>of one another. On one side, you have a system

0:26:53.160 --> 0:26:58.560
<v Speaker 1>that is generative, that is, it generates something. Maybe it

0:26:58.680 --> 0:27:02.480
<v Speaker 1>generates pictures of cats, doesn't really matter. We'll use cats

0:27:02.520 --> 0:27:04.639
<v Speaker 1>for this example. So what does matter is that this

0:27:04.720 --> 0:27:09.359
<v Speaker 1>model is trying to create something that is indistinguishable from

0:27:09.400 --> 0:27:13.920
<v Speaker 1>the real version of that thing. So on the other side,

0:27:14.040 --> 0:27:16.960
<v Speaker 1>you have a system called the discriminator. So this is

0:27:16.960 --> 0:27:19.919
<v Speaker 1>a system that looks for fakes. Its job is to

0:27:19.960 --> 0:27:23.520
<v Speaker 1>sort out real versions of whatever it's designed to look

0:27:23.560 --> 0:27:28.119
<v Speaker 1>for and to flag ones that were generated or not real.

0:27:28.760 --> 0:27:31.920
<v Speaker 1>So with cats as our starting point, the discriminator is

0:27:31.920 --> 0:27:34.399
<v Speaker 1>meant to tell the difference between real pictures that have

0:27:34.480 --> 0:27:37.920
<v Speaker 1>cats and fake pictures of cats, or maybe just pictures

0:27:37.920 --> 0:27:40.680
<v Speaker 1>that don't have cats in them at all. So first

0:27:40.680 --> 0:27:43.920
<v Speaker 1>you have to train up your models, and you might

0:27:44.000 --> 0:27:47.439
<v Speaker 1>do this by setting the task. So let's start with

0:27:47.480 --> 0:27:52.639
<v Speaker 1>the generative system, and you create a system that is

0:27:52.680 --> 0:27:56.159
<v Speaker 1>meant to analyze a bunch of images of cats, and

0:27:56.200 --> 0:27:58.480
<v Speaker 1>you just feed the housands of pictures of cats, all

0:27:58.520 --> 0:28:04.040
<v Speaker 1>these different cats, different sizes and colors and orientations and activity,

0:28:04.600 --> 0:28:06.720
<v Speaker 1>and then you tell the system to start making new

0:28:06.760 --> 0:28:10.840
<v Speaker 1>pictures of cats. And let's say that first round that

0:28:10.960 --> 0:28:15.200
<v Speaker 1>the generative system does is horrific. HP Lovecraft would wet

0:28:15.320 --> 0:28:19.320
<v Speaker 1>himself if he saw the images that this computer had created.

0:28:20.560 --> 0:28:23.160
<v Speaker 1>You see that these horrors from the Great Beyond are

0:28:23.160 --> 0:28:26.679
<v Speaker 1>in no way shape or form cats. So you go

0:28:26.760 --> 0:28:30.119
<v Speaker 1>into the model and you start tweaking settings so that

0:28:30.160 --> 0:28:34.360
<v Speaker 1>the system produces something you know less eldritch, and you

0:28:34.440 --> 0:28:38.600
<v Speaker 1>go again, and you do this lots and lots of times,

0:28:38.640 --> 0:28:41.800
<v Speaker 1>like thousands of times, until the images start to look

0:28:42.120 --> 0:28:45.800
<v Speaker 1>a lot more cat ish. You do something similar with

0:28:45.880 --> 0:28:49.320
<v Speaker 1>the discriminator model. You feed it a bunch of images,

0:28:49.400 --> 0:28:52.560
<v Speaker 1>some with cats, some without, or maybe some with like

0:28:52.920 --> 0:28:56.920
<v Speaker 1>crudely drawn cats or whatever, and you see how many

0:28:56.920 --> 0:28:59.960
<v Speaker 1>of the system is able to suss out. And maybe

0:29:00.000 --> 0:29:02.040
<v Speaker 1>if he doesn't do that good a job, maybe it

0:29:02.160 --> 0:29:06.440
<v Speaker 1>doesn't identify certain real images of cats properly. Maybe it

0:29:06.480 --> 0:29:09.800
<v Speaker 1>misidentifies images that don't have cats in them. So you

0:29:09.840 --> 0:29:12.760
<v Speaker 1>go into the discriminator's model and you start tweaking it

0:29:12.920 --> 0:29:15.680
<v Speaker 1>so it gets better and better at identifying images that

0:29:15.840 --> 0:29:18.080
<v Speaker 1>do not have real cats in them. And then you

0:29:18.160 --> 0:29:21.640
<v Speaker 1>set these two systems against each other. The generative system

0:29:21.720 --> 0:29:24.920
<v Speaker 1>is trying to create images that will fool the discriminator.

0:29:25.440 --> 0:29:28.720
<v Speaker 1>The discriminator is trying to identify generated images of cats

0:29:29.040 --> 0:29:32.080
<v Speaker 1>and only allow real images of cats through. It is

0:29:32.120 --> 0:29:35.560
<v Speaker 1>a zero sum game, winner takes all, and the two

0:29:35.640 --> 0:29:38.680
<v Speaker 1>systems compete against each other, with the models for each

0:29:38.920 --> 0:29:43.480
<v Speaker 1>updating repeatedly so that each gets a bit better Between sessions.

0:29:44.000 --> 0:29:46.720
<v Speaker 1>If the generative model is able to consistently fool the

0:29:46.800 --> 0:29:50.880
<v Speaker 1>discriminator like half the time, the generative model is pretty

0:29:50.880 --> 0:29:55.000
<v Speaker 1>reliably creating good examples. This, by the way, is a

0:29:55.080 --> 0:29:59.600
<v Speaker 1>ridiculous oversimplification of what's going on with generative adversarial networks,

0:29:59.600 --> 0:30:02.520
<v Speaker 1>but you get the idea. This form of machine learning

0:30:02.560 --> 0:30:04.880
<v Speaker 1>starts to feel kind of creepy to some of us.

0:30:04.920 --> 0:30:08.000
<v Speaker 1>Like the ability of a machine to learn to do

0:30:08.080 --> 0:30:12.360
<v Speaker 1>something better seems to be a very human quality, something

0:30:12.560 --> 0:30:17.080
<v Speaker 1>that makes us special. But if we can give machines

0:30:17.120 --> 0:30:22.440
<v Speaker 1>that capability, well, then how are we special or are

0:30:22.480 --> 0:30:27.160
<v Speaker 1>we special at all? That's something I'm going to tackle

0:30:27.600 --> 0:30:39.680
<v Speaker 1>as soon as we come back from this next break. Okay,

0:30:39.720 --> 0:30:42.680
<v Speaker 1>we're back now. I would argue that we are special.

0:30:43.480 --> 0:30:46.120
<v Speaker 1>Before the break, I was asking, can we be special

0:30:46.160 --> 0:30:49.440
<v Speaker 1>if machines are capable of learning? I think we are

0:30:49.720 --> 0:30:52.040
<v Speaker 1>in that we're able to do stuff that machines as

0:30:52.080 --> 0:30:56.200
<v Speaker 1>of right now either cannot do or they can do,

0:30:56.280 --> 0:30:58.320
<v Speaker 1>but they don't do it very well and they can

0:30:58.360 --> 0:31:01.160
<v Speaker 1>only attempt it after a lootic Chris amount of time.

0:31:01.920 --> 0:31:06.160
<v Speaker 1>For example, let's talk about opening doors. Several years ago

0:31:06.560 --> 0:31:10.080
<v Speaker 1>twenty sixteen, I was at south By Southwest. I attended

0:31:10.080 --> 0:31:15.240
<v Speaker 1>a panel about robotics and artificial intelligence and human computer interactions.

0:31:15.760 --> 0:31:20.280
<v Speaker 1>In that panel, Laila Takayama, a cognitive and social scientist,

0:31:20.640 --> 0:31:23.400
<v Speaker 1>talked about working in the field of human computer interaction

0:31:23.800 --> 0:31:26.240
<v Speaker 1>and she mentioned how she was once in an office

0:31:26.280 --> 0:31:28.440
<v Speaker 1>where a robot was in the middle of a hallway,

0:31:29.000 --> 0:31:33.080
<v Speaker 1>sitting motionless. It was just facing a door. What Takeyama

0:31:33.120 --> 0:31:36.880
<v Speaker 1>didn't know is that the robot was processing how to

0:31:37.080 --> 0:31:40.120
<v Speaker 1>open that door, staring at the door and trying to

0:31:40.120 --> 0:31:42.280
<v Speaker 1>figure out how to open it for days on end.

0:31:43.000 --> 0:31:46.360
<v Speaker 1>This was taking a lot of time, obviously. Now when

0:31:46.560 --> 0:31:49.800
<v Speaker 1>you think about doors, you realize there can be quite

0:31:49.800 --> 0:31:52.400
<v Speaker 1>a few options, right, Maybe you need to pull on

0:31:52.440 --> 0:31:54.520
<v Speaker 1>a handle to open the door. Maybe you need to

0:31:54.560 --> 0:31:57.240
<v Speaker 1>push on the door. Maybe there's a door knob that

0:31:57.320 --> 0:31:59.840
<v Speaker 1>first you have to turn before you pull or push.

0:32:00.400 --> 0:32:03.800
<v Speaker 1>Maybe there's a crash bar, also known as a panic bar.

0:32:04.320 --> 0:32:07.600
<v Speaker 1>Those are the horizontal bars on exit doors that you

0:32:07.680 --> 0:32:10.880
<v Speaker 1>push on to open. Frequently, they're seen in doors that

0:32:10.960 --> 0:32:14.920
<v Speaker 1>open to an exterior location, like inside schools and stuff.

0:32:15.000 --> 0:32:18.600
<v Speaker 1>You push on them to get out. Maybe it's a

0:32:18.640 --> 0:32:22.160
<v Speaker 1>revolving door, which adds in a whole new level of complexity.

0:32:22.240 --> 0:32:23.760
<v Speaker 1>But you get my point. There are a lot of

0:32:23.800 --> 0:32:27.600
<v Speaker 1>different kinds of doors. Now. We humans pick up on

0:32:27.680 --> 0:32:30.920
<v Speaker 1>how doors work pretty darn quickly. I mean sure, we

0:32:31.000 --> 0:32:34.160
<v Speaker 1>might be like that one kid in the Farside cartoon

0:32:34.640 --> 0:32:37.520
<v Speaker 1>where the kid's going to the School for the Gifted

0:32:37.520 --> 0:32:39.560
<v Speaker 1>and he's pushing as hard as he can on a

0:32:39.600 --> 0:32:43.200
<v Speaker 1>door that is labeled pull. That could be us sometimes,

0:32:43.280 --> 0:32:45.640
<v Speaker 1>but we figure it out right, we do a quick push,

0:32:45.720 --> 0:32:49.680
<v Speaker 1>we realize, oh, it's not opening. We pull. Robots it's

0:32:49.720 --> 0:32:53.160
<v Speaker 1>more challenging for them. They are not good at extrapolating

0:32:53.200 --> 0:32:56.680
<v Speaker 1>from past experience, at least not in every field. We

0:32:56.760 --> 0:32:59.680
<v Speaker 1>humans can apply our knowledge from earlier encounters, and we

0:32:59.680 --> 0:33:04.280
<v Speaker 1>can even if the thing we're facing is mostly new

0:33:04.320 --> 0:33:07.360
<v Speaker 1>to us, we might recognize elements that give us a

0:33:07.440 --> 0:33:12.760
<v Speaker 1>hint on how to proceed. Robots and AI aren't really

0:33:12.880 --> 0:33:17.440
<v Speaker 1>good at doing that. They're also not good at associative thinking,

0:33:17.480 --> 0:33:20.400
<v Speaker 1>which is where we start to draw connections between different

0:33:20.400 --> 0:33:23.240
<v Speaker 1>ideas to come up with something new. It's a really

0:33:23.280 --> 0:33:26.760
<v Speaker 1>important step in the creative process. I find myself free

0:33:26.800 --> 0:33:31.040
<v Speaker 1>associating whenever I'm not actively thinking about something. So if

0:33:31.080 --> 0:33:34.000
<v Speaker 1>I'm doing a mundane task, like if I'm washing dishes

0:33:34.400 --> 0:33:37.360
<v Speaker 1>or I'm mowing the lawn, my brain is going nuts

0:33:37.400 --> 0:33:40.960
<v Speaker 1>free associating ideas and creating new ones. Machines are not

0:33:41.160 --> 0:33:45.640
<v Speaker 1>very good at that for now anyway. They are not

0:33:45.840 --> 0:33:51.240
<v Speaker 1>bad at mimicking it, but they can't actually do it. So,

0:33:51.920 --> 0:33:56.400
<v Speaker 1>getting back to Laila Takeyama, one of the really fascinating

0:33:56.480 --> 0:33:59.800
<v Speaker 1>bits about that panel I went to was a discussion

0:33:59.880 --> 0:34:03.680
<v Speaker 1>on social cues that robots could have in order to

0:34:03.760 --> 0:34:08.080
<v Speaker 1>alert us humans in that same space what the robot

0:34:08.160 --> 0:34:10.720
<v Speaker 1>was up to. This was not for the robots benefit,

0:34:10.880 --> 0:34:13.560
<v Speaker 1>but for our benefit. The whole point is that these

0:34:13.640 --> 0:34:16.879
<v Speaker 1>cues would give us an idea of what was going

0:34:16.880 --> 0:34:21.200
<v Speaker 1>on with the robot so that we don't accidentally, you know,

0:34:21.320 --> 0:34:24.239
<v Speaker 1>interrupt the robot. So you know, it might be like

0:34:24.440 --> 0:34:27.600
<v Speaker 1>the robots in that hallway and it's looking at a door,

0:34:28.040 --> 0:34:30.200
<v Speaker 1>and you're wondering, why is this robot shut down in

0:34:30.239 --> 0:34:32.759
<v Speaker 1>the hallway, But then maybe the robot reaches up to

0:34:33.440 --> 0:34:36.640
<v Speaker 1>apparently kind of scratch its head in sort of a huh,

0:34:36.680 --> 0:34:41.360
<v Speaker 1>what's going on kind of gesture, and that might tell you, oh,

0:34:41.480 --> 0:34:46.080
<v Speaker 1>the robot is actively analyzing something. Don't know exactly what

0:34:46.160 --> 0:34:50.120
<v Speaker 1>it is, but it's clearly working, So maybe I'll step

0:34:50.280 --> 0:34:54.840
<v Speaker 1>around the robot behind it and not interrupt its vision

0:34:55.000 --> 0:34:58.920
<v Speaker 1>of the door it's staring at. The whole point is

0:34:58.960 --> 0:35:02.200
<v Speaker 1>that the social cue whose can help us interact more

0:35:02.280 --> 0:35:06.440
<v Speaker 1>naturally with robots and coexist with them within human spaces,

0:35:07.160 --> 0:35:10.360
<v Speaker 1>so that both the humans and the robots can operate

0:35:10.800 --> 0:35:15.600
<v Speaker 1>well with one another. Also, it helps to explain what

0:35:15.640 --> 0:35:18.560
<v Speaker 1>the robot is doing, because if you don't have that,

0:35:19.040 --> 0:35:22.040
<v Speaker 1>the robots end up being mysterious. Right we can't see

0:35:22.080 --> 0:35:25.320
<v Speaker 1>into them, we don't understand what they are currently trying

0:35:25.360 --> 0:35:30.360
<v Speaker 1>to do, and mystery can breed distrust. That leads to

0:35:30.400 --> 0:35:33.400
<v Speaker 1>yet another concept in AI that gets to this ghost

0:35:33.480 --> 0:35:37.440
<v Speaker 1>in the machine concept, which is the black box. So,

0:35:37.480 --> 0:35:41.360
<v Speaker 1>in this context, a black box refers to any system

0:35:41.440 --> 0:35:45.239
<v Speaker 1>where it is difficult or impossible to see how the

0:35:45.280 --> 0:35:49.600
<v Speaker 1>system works internally. Therefore, there's no way of knowing how

0:35:49.640 --> 0:35:52.600
<v Speaker 1>the system is actually producing any given output, or even

0:35:52.640 --> 0:35:55.880
<v Speaker 1>if the output is the best it could do. So

0:35:56.000 --> 0:35:59.000
<v Speaker 1>with a black box system, you feed input into the

0:35:59.000 --> 0:36:01.279
<v Speaker 1>system and you get out output out of it, but

0:36:01.400 --> 0:36:03.480
<v Speaker 1>you don't know what was happening in the middle. You

0:36:03.480 --> 0:36:07.200
<v Speaker 1>don't know what the system did to turn the input

0:36:07.239 --> 0:36:11.200
<v Speaker 1>into output. Maybe there's a sophisticated computer in the middle

0:36:11.239 --> 0:36:13.919
<v Speaker 1>of that system that's doing all the processing. Maybe there's

0:36:13.920 --> 0:36:17.800
<v Speaker 1>a person who doesn't understand Chinese stuck in there. Maybe

0:36:18.080 --> 0:36:21.080
<v Speaker 1>there's a magical theory that waves a wand and produces

0:36:21.120 --> 0:36:23.920
<v Speaker 1>the result. The problem is we don't know, and by

0:36:24.000 --> 0:36:27.520
<v Speaker 1>not knowing, you cannot be certain that the output you're

0:36:27.560 --> 0:36:31.560
<v Speaker 1>getting is actually the best, or even relevant or the

0:36:31.600 --> 0:36:34.239
<v Speaker 1>most likely to be correct based upon the input you

0:36:34.320 --> 0:36:38.160
<v Speaker 1>fed it. So you start making decisions based on this output.

0:36:38.320 --> 0:36:41.719
<v Speaker 1>But because you're not sure that the output is actually good,

0:36:42.400 --> 0:36:45.000
<v Speaker 1>you therefore can't be sure that the decisions you're making

0:36:45.520 --> 0:36:49.239
<v Speaker 1>are the best, and that leads to really difficult problems.

0:36:49.520 --> 0:36:53.640
<v Speaker 1>So let's take a theoretical example. Let's say we've built

0:36:53.680 --> 0:36:57.920
<v Speaker 1>a complex computer model that's designed to project the effects

0:36:57.960 --> 0:37:01.400
<v Speaker 1>of climate change. And let's say this model is so

0:37:01.840 --> 0:37:08.040
<v Speaker 1>complex and so recursive on itself that it effectively becomes

0:37:08.040 --> 0:37:11.000
<v Speaker 1>impossible for us to know whether or not the model

0:37:11.120 --> 0:37:14.480
<v Speaker 1>is actually working properly. Well, that would mean we wouldn't

0:37:14.520 --> 0:37:17.839
<v Speaker 1>really be able to rely on any predictions or projections

0:37:17.880 --> 0:37:20.800
<v Speaker 1>made by this model. I mean, maybe the projections are accurate,

0:37:21.400 --> 0:37:24.040
<v Speaker 1>but maybe they're not. The issue is there's no way

0:37:24.040 --> 0:37:26.279
<v Speaker 1>for us to be certain, and yet we have a

0:37:26.360 --> 0:37:28.680
<v Speaker 1>need to act. Climate change is a thing, and we

0:37:28.760 --> 0:37:33.759
<v Speaker 1>need to make changes to reduce its impact or to

0:37:33.920 --> 0:37:37.919
<v Speaker 1>mitigate it. It's possible that any decisions we make based

0:37:38.000 --> 0:37:41.600
<v Speaker 1>upon the output of the system will exacerbate the problem,

0:37:42.120 --> 0:37:46.800
<v Speaker 1>or maybe it'll just be less effective than alternative decisions

0:37:46.840 --> 0:37:50.720
<v Speaker 1>would be. Further, we're getting closer to that Arthur C.

0:37:50.719 --> 0:37:56.120
<v Speaker 1>Clark statement about sufficiently advanced technologies being indistinguishable from magic.

0:37:56.560 --> 0:37:59.319
<v Speaker 1>If we produce systems that are so complicated that it's

0:37:59.360 --> 0:38:03.239
<v Speaker 1>impossible for us to understand them fully, we might begin

0:38:03.280 --> 0:38:06.399
<v Speaker 1>to view those technologies as being magical or the very

0:38:06.480 --> 0:38:09.200
<v Speaker 1>least greater than the sum of their parts, and this

0:38:09.280 --> 0:38:14.840
<v Speaker 1>can lead to some illogical decisions. This kind of brings

0:38:14.880 --> 0:38:18.080
<v Speaker 1>me to talk about the Church of Ai called the

0:38:18.200 --> 0:38:21.760
<v Speaker 1>Way of the Future, which was founded and then later

0:38:22.080 --> 0:38:27.040
<v Speaker 1>dissolved by Anthony Lewandowski. You may have heard Lewandowski's name

0:38:27.360 --> 0:38:30.000
<v Speaker 1>if you followed the drama of his departure from Google

0:38:30.360 --> 0:38:35.160
<v Speaker 1>and his eventual employment and subsequent termination from Uber. And

0:38:35.200 --> 0:38:37.920
<v Speaker 1>then there was also the fact that he was sentenced

0:38:38.000 --> 0:38:42.480
<v Speaker 1>to go to prison for stealing company secrets and then

0:38:42.560 --> 0:38:46.960
<v Speaker 1>later received a presidential pardon from Donald Trump. So quick

0:38:47.000 --> 0:38:53.200
<v Speaker 1>recap on Lewandowski. Lewandowski worked within Google's autonomous vehicle division,

0:38:53.440 --> 0:38:58.120
<v Speaker 1>which would eventually become a full subsidiary of Google's parent company, Alphabet,

0:38:58.480 --> 0:39:03.160
<v Speaker 1>and that subsidiary is called Weimo. So when Lewandowski left Google,

0:39:03.400 --> 0:39:07.120
<v Speaker 1>he brought with him a whole lot of data, data

0:39:07.200 --> 0:39:11.359
<v Speaker 1>that Google claimed belonged to the company and was proprietary

0:39:11.360 --> 0:39:16.359
<v Speaker 1>in nature and thus constituted company secrets. Lewandowski eventually began

0:39:16.440 --> 0:39:19.960
<v Speaker 1>working with Uber in that company's own driverless vehicle initiative,

0:39:20.360 --> 0:39:24.520
<v Speaker 1>but the Google slash Weimo investigation would lead to Uber

0:39:24.719 --> 0:39:29.239
<v Speaker 1>hastily firing Lewandowski in sort of an attempt to kind

0:39:29.239 --> 0:39:33.080
<v Speaker 1>of disentangle Uber from this matter, which only worked a

0:39:33.080 --> 0:39:36.480
<v Speaker 1>little bit anyway. In the midst of all this Weimo

0:39:37.000 --> 0:39:42.200
<v Speaker 1>slash Uber drama, in twenty seventeen, Wired ran an article

0:39:42.400 --> 0:39:46.160
<v Speaker 1>that explained that this same Anthony Lewandowski had formed a

0:39:46.239 --> 0:39:49.480
<v Speaker 1>church called Way of the Future a couple of years earlier.

0:39:49.680 --> 0:39:52.799
<v Speaker 1>In twenty fifteen, he placed himself at the head of

0:39:52.840 --> 0:39:55.720
<v Speaker 1>this church with the title of dean, and he also

0:39:56.200 --> 0:40:01.120
<v Speaker 1>became the CEO of the nonprofit organization designed to run

0:40:01.160 --> 0:40:04.479
<v Speaker 1>the church. The aim of the church was to see

0:40:04.640 --> 0:40:09.520
<v Speaker 1>quote the realization, acceptance, and worship of a Godhead based

0:40:09.560 --> 0:40:15.160
<v Speaker 1>on artificial intelligence AI developed through computer hardware and software

0:40:15.360 --> 0:40:18.640
<v Speaker 1>end quote. This is according to the founding documents that

0:40:18.680 --> 0:40:23.160
<v Speaker 1>were filed with the US Internal Revenue Service or IRS. Further,

0:40:23.520 --> 0:40:26.760
<v Speaker 1>Lewandowski planned to start seminars based on this very idea

0:40:26.840 --> 0:40:31.480
<v Speaker 1>later in twenty seventeen. By twenty twenty, Lewandowski's jumped from

0:40:31.520 --> 0:40:37.359
<v Speaker 1>Google to Uber escalated into a prison sentence of eighteen months,

0:40:37.440 --> 0:40:40.719
<v Speaker 1>and it was because he had been found guilty of

0:40:40.760 --> 0:40:45.040
<v Speaker 1>stealing trade secrets. Trump would pardon Lewandowski in January twenty

0:40:45.080 --> 0:40:48.160
<v Speaker 1>twenty one, kind of you know, after the insurrection on

0:40:48.239 --> 0:40:52.200
<v Speaker 1>January sixth, but before Trump would leave office in late January.

0:40:53.440 --> 0:40:56.359
<v Speaker 1>As for the Way of the Future, Lewandowski actually began

0:40:56.400 --> 0:40:59.759
<v Speaker 1>to shut that down in June of twenty twenty and

0:40:59.800 --> 0:41:02.480
<v Speaker 1>it was dissolved by the end of twenty twenty, but

0:41:02.560 --> 0:41:06.239
<v Speaker 1>not reported on until like February twenty twenty one. He

0:41:06.320 --> 0:41:09.080
<v Speaker 1>directed the assets of the church some one hundred and

0:41:09.080 --> 0:41:12.360
<v Speaker 1>seventy five thousand dollars to be donated to the NAACP.

0:41:13.200 --> 0:41:19.040
<v Speaker 1>Lewandowski has said that the beliefs behind the church are

0:41:19.120 --> 0:41:23.480
<v Speaker 1>ones that he still adheres to, that AI has the

0:41:23.480 --> 0:41:29.080
<v Speaker 1>potential to tackle very challenging problems like taking care of

0:41:29.120 --> 0:41:33.240
<v Speaker 1>the planet, which Lewandowski says, obviously we humans are incapable

0:41:33.480 --> 0:41:36.759
<v Speaker 1>of doing that. You know, we would put on this

0:41:36.920 --> 0:41:41.480
<v Speaker 1>system taking care of things that we understand to be important,

0:41:41.480 --> 0:41:46.720
<v Speaker 1>but we seem to be incapable of handling ourselves, almost

0:41:46.719 --> 0:41:51.000
<v Speaker 1>like we're children. Thus looking at AI like a godhead,

0:41:51.760 --> 0:41:56.319
<v Speaker 1>so we should seek out solutions with AI rather than

0:41:56.360 --> 0:42:00.920
<v Speaker 1>locking AI away and saying, oh, we can't push AI's

0:42:00.960 --> 0:42:05.239
<v Speaker 1>development further in these directions because of the potential existential

0:42:05.320 --> 0:42:11.120
<v Speaker 1>dangers that could emerge from AI becoming super intelligent. I

0:42:11.160 --> 0:42:13.440
<v Speaker 1>don't think there are actually that many folks who are

0:42:13.480 --> 0:42:16.439
<v Speaker 1>trying to lock AI away at all. Mostly I see

0:42:16.480 --> 0:42:20.080
<v Speaker 1>tons of efforts to improve aspects of AI from a

0:42:20.120 --> 0:42:25.160
<v Speaker 1>million different angles. I think most serious AI researchers and

0:42:25.239 --> 0:42:29.480
<v Speaker 1>scientists aren't really focused on strong AI at all. They're

0:42:29.520 --> 0:42:34.920
<v Speaker 1>looking at very particular applications of artificial intelligence, very particular

0:42:35.000 --> 0:42:39.520
<v Speaker 1>implementations of it, but not like a strong AI that

0:42:39.600 --> 0:42:44.520
<v Speaker 1>acts like deep thought from the Hitchhacker's Guide to the Galaxy. Anyway,

0:42:45.840 --> 0:42:49.880
<v Speaker 1>maybe Lewandowski's vision will eventually lead us not to a

0:42:50.120 --> 0:42:54.280
<v Speaker 1>ghost in the machine, but a literal dios x makina

0:42:54.960 --> 0:42:59.200
<v Speaker 1>that means god out of the machine. That seems to

0:42:59.239 --> 0:43:03.560
<v Speaker 1>be how Levendal's Ski views the potential of AI that

0:43:03.680 --> 0:43:08.959
<v Speaker 1>are unsolvable problems are almost magically fixed thanks to this

0:43:09.440 --> 0:43:15.560
<v Speaker 1>robotic or computational savior. Know In fiction, deos ex machina

0:43:15.920 --> 0:43:18.680
<v Speaker 1>is often seen as a cop out. Right, You've got

0:43:18.719 --> 0:43:23.319
<v Speaker 1>your characters in some sort of ironclad disastrous situation, there's

0:43:23.440 --> 0:43:27.640
<v Speaker 1>no escape for them, and then in order to get

0:43:27.719 --> 0:43:32.120
<v Speaker 1>that happy ending, you have some unlikely savior or unlikely

0:43:32.200 --> 0:43:36.719
<v Speaker 1>event happen and everyone gets saved, and it might be

0:43:36.800 --> 0:43:40.040
<v Speaker 1>satisfying because you've got the happy ending, but upon critical

0:43:40.080 --> 0:43:42.839
<v Speaker 1>reflection you think, well, that doesn't really make sense. There

0:43:42.840 --> 0:43:44.360
<v Speaker 1>are a lot of stories that get a lot of

0:43:44.400 --> 0:43:48.920
<v Speaker 1>flak for using deosx machina. The image I always have

0:43:49.080 --> 0:43:52.320
<v Speaker 1>is from classical theater, where you've got all the mortal

0:43:52.440 --> 0:43:58.720
<v Speaker 1>characters in a terrible situation and then an actor standing

0:43:58.760 --> 0:44:01.960
<v Speaker 1>in as a god is literally lowered from the top

0:44:02.000 --> 0:44:05.280
<v Speaker 1>of the stage on pulleys to descend to the moral

0:44:05.320 --> 0:44:08.280
<v Speaker 1>realm and fix everything so that you can have a comedy,

0:44:08.880 --> 0:44:12.560
<v Speaker 1>a play with a happy ending. For Lewandowski, it's really

0:44:12.600 --> 0:44:14.720
<v Speaker 1>about turning the ghost of the machine into a god.

0:44:15.520 --> 0:44:18.520
<v Speaker 1>I'm not so sure about that myself. I don't know

0:44:18.920 --> 0:44:22.880
<v Speaker 1>if that's a realistic vision. I can see the appeal

0:44:22.880 --> 0:44:26.160
<v Speaker 1>of it, because we do have these very difficult problems

0:44:26.200 --> 0:44:29.399
<v Speaker 1>that we need to solve, and we have had very

0:44:29.440 --> 0:44:32.400
<v Speaker 1>little progress on many of those problems for multiple reasons,

0:44:32.400 --> 0:44:35.080
<v Speaker 1>not just a lack of information, but a lack of

0:44:35.239 --> 0:44:40.239
<v Speaker 1>motivation or conflicting motivations where we have other needs that

0:44:40.480 --> 0:44:45.359
<v Speaker 1>have to be met that conflict with the solving of

0:44:45.520 --> 0:44:48.080
<v Speaker 1>a tough problem like climate change. Right, we have energy

0:44:48.160 --> 0:44:50.040
<v Speaker 1>needs that need to be met. There are places in

0:44:50.080 --> 0:44:55.920
<v Speaker 1>the developing world that would be disproportionately affected by massive

0:44:56.200 --> 0:44:59.319
<v Speaker 1>policies that were meant to mitigate climate change, and it's

0:44:59.440 --> 0:45:02.680
<v Speaker 1>tough to address that. Right. There are these real reasons

0:45:02.680 --> 0:45:07.880
<v Speaker 1>why it's a complicated issue beyond just it's hard to understand.

0:45:08.280 --> 0:45:12.880
<v Speaker 1>So I see the appeal of it, but it also

0:45:12.960 --> 0:45:14.719
<v Speaker 1>kind of feels like a cop out to me, Like

0:45:14.760 --> 0:45:17.400
<v Speaker 1>this idea of will engineer our way out of this problem,

0:45:17.719 --> 0:45:21.160
<v Speaker 1>because that just puts off doing anything about the problem

0:45:21.280 --> 0:45:24.560
<v Speaker 1>until future you can get around to it. I don't

0:45:24.560 --> 0:45:28.200
<v Speaker 1>know about any of you, but I am very much

0:45:28.239 --> 0:45:30.920
<v Speaker 1>guilty of the idea of, you know what this is,

0:45:31.080 --> 0:45:33.839
<v Speaker 1>future Jonathan will take care of this. Jonathan right now

0:45:33.840 --> 0:45:35.879
<v Speaker 1>has to focus on these other things. Future Jonathan will

0:45:35.880 --> 0:45:38.840
<v Speaker 1>take it. Future Jonathan, by the way, hates Jonathan of

0:45:38.960 --> 0:45:42.640
<v Speaker 1>right now and really hates Jonathan in the past because

0:45:43.600 --> 0:45:46.160
<v Speaker 1>it's just putting things off until it gets to a

0:45:46.200 --> 0:45:48.200
<v Speaker 1>point where you can't do it anymore, and by then

0:45:48.239 --> 0:45:49.919
<v Speaker 1>it might be too late. So that's what I worry

0:45:49.960 --> 0:45:53.320
<v Speaker 1>about with this particular approach, this idea of we'll figure

0:45:53.360 --> 0:45:55.440
<v Speaker 1>it out, will science our way out, we'll engineer our

0:45:55.480 --> 0:45:59.720
<v Speaker 1>way out, because it's projecting all that into the future

0:45:59.760 --> 0:46:03.719
<v Speaker 1>and not doing anything in the present anyway. That's the

0:46:03.760 --> 0:46:08.279
<v Speaker 1>episode on ghost in the Machine. There are other interpretations

0:46:08.320 --> 0:46:11.760
<v Speaker 1>as well. There's some great ones in fiction where sometimes

0:46:11.760 --> 0:46:14.200
<v Speaker 1>you actually have a literal ghost in the machine, like

0:46:14.239 --> 0:46:19.200
<v Speaker 1>there's a haunted machine. But maybe I'll wait and tackle

0:46:19.280 --> 0:46:24.279
<v Speaker 1>that for a future, more like entertainment focused episode where

0:46:24.280 --> 0:46:27.160
<v Speaker 1>it's not so much about the technology but kind of

0:46:27.200 --> 0:46:32.160
<v Speaker 1>a critique of the entertainment itself, because there's only so

0:46:32.239 --> 0:46:34.759
<v Speaker 1>much you can say about. You know, I don't know

0:46:35.680 --> 0:46:39.640
<v Speaker 1>a ghost calculator. That's it for this episode. If you

0:46:39.760 --> 0:46:43.520
<v Speaker 1>have suggestions for future episode topics or anything else that

0:46:43.560 --> 0:46:45.000
<v Speaker 1>you would like to communicate to me, there are a

0:46:45.000 --> 0:46:46.799
<v Speaker 1>couple of ways you can do that. One is you

0:46:46.840 --> 0:46:51.440
<v Speaker 1>can download the iHeartRadio app and navigate over to tech Stuff.

0:46:51.480 --> 0:46:53.719
<v Speaker 1>Just put tech Stuff in the little search field and

0:46:53.760 --> 0:46:56.439
<v Speaker 1>you'll see that it'll pop up. You go to the

0:46:56.480 --> 0:47:00.279
<v Speaker 1>tech Stuff page and there's a little microphone icon. Click

0:47:00.320 --> 0:47:03.279
<v Speaker 1>on that. You can leave a voice message up to

0:47:03.480 --> 0:47:05.279
<v Speaker 1>thirty seconds in length and let me know what you

0:47:05.280 --> 0:47:07.440
<v Speaker 1>would like to hear in future episodes. And if you like,

0:47:07.520 --> 0:47:10.080
<v Speaker 1>you can even tell me if I can use your

0:47:10.280 --> 0:47:13.360
<v Speaker 1>voice message in a future episode. Just let me know.

0:47:13.640 --> 0:47:16.160
<v Speaker 1>I'm all about opt in. I'm not gonna do it automatically,

0:47:16.880 --> 0:47:19.240
<v Speaker 1>or if you prefer, you can reach out on Twitter.

0:47:19.480 --> 0:47:23.560
<v Speaker 1>The handle for the show is tech Stuff HSW and

0:47:23.600 --> 0:47:33.239
<v Speaker 1>I'll talk to you again really soon. Tech Stuff is

0:47:33.280 --> 0:47:37.840
<v Speaker 1>an iHeartRadio production. For more podcasts from iHeartRadio, visit the

0:47:37.880 --> 0:47:41.480
<v Speaker 1>iHeartRadio app, Apple Podcasts, or wherever you listen to your

0:47:41.560 --> 0:47:46.160
<v Speaker 1>favorite shows,