WEBVTT - Three Cool Talks at Think2018

0:00:04.160 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.240 --> 0:00:13.880
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:13.920 --> 0:00:17.000
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer at

0:00:17.040 --> 0:00:19.320
<v Speaker 1>how Stuff Works and I love all things tech. And

0:00:19.360 --> 0:00:23.360
<v Speaker 1>here is another special episode brought to you from the

0:00:23.440 --> 0:00:27.040
<v Speaker 1>IBM Think two thousand and eighteen conference. I've been going

0:00:27.080 --> 0:00:30.240
<v Speaker 1>to this all week in Las Vegas, Nevada. It is Thursday,

0:00:30.320 --> 0:00:33.800
<v Speaker 1>March twenty two as I record this episode, and you

0:00:33.880 --> 0:00:37.000
<v Speaker 1>probably heard me speak a little bit about a lot

0:00:37.040 --> 0:00:40.519
<v Speaker 1>of different topics that I've heard about here at the

0:00:40.680 --> 0:00:44.839
<v Speaker 1>Think two thousand eighteen conference, and uh pretty much wrapped

0:00:44.840 --> 0:00:49.080
<v Speaker 1>everything up. I am technically attending the conference today. However,

0:00:49.120 --> 0:00:51.640
<v Speaker 1>I'm also checking out of my hotel room today, which

0:00:51.640 --> 0:00:54.120
<v Speaker 1>means I will not have a dedicated place to sit

0:00:54.160 --> 0:00:58.600
<v Speaker 1>down and record. So I might record another episode after this,

0:00:58.640 --> 0:01:02.240
<v Speaker 1>depending upon what I counter today, but that might have

0:01:02.280 --> 0:01:04.400
<v Speaker 1>to wait until I get back to the studio because

0:01:04.400 --> 0:01:06.280
<v Speaker 1>I may not be able to find a corner to

0:01:06.360 --> 0:01:09.160
<v Speaker 1>sit down and record and that is suitable for such

0:01:09.200 --> 0:01:12.440
<v Speaker 1>a thing. However, I do have that opportunity right now,

0:01:13.120 --> 0:01:17.200
<v Speaker 1>and I figure I would have this chance to kind

0:01:17.200 --> 0:01:19.959
<v Speaker 1>of talk to you about a few different speakers I

0:01:20.080 --> 0:01:23.400
<v Speaker 1>had the chance to to witness and listen to while

0:01:23.440 --> 0:01:26.720
<v Speaker 1>I was here at think two thousand eighteen, and uh,

0:01:26.760 --> 0:01:29.720
<v Speaker 1>these were several talks given by various experts, including a

0:01:29.720 --> 0:01:33.960
<v Speaker 1>few who have achieved celebrity status beyond just uh, the

0:01:34.200 --> 0:01:36.920
<v Speaker 1>the tech conference level. And I don't think I could

0:01:36.959 --> 0:01:42.360
<v Speaker 1>talk about any of these presentations as a full episode

0:01:42.360 --> 0:01:45.200
<v Speaker 1>without doing a ton more research to flesh it out,

0:01:45.240 --> 0:01:48.920
<v Speaker 1>to give background, because these presentations were each about forty

0:01:49.000 --> 0:01:52.560
<v Speaker 1>minutes thirty forty minutes long, and so you know, to

0:01:52.760 --> 0:01:55.160
<v Speaker 1>make a what usually ends up being about a forty

0:01:55.160 --> 0:01:58.080
<v Speaker 1>five minute long podcast about a thirty minute talk, you

0:01:58.120 --> 0:02:00.360
<v Speaker 1>can't do that without patting it, which I'm not gonna do.

0:02:00.560 --> 0:02:02.960
<v Speaker 1>That's an insult to you, guys. You deserve better than that,

0:02:04.080 --> 0:02:07.040
<v Speaker 1>or without doing a lot of background information to flesh

0:02:07.040 --> 0:02:10.760
<v Speaker 1>things out to provide context. And while I could, in

0:02:10.880 --> 0:02:13.480
<v Speaker 1>theory do that, there's only so many hours in the day.

0:02:13.600 --> 0:02:15.639
<v Speaker 1>So what we're gonna do instead is I'm going to

0:02:15.720 --> 0:02:18.320
<v Speaker 1>tell you about three of the speakers I've seen and

0:02:18.360 --> 0:02:21.040
<v Speaker 1>the stuff that they covered, and that will be each

0:02:21.160 --> 0:02:23.960
<v Speaker 1>of the three segments of this podcast. And I think

0:02:24.000 --> 0:02:26.320
<v Speaker 1>it's pretty interesting. They were a fascinating group of people.

0:02:26.639 --> 0:02:28.320
<v Speaker 1>And up first was someone who is kind of a

0:02:28.440 --> 0:02:33.680
<v Speaker 1>rock star in science. That would be Neil Degrass Tyson.

0:02:33.840 --> 0:02:36.200
<v Speaker 1>I'm sure most of you have heard about Neil de

0:02:36.200 --> 0:02:40.040
<v Speaker 1>Grass Tyson. Maybe you've watched television programs that he's hosted,

0:02:40.200 --> 0:02:45.000
<v Speaker 1>or heard him chime in on scientific discussions on various venues,

0:02:45.000 --> 0:02:49.120
<v Speaker 1>whether it's online video, radio shows, TV, all sorts of stuff.

0:02:49.320 --> 0:02:52.680
<v Speaker 1>He's uh of course, also made cameo appearances, or at

0:02:52.760 --> 0:02:55.679
<v Speaker 1>least a character that is Neil de Grass Tyson made

0:02:55.760 --> 0:02:58.839
<v Speaker 1>cameo appearances and epic rap battles of history. It wasn't

0:02:58.840 --> 0:03:01.520
<v Speaker 1>actually Neil Degrass Tyson was obviously an actor playing him.

0:03:01.560 --> 0:03:05.119
<v Speaker 1>But he's not just an accomplished scientist. He's a famous

0:03:05.160 --> 0:03:09.360
<v Speaker 1>science communicator. So he uses his knowledge and humor and

0:03:09.440 --> 0:03:14.760
<v Speaker 1>other uh social uh strategies to talk about science with

0:03:14.840 --> 0:03:17.560
<v Speaker 1>the general public and to explain it and to to

0:03:17.639 --> 0:03:20.800
<v Speaker 1>get enthusiasm behind it. He presented a talk here at

0:03:20.840 --> 0:03:24.360
<v Speaker 1>THINK two thousand eighteen called the Knowledge of Nature and

0:03:24.400 --> 0:03:29.080
<v Speaker 1>the Nature of Knowledge. Now, his presentation didn't speak directly

0:03:29.120 --> 0:03:32.040
<v Speaker 1>to the theme of technology, but much of what he

0:03:32.080 --> 0:03:35.560
<v Speaker 1>had to say was relevant to tech, particularly the way

0:03:35.600 --> 0:03:39.200
<v Speaker 1>people who work in tech communicate their work to the public.

0:03:39.520 --> 0:03:42.760
<v Speaker 1>And he began by talking about what we are able

0:03:42.800 --> 0:03:47.320
<v Speaker 1>to observe directly using our five primary senses, those of

0:03:47.360 --> 0:03:51.080
<v Speaker 1>course being site, hearing, smell, taste, and touch. Now he

0:03:51.120 --> 0:03:54.280
<v Speaker 1>acknowledged that we actually have other senses on top of

0:03:54.320 --> 0:03:58.160
<v Speaker 1>these five. You could argue a whole list of different senses,

0:03:58.160 --> 0:04:01.480
<v Speaker 1>like the ability to sense pain, which is related to

0:04:01.600 --> 0:04:05.760
<v Speaker 1>but not completely encompassed by touch. But these are generally

0:04:06.160 --> 0:04:10.640
<v Speaker 1>agreed upon as the five basic senses, and they obviously

0:04:10.720 --> 0:04:15.960
<v Speaker 1>have limits. So let's take an example. Our site is limited.

0:04:16.200 --> 0:04:19.360
<v Speaker 1>Not only can we not focus to an infinite distance,

0:04:19.360 --> 0:04:23.160
<v Speaker 1>Eventually the focal point will exceed what even the keenest

0:04:23.240 --> 0:04:26.640
<v Speaker 1>eyed person can see. We can also only see a

0:04:26.880 --> 0:04:30.160
<v Speaker 1>band of the spectrum of light. We call it the

0:04:30.279 --> 0:04:33.720
<v Speaker 1>visible spectrum. Obviously, you know that's that's all the light

0:04:33.800 --> 0:04:36.720
<v Speaker 1>that human beings are capable of perceiving with their sight.

0:04:37.360 --> 0:04:41.160
<v Speaker 1>But there's obviously light outside of that spectrum. There's ultraviolet light,

0:04:41.200 --> 0:04:44.200
<v Speaker 1>there's infrared light, and we know it exists, but we

0:04:44.240 --> 0:04:47.919
<v Speaker 1>cannot directly observe it with our eyes. And beyond that

0:04:47.960 --> 0:04:52.200
<v Speaker 1>there are other electromagnetic frequencies that we know exist, but

0:04:52.400 --> 0:04:56.479
<v Speaker 1>again we cannot observe them using only our five senses.

0:04:56.920 --> 0:05:01.280
<v Speaker 1>There are similar cases for our other senses, right, Like

0:05:02.000 --> 0:05:04.679
<v Speaker 1>there's limits to what we can hear. We can hear

0:05:04.720 --> 0:05:08.360
<v Speaker 1>at a certain spectrum of sound frequencies. Typically we call

0:05:08.440 --> 0:05:12.440
<v Speaker 1>it twenty hurts to twenty thou hurts and anything in between.

0:05:12.440 --> 0:05:15.760
<v Speaker 1>That that's the the average range of human hearing. And

0:05:15.800 --> 0:05:18.520
<v Speaker 1>of course that range decreases as we get older. As

0:05:18.560 --> 0:05:22.479
<v Speaker 1>we get older, our ability to hear to perceive those

0:05:22.600 --> 0:05:25.920
<v Speaker 1>upper level frequencies, the ones that are at the twenty

0:05:26.360 --> 0:05:30.480
<v Speaker 1>level um, that decreases over time. So we're are our

0:05:30.800 --> 0:05:35.000
<v Speaker 1>range narrows as we get older, and we know obviously

0:05:35.440 --> 0:05:38.039
<v Speaker 1>that there are frequencies outside of that. So he was

0:05:38.120 --> 0:05:42.520
<v Speaker 1>pointing out that we have limitations. It's not that our

0:05:42.560 --> 0:05:45.440
<v Speaker 1>senses are total crap. He was pointing out that there's

0:05:45.480 --> 0:05:47.599
<v Speaker 1>way more out there in the universe than we can

0:05:47.640 --> 0:05:53.479
<v Speaker 1>observe directly, and that, uh, we know this through science

0:05:53.480 --> 0:05:57.200
<v Speaker 1>and technology. We cannot directly experience it as human beings

0:05:57.520 --> 0:06:00.039
<v Speaker 1>in ways that we can make sense of using the

0:06:00.160 --> 0:06:02.720
<v Speaker 1>five basic senses, but we've learned a lot about it

0:06:03.160 --> 0:06:05.359
<v Speaker 1>using science and technology, and you can even think of

0:06:05.360 --> 0:06:10.200
<v Speaker 1>technology as applied science, because without science, there's really no technology.

0:06:10.600 --> 0:06:13.960
<v Speaker 1>With these scientific tools, we can then extend our understanding

0:06:14.040 --> 0:06:18.119
<v Speaker 1>of the universe. We can make observations, we can develop hypotheses,

0:06:18.480 --> 0:06:21.760
<v Speaker 1>we can test those hypotheses to see if they have merit,

0:06:22.320 --> 0:06:25.400
<v Speaker 1>and we can have other people test those hypotheses. We

0:06:25.440 --> 0:06:29.279
<v Speaker 1>can even have them use different methods to test those hypotheses,

0:06:29.279 --> 0:06:33.039
<v Speaker 1>and as long as those results keep coming back, then

0:06:33.200 --> 0:06:35.640
<v Speaker 1>we can be reasonably confident that we've hit on something.

0:06:35.960 --> 0:06:38.120
<v Speaker 1>This is the basis of the scientific method. In fact,

0:06:38.200 --> 0:06:40.640
<v Speaker 1>Neil deGrasse Tyson took some time to talk about the

0:06:40.680 --> 0:06:44.800
<v Speaker 1>scientific method and stress the importance of testing ideas and

0:06:44.880 --> 0:06:47.839
<v Speaker 1>have others test those same ideas, both with an approach

0:06:47.880 --> 0:06:50.960
<v Speaker 1>that is similar to the one you took when you

0:06:51.120 --> 0:06:54.479
<v Speaker 1>first tested it and with other entirely different approaches to

0:06:54.520 --> 0:06:56.839
<v Speaker 1>make sure that they come to the same result. And

0:06:56.880 --> 0:06:59.920
<v Speaker 1>if everyone gets more or less the same answer through

0:07:00.000 --> 0:07:03.159
<v Speaker 1>their various tests, and those tests are considered to be

0:07:03.240 --> 0:07:06.960
<v Speaker 1>well designed, you can feel reasonably sure that the idea

0:07:07.040 --> 0:07:10.560
<v Speaker 1>you had, the observation you made, the conclusion you came

0:07:10.600 --> 0:07:14.480
<v Speaker 1>to is close to an actual truth as close as

0:07:14.880 --> 0:07:17.480
<v Speaker 1>we can reasonably get, and therefore we just kind of

0:07:17.920 --> 0:07:21.440
<v Speaker 1>say it's true, because I mean, otherwise you're being really,

0:07:21.520 --> 0:07:24.320
<v Speaker 1>really particular. And if you argue that we can never

0:07:24.840 --> 0:07:29.160
<v Speaker 1>know the absolute truth, you might be right, but it's

0:07:29.200 --> 0:07:33.840
<v Speaker 1>also kind of impractical. So at some point you just say,

0:07:33.880 --> 0:07:36.080
<v Speaker 1>all right, this is good enough, this is close enough

0:07:36.120 --> 0:07:38.160
<v Speaker 1>to truth for us to call it that. He was

0:07:38.200 --> 0:07:42.680
<v Speaker 1>also careful to differentiate the concept of proof from evidence.

0:07:43.120 --> 0:07:46.160
<v Speaker 1>He talked about proofs in mathematical terms and said, no

0:07:46.280 --> 0:07:49.760
<v Speaker 1>good scientists would ever use the word proof when talking

0:07:49.760 --> 0:07:52.640
<v Speaker 1>about his or her work. You can find evidence to

0:07:52.680 --> 0:07:56.520
<v Speaker 1>support your claims, but not proof. Proofs are for math,

0:07:56.800 --> 0:07:59.560
<v Speaker 1>not for science. This goes back to something else I

0:07:59.560 --> 0:08:02.720
<v Speaker 1>had mentioned and that I had witnessed earlier in the

0:08:02.600 --> 0:08:06.920
<v Speaker 1>h the conference where Chilia Bosquini was talking about lattice

0:08:06.960 --> 0:08:11.720
<v Speaker 1>based cryptography and mathematical proofs, and the person she was

0:08:11.760 --> 0:08:16.760
<v Speaker 1>talking to was interpreting proof as evidence. So he was saying,

0:08:17.160 --> 0:08:20.320
<v Speaker 1>isn't the fact that computers have had so much trouble

0:08:20.680 --> 0:08:26.840
<v Speaker 1>with large factors, large number of factoring that that's proof

0:08:27.520 --> 0:08:31.200
<v Speaker 1>that it is a hard problem. And so they were

0:08:31.240 --> 0:08:33.040
<v Speaker 1>both using a word, but they were using it in

0:08:33.120 --> 0:08:36.480
<v Speaker 1>different ways, and there was a disconnect there. There was

0:08:36.520 --> 0:08:39.160
<v Speaker 1>a miscommunication going on, and I didn't want to butt

0:08:39.160 --> 0:08:41.160
<v Speaker 1>in because it didn't want to be a smarty pants.

0:08:41.760 --> 0:08:44.920
<v Speaker 1>But it was interesting to see this breakdown in communication

0:08:45.000 --> 0:08:50.160
<v Speaker 1>because they're using two separate sets of terminologies that share

0:08:50.160 --> 0:08:54.600
<v Speaker 1>a common a common lexicography, like they're all lexicons that

0:08:54.679 --> 0:08:57.120
<v Speaker 1>are exactly the same, but the meanings are different and

0:08:57.160 --> 0:09:00.520
<v Speaker 1>that's the problem. So then Neil Degrass Tyson went on

0:09:00.559 --> 0:09:04.800
<v Speaker 1>to talk about the difference between accuracy and precision. He

0:09:04.920 --> 0:09:07.760
<v Speaker 1>used a simple question, and that question is what time

0:09:07.840 --> 0:09:10.720
<v Speaker 1>is it? So his first answer was it's two thousand eighteen,

0:09:10.760 --> 0:09:13.160
<v Speaker 1>which is accurate, or at least it's accurate as of

0:09:13.160 --> 0:09:17.000
<v Speaker 1>the recording of this podcast. I'm recording it on March eighteen.

0:09:17.440 --> 0:09:21.199
<v Speaker 1>But even though the answer is accurate, it's not very precise.

0:09:21.320 --> 0:09:23.400
<v Speaker 1>It doesn't go to a very good level of precision.

0:09:23.400 --> 0:09:26.720
<v Speaker 1>It's not useful. Typically, like if I ask you what

0:09:26.840 --> 0:09:28.640
<v Speaker 1>time is it because I need to figure out if

0:09:28.679 --> 0:09:31.839
<v Speaker 1>I'm going to be late to a meeting I'm rushing

0:09:31.880 --> 0:09:33.800
<v Speaker 1>off to, and you just give me the year. That

0:09:33.840 --> 0:09:36.800
<v Speaker 1>doesn't give me enough information to know whether or not

0:09:36.840 --> 0:09:39.080
<v Speaker 1>I need to take a car or if I can

0:09:39.120 --> 0:09:41.720
<v Speaker 1>take a bike ride to get there. However, you could

0:09:41.760 --> 0:09:44.400
<v Speaker 1>also air the other way, where you have a lot

0:09:44.440 --> 0:09:46.480
<v Speaker 1>of precision but not a lot of accuracy. So his

0:09:46.600 --> 0:09:50.560
<v Speaker 1>second answer said, oh, it's oh, seven hours, forty four minutes,

0:09:50.600 --> 0:09:53.920
<v Speaker 1>twenty two seconds and thirty seven milliseconds. Now that answer

0:09:54.000 --> 0:09:56.400
<v Speaker 1>is precise, but it could also be wrong. What if

0:09:56.440 --> 0:10:01.080
<v Speaker 1>it's forty five minutes, so it's off by a whole minute. Yeah,

0:10:01.080 --> 0:10:03.440
<v Speaker 1>you had this huge level of precision, but your accuracy

0:10:03.520 --> 0:10:06.640
<v Speaker 1>was off. Moreover, because you went to such a level

0:10:06.679 --> 0:10:11.480
<v Speaker 1>of precision down to the millisecond, you cannot possibly be

0:10:11.600 --> 0:10:16.320
<v Speaker 1>accurate because by the time you finish telling someone what

0:10:16.360 --> 0:10:19.040
<v Speaker 1>time it is, it will be a different time. And

0:10:19.120 --> 0:10:22.599
<v Speaker 1>so when was it four minutes, twenty two seconds and

0:10:22.640 --> 0:10:25.400
<v Speaker 1>thirty seven milliseconds? Was it when you started telling the

0:10:25.440 --> 0:10:27.880
<v Speaker 1>person what time it was? Was it? The end of

0:10:27.920 --> 0:10:32.320
<v Speaker 1>that precision without accuracy is not very useful either, was

0:10:32.360 --> 0:10:37.000
<v Speaker 1>his point. And uh, his this was to say that

0:10:37.160 --> 0:10:40.880
<v Speaker 1>accuracy and precision are both important, and the level of

0:10:40.880 --> 0:10:44.280
<v Speaker 1>precision you should use when you're communicating something to others

0:10:44.720 --> 0:10:47.520
<v Speaker 1>is dependent upon what you're trying to accomplish. You could

0:10:47.520 --> 0:10:50.760
<v Speaker 1>always get more precise, but sometimes that reaches a level

0:10:50.800 --> 0:10:53.240
<v Speaker 1>that is no longer of any real use. And I

0:10:53.280 --> 0:10:56.000
<v Speaker 1>can identify with this idea. See when I construct an

0:10:56.000 --> 0:10:58.320
<v Speaker 1>episode of tech stuff, when I'm researching and writing up

0:10:58.320 --> 0:11:01.679
<v Speaker 1>my notes, I frequently have to figure out where should

0:11:01.720 --> 0:11:05.559
<v Speaker 1>I start? Where's my starting point for the episode, based

0:11:05.640 --> 0:11:08.280
<v Speaker 1>upon whatever topic it is that I'm covering. Now, Rarely

0:11:08.520 --> 0:11:11.760
<v Speaker 1>do I start right at the quote unquote beginning of

0:11:11.760 --> 0:11:15.160
<v Speaker 1>a technology's creation. And that's because it's usually helpful to

0:11:15.400 --> 0:11:19.400
<v Speaker 1>understand things that were happening before someone, more likely a

0:11:19.440 --> 0:11:24.200
<v Speaker 1>string of someone's invented the technology. Without having that understanding

0:11:24.320 --> 0:11:28.079
<v Speaker 1>of what preceded the invention, you don't really have enough

0:11:28.120 --> 0:11:31.200
<v Speaker 1>context to understand what is going on and why it's important.

0:11:31.520 --> 0:11:33.800
<v Speaker 1>Neil deGrasse Tyson went on to use an example of

0:11:33.800 --> 0:11:37.600
<v Speaker 1>his own as he spoke about the Earth's orbit. The

0:11:37.679 --> 0:11:41.240
<v Speaker 1>shorthand description of the Earth's orbit around the Sun. Something

0:11:41.240 --> 0:11:43.320
<v Speaker 1>that you might have learned in elementary school is that

0:11:43.360 --> 0:11:46.680
<v Speaker 1>it's an elliptical orbit. But that's not entirely accurate. First

0:11:46.720 --> 0:11:49.360
<v Speaker 1>of all, the Earth's orbit is only a slight deviation

0:11:49.600 --> 0:11:52.440
<v Speaker 1>from a circle. You could argue that it's closer to

0:11:52.480 --> 0:11:55.800
<v Speaker 1>being a circular orbit than it is an elliptical orbit.

0:11:55.920 --> 0:11:59.600
<v Speaker 1>But despite this, many textbooks exaggerate the path that the

0:11:59.600 --> 0:12:03.080
<v Speaker 1>Earth's orbit takes to show that's not a perfect circle.

0:12:03.520 --> 0:12:06.199
<v Speaker 1>But even if you were to say it's more circular

0:12:06.240 --> 0:12:10.760
<v Speaker 1>than elliptical, that's not entirely precise because the Earth's Moon

0:12:11.040 --> 0:12:14.360
<v Speaker 1>affects the Earth's orbital path. Now, the Moon does not

0:12:15.080 --> 0:12:18.600
<v Speaker 1>actually revolve around the Earth. Instead, the Earth and the

0:12:18.640 --> 0:12:21.839
<v Speaker 1>Moon are in a dance together. They rotate around a

0:12:21.880 --> 0:12:25.320
<v Speaker 1>common center of gravity between the two. This is true

0:12:25.360 --> 0:12:28.840
<v Speaker 1>for any two objects that are revolving around one another.

0:12:29.040 --> 0:12:33.440
<v Speaker 1>They revolve around a common point of center of gravity. Now,

0:12:33.480 --> 0:12:36.920
<v Speaker 1>as it happens because of the masses of the two

0:12:37.600 --> 0:12:40.760
<v Speaker 1>the two bodies, the Earth and the Moon, the center

0:12:40.800 --> 0:12:44.480
<v Speaker 1>of gravity happens to be located below the Earth's surface.

0:12:44.800 --> 0:12:46.839
<v Speaker 1>But it's not at the center of the Earth. If

0:12:46.840 --> 0:12:48.560
<v Speaker 1>it if it were at the center of the Earth,

0:12:48.559 --> 0:12:52.160
<v Speaker 1>then you could say while the Moon essentially revolves around

0:12:52.160 --> 0:12:55.480
<v Speaker 1>the Earth. Instead, it's about a thousand miles below the

0:12:55.520 --> 0:12:59.400
<v Speaker 1>Earth's surface on whichever side the Moon is on at

0:12:59.440 --> 0:13:02.000
<v Speaker 1>that time. So, in other words, the center of gravity

0:13:02.040 --> 0:13:07.720
<v Speaker 1>moves around the Earth's interior as the Moon continues through

0:13:07.720 --> 0:13:10.520
<v Speaker 1>its orbit, which has the effect of creating a little

0:13:10.559 --> 0:13:13.960
<v Speaker 1>wobble in the Earth's orbit. So you can really think

0:13:14.000 --> 0:13:16.080
<v Speaker 1>of the Earth's orbit around the Sun as a bit

0:13:16.160 --> 0:13:19.240
<v Speaker 1>of a a circle that's made up of a kind

0:13:19.240 --> 0:13:22.240
<v Speaker 1>of squiggly line. Then that squiggly line is the little

0:13:22.360 --> 0:13:26.080
<v Speaker 1>jiggle that the Earth has because of the the Moon,

0:13:26.400 --> 0:13:29.480
<v Speaker 1>the Moon's poll on the Earth. But even that is

0:13:29.520 --> 0:13:33.480
<v Speaker 1>not truly precise, because the Sun in our Solar system

0:13:33.840 --> 0:13:37.520
<v Speaker 1>is orbiting around the galactic center of the Milky Way

0:13:37.600 --> 0:13:41.280
<v Speaker 1>galaxy and it's not in the same plane as Earth's orbit.

0:13:41.400 --> 0:13:45.800
<v Speaker 1>So while from one perspective you could say the Earth

0:13:45.880 --> 0:13:48.880
<v Speaker 1>has a wobbly circular orbit, if you were looking at

0:13:48.920 --> 0:13:51.440
<v Speaker 1>the Sun directly in front of it as it was

0:13:51.480 --> 0:13:54.760
<v Speaker 1>moving through its galactical orbital path, you would see that

0:13:54.800 --> 0:13:57.360
<v Speaker 1>the planets of our Solar system are moving around and

0:13:57.400 --> 0:14:02.640
<v Speaker 1>what it amounts to a spiral Because take any arbitrary

0:14:02.720 --> 0:14:06.600
<v Speaker 1>starting position of the Earth with respect to its position

0:14:06.640 --> 0:14:08.480
<v Speaker 1>with the Sun, and you say, all right, this is

0:14:08.480 --> 0:14:12.800
<v Speaker 1>the day zero, and we're gonna go three days around

0:14:13.200 --> 0:14:15.520
<v Speaker 1>so that we return to our point of origin. The

0:14:15.559 --> 0:14:18.520
<v Speaker 1>thing is you'll never return to that exact fixed point

0:14:18.600 --> 0:14:23.600
<v Speaker 1>in space, because the Solar system itself is uh rotating

0:14:23.600 --> 0:14:26.840
<v Speaker 1>around this galactic center in the Milky Way. So while

0:14:26.960 --> 0:14:31.240
<v Speaker 1>you will return to your same relative position in reference

0:14:31.280 --> 0:14:34.080
<v Speaker 1>to the Sun, you won't be in the same fixed

0:14:34.080 --> 0:14:37.480
<v Speaker 1>point in space because the whole system has been moving

0:14:37.520 --> 0:14:40.880
<v Speaker 1>this entire time. So you can't really even say it's

0:14:40.920 --> 0:14:43.120
<v Speaker 1>a circle. It's more like a spiral when you when

0:14:43.160 --> 0:14:46.480
<v Speaker 1>you take your reference point as the galaxy as opposed

0:14:46.520 --> 0:14:50.080
<v Speaker 1>to just the Solar system. Uh. Again, the whole purpose

0:14:50.120 --> 0:14:52.320
<v Speaker 1>of this was to give an example to say we

0:14:52.400 --> 0:14:55.640
<v Speaker 1>have to make choices when we communicate information to others.

0:14:56.040 --> 0:14:57.960
<v Speaker 1>At what point do we need to draw the line

0:14:57.960 --> 0:15:00.880
<v Speaker 1>and say, okay, that's enough detail. Anything more than that

0:15:01.000 --> 0:15:04.880
<v Speaker 1>is either confusing or it's boring, or it's both. And

0:15:04.920 --> 0:15:06.920
<v Speaker 1>then we make those determinations and hope that we can

0:15:06.960 --> 0:15:10.520
<v Speaker 1>inspire people to look further into subjects. Later on, Neil

0:15:10.560 --> 0:15:14.360
<v Speaker 1>deGrasse Tyson's presentation concluded with a discussion about how to

0:15:14.440 --> 0:15:17.440
<v Speaker 1>convey information to your audience in a way that matters

0:15:17.480 --> 0:15:21.800
<v Speaker 1>to them. He showed examples of science incorporated into pop culture.

0:15:22.400 --> 0:15:25.880
<v Speaker 1>He specifically played a clip from the movie Frozen and

0:15:25.920 --> 0:15:29.280
<v Speaker 1>then he danced around on stage as Elsa sang frozen

0:15:29.400 --> 0:15:33.800
<v Speaker 1>fractals all around because the word fractal was included in

0:15:33.880 --> 0:15:37.040
<v Speaker 1>a Disney film and sung by a Disney princess. And

0:15:37.080 --> 0:15:41.480
<v Speaker 1>he said, this is amazing progress. He said, you need

0:15:41.560 --> 0:15:43.840
<v Speaker 1>to find out what your audience cares about and then

0:15:43.880 --> 0:15:46.680
<v Speaker 1>find ways to use that as a means of explaining

0:15:46.760 --> 0:15:50.720
<v Speaker 1>scientific or technological ideas to them. And he used football

0:15:50.760 --> 0:15:53.160
<v Speaker 1>as his own example, showing off a series of fairly

0:15:53.200 --> 0:15:56.280
<v Speaker 1>recent tweets he had made during football games to get

0:15:56.280 --> 0:15:59.880
<v Speaker 1>across scientific principles. Now, those tweets sparked a lot of

0:16:00.000 --> 0:16:03.280
<v Speaker 1>conversation and humor and jokes around his followers and other

0:16:03.280 --> 0:16:05.760
<v Speaker 1>people who saw those messages, and it meant that for

0:16:05.840 --> 0:16:09.240
<v Speaker 1>a short while at least, people were talking about actual science.

0:16:09.960 --> 0:16:12.000
<v Speaker 1>For people in the technology space, that could be a

0:16:12.080 --> 0:16:16.440
<v Speaker 1>very valuable lesson because technology gets super complicated, and not

0:16:16.600 --> 0:16:21.400
<v Speaker 1>only can the actual mechanics of technology get complex, the

0:16:21.400 --> 0:16:25.480
<v Speaker 1>way it works and the intricacies of how it works.

0:16:26.200 --> 0:16:30.560
<v Speaker 1>The way we describe technology can also be really confusing

0:16:30.600 --> 0:16:32.320
<v Speaker 1>because we use a lot of jargon, a lot of

0:16:32.440 --> 0:16:36.600
<v Speaker 1>terminology that is not in the common parlance, and we

0:16:36.680 --> 0:16:40.520
<v Speaker 1>use a lot of shorthand to communicate complicated ideas. To

0:16:40.600 --> 0:16:45.240
<v Speaker 1>a newcomer, this comes across as incredibly intimidating, very dense,

0:16:45.360 --> 0:16:48.640
<v Speaker 1>and difficult to understand. Before you can even get to

0:16:48.720 --> 0:16:53.520
<v Speaker 1>the point where you comprehend the actual concepts that underlie technology,

0:16:53.760 --> 0:16:56.239
<v Speaker 1>you first have to get a grip on the language

0:16:56.280 --> 0:16:59.360
<v Speaker 1>that's being used. Then you have to struggle with that

0:16:59.440 --> 0:17:03.480
<v Speaker 1>language to understand what is actually happening with any technological,

0:17:04.080 --> 0:17:08.200
<v Speaker 1>uh product, or service. And if technologies can use analogies

0:17:08.359 --> 0:17:11.679
<v Speaker 1>or stories or examples to explain their work, If if

0:17:11.720 --> 0:17:15.800
<v Speaker 1>technologists rather can use those tools to explain what it

0:17:15.840 --> 0:17:18.159
<v Speaker 1>is they're doing and what they're they're the things they

0:17:18.160 --> 0:17:22.240
<v Speaker 1>work on, what they do, then the general public may

0:17:22.520 --> 0:17:25.520
<v Speaker 1>end up having a more enthusiastic response because they'll have

0:17:25.600 --> 0:17:30.440
<v Speaker 1>a touchstone to understand what exactly is going on. Now,

0:17:30.480 --> 0:17:34.080
<v Speaker 1>that's easier said than done, because you you gotta you

0:17:34.119 --> 0:17:37.320
<v Speaker 1>gotta walk a line. You don't want to simplify matters

0:17:37.800 --> 0:17:41.480
<v Speaker 1>to the point where people are going to misunderstand what

0:17:41.520 --> 0:17:44.960
<v Speaker 1>you're saying. So with some subjects like artificial intelligence or

0:17:45.040 --> 0:17:48.680
<v Speaker 1>quantum computing, going too broad or too simple will make

0:17:48.720 --> 0:17:51.920
<v Speaker 1>people think that the technology is akin to magic because

0:17:52.320 --> 0:17:55.760
<v Speaker 1>you've you've abstracted it and you've simplified it so much

0:17:56.320 --> 0:17:59.240
<v Speaker 1>that it just sounds like it does things that nothing

0:17:59.280 --> 0:18:03.320
<v Speaker 1>could truly possibly do, or you give them the idea

0:18:03.400 --> 0:18:06.399
<v Speaker 1>that this technology is capable of doing things that we

0:18:06.480 --> 0:18:09.880
<v Speaker 1>really can't do yet. So, like the science lesson about

0:18:09.920 --> 0:18:12.160
<v Speaker 1>the Earth's orbit, there's a balance we have to achieve

0:18:12.280 --> 0:18:15.320
<v Speaker 1>when we're explaining these things to someone new to the

0:18:15.359 --> 0:18:18.320
<v Speaker 1>subject matter. And that's true across every industry. It's not

0:18:18.400 --> 0:18:22.119
<v Speaker 1>just science or technology. I mean, there are plenty of

0:18:22.440 --> 0:18:27.160
<v Speaker 1>discussions about business and particularly finance. Law is another example.

0:18:27.720 --> 0:18:31.600
<v Speaker 1>Whenever I read any stories about finance or law or business,

0:18:32.040 --> 0:18:34.320
<v Speaker 1>I get to a point where I realize I've read

0:18:34.359 --> 0:18:37.439
<v Speaker 1>a paragraph and I have absolutely no idea what that

0:18:37.480 --> 0:18:40.280
<v Speaker 1>paragraph meant. I can reread it and I can say

0:18:40.320 --> 0:18:43.160
<v Speaker 1>to myself, I individually I understand what all of these

0:18:43.200 --> 0:18:46.720
<v Speaker 1>words mean, but collectively I don't get what they're trying

0:18:46.720 --> 0:18:49.359
<v Speaker 1>to say. And you know that that comes with the

0:18:49.440 --> 0:18:53.240
<v Speaker 1>territory of having specialization in any field. Eventually get to

0:18:53.280 --> 0:18:57.200
<v Speaker 1>a point where the language you use is extremely efficient.

0:18:57.320 --> 0:18:59.880
<v Speaker 1>If you're talking to someone else who shares your knowledge,

0:19:00.160 --> 0:19:03.800
<v Speaker 1>you can have very deep very quick conversations based upon

0:19:03.840 --> 0:19:06.480
<v Speaker 1>this shared language. But if you try to communicate to

0:19:06.480 --> 0:19:09.119
<v Speaker 1>anyone outside of that, you get the deer in the

0:19:09.119 --> 0:19:11.960
<v Speaker 1>headlights look. Or at least that's what I get whenever

0:19:12.000 --> 0:19:14.400
<v Speaker 1>I try and talk to anyone about finance or law

0:19:14.520 --> 0:19:16.840
<v Speaker 1>or anything like that. So that's why I try to

0:19:16.880 --> 0:19:19.280
<v Speaker 1>structure episodes the way I do. It's not that I

0:19:19.320 --> 0:19:22.320
<v Speaker 1>don't have faith in my audience. I have a great audience.

0:19:22.359 --> 0:19:25.280
<v Speaker 1>I have a really smart and engaging audience. It's that

0:19:25.680 --> 0:19:28.680
<v Speaker 1>I never know when it might be someone's first introduction

0:19:28.880 --> 0:19:31.680
<v Speaker 1>to that specific subject matter, and I want to make

0:19:31.720 --> 0:19:34.760
<v Speaker 1>sure that I can build a foundation before diving more

0:19:34.800 --> 0:19:37.639
<v Speaker 1>deeply into any given topic. When we come back from

0:19:37.680 --> 0:19:40.680
<v Speaker 1>the break, i'll tell you about the presentation a famous

0:19:40.720 --> 0:19:45.760
<v Speaker 1>futurist gave at IBM Think. But first let's take a

0:19:45.800 --> 0:19:56.080
<v Speaker 1>break and thank our sponsor. The next famous person I

0:19:56.080 --> 0:19:58.879
<v Speaker 1>saw give a presentation at Think two thousand eighteen was

0:19:59.000 --> 0:20:03.600
<v Speaker 1>Dr michio Aku. Dr Cocku is a theoretical physicist and

0:20:03.600 --> 0:20:06.760
<v Speaker 1>a professor at City College of New York. He's also

0:20:06.800 --> 0:20:10.080
<v Speaker 1>an author. A futurist, UH that would be someone who

0:20:10.080 --> 0:20:13.680
<v Speaker 1>predicts how technology and advancements and science will change our

0:20:13.720 --> 0:20:16.680
<v Speaker 1>world in the decades to come very close to my heart.

0:20:16.720 --> 0:20:19.359
<v Speaker 1>Since I used to host a show called Forward Thinking.

0:20:19.400 --> 0:20:22.400
<v Speaker 1>In fact, I often would read about Minchio Okaku's work

0:20:22.920 --> 0:20:25.760
<v Speaker 1>as a host of Forward Thinking, I would refer to

0:20:25.840 --> 0:20:28.280
<v Speaker 1>that as part of the research I did for lots

0:20:28.280 --> 0:20:31.399
<v Speaker 1>of different topics. He's a frequent guest or host on

0:20:31.560 --> 0:20:34.560
<v Speaker 1>television series and radio programs, and he talks a lot

0:20:34.600 --> 0:20:38.479
<v Speaker 1>about his work and predictions regularly. He has specifically studied

0:20:38.560 --> 0:20:41.639
<v Speaker 1>quantum mechanics and string theory. Now, I've talked an awful

0:20:41.680 --> 0:20:44.040
<v Speaker 1>lot about quantum mechanics already in this mini series, so

0:20:44.080 --> 0:20:46.240
<v Speaker 1>I'm not going to rehash that. But what the heck

0:20:46.320 --> 0:20:50.720
<v Speaker 1>is string theory? Well, string theory is a family of

0:20:50.840 --> 0:20:55.840
<v Speaker 1>theories that attempt to describe why fundamental forces and particles

0:20:55.880 --> 0:21:00.040
<v Speaker 1>found in nature behave the way they do. They go

0:21:00.119 --> 0:21:05.159
<v Speaker 1>into topic in depth. Uh, it would require a whole

0:21:05.240 --> 0:21:08.560
<v Speaker 1>suite of episodes to explain this. And there are multiple

0:21:08.880 --> 0:21:12.320
<v Speaker 1>types of string theory. There's not just one string theory.

0:21:12.680 --> 0:21:16.520
<v Speaker 1>There are competing theories. Um. I would rapidly find myself

0:21:16.520 --> 0:21:19.719
<v Speaker 1>out of depth if I tried to tackle the entire field,

0:21:19.760 --> 0:21:23.040
<v Speaker 1>and even sum summarize it in uh, you know, in

0:21:23.080 --> 0:21:27.040
<v Speaker 1>a way that was at least semi comprehensive, but I

0:21:27.080 --> 0:21:30.119
<v Speaker 1>can give a very super high level idea. In general,

0:21:30.480 --> 0:21:35.440
<v Speaker 1>these theories describe forces and particles as one dimensional strings

0:21:35.480 --> 0:21:38.879
<v Speaker 1>that vibrate in a way that gives those forces and

0:21:38.960 --> 0:21:42.920
<v Speaker 1>particles their properties. Some of them are closed loop strings

0:21:43.000 --> 0:21:46.160
<v Speaker 1>that are like rubber bands. Dr Cocu has talked about

0:21:46.200 --> 0:21:50.040
<v Speaker 1>supersymmetric string theory in particular. That's one of the flavors

0:21:50.080 --> 0:21:53.600
<v Speaker 1>of string theory, and it's really fascinating stuff that at

0:21:53.680 --> 0:21:57.240
<v Speaker 1>least I'm told makes sense from a mathematical perspective. Now

0:21:57.240 --> 0:21:59.320
<v Speaker 1>I say I'm told because the math is far too

0:21:59.320 --> 0:22:02.600
<v Speaker 1>complex for me to understand, so I certainly can't look

0:22:02.600 --> 0:22:04.800
<v Speaker 1>at and say, oh, yeah, no, that holds up. But

0:22:04.880 --> 0:22:07.960
<v Speaker 1>as of right now and for the foreseeable future, we

0:22:08.000 --> 0:22:11.919
<v Speaker 1>have no way to directly observe and test string theory,

0:22:12.359 --> 0:22:14.199
<v Speaker 1>which has led some people to say that's not so

0:22:14.280 --> 0:22:17.879
<v Speaker 1>much a scientific theory as it is a philosophy because

0:22:17.880 --> 0:22:20.520
<v Speaker 1>you cannot test or observe it. But we'll set that

0:22:20.600 --> 0:22:24.639
<v Speaker 1>whole argument aside. Dr Kaku, who took the main stage

0:22:24.640 --> 0:22:28.439
<v Speaker 1>here at IBM focus largely unwary thinks humanity will be

0:22:28.440 --> 0:22:31.520
<v Speaker 1>headed in the next few decades with the space the

0:22:31.560 --> 0:22:35.119
<v Speaker 1>space missions in particular, he pointed out that today's computers

0:22:35.200 --> 0:22:39.040
<v Speaker 1>still depend upon silicon chips and Moore's law, but he

0:22:39.040 --> 0:22:42.600
<v Speaker 1>also talked about the ultimate limits of that technology, and

0:22:42.640 --> 0:22:45.159
<v Speaker 1>as I mentioned in this series, you can only shrink

0:22:45.200 --> 0:22:49.440
<v Speaker 1>components down so far using traditional silicon chip technology. Once

0:22:49.440 --> 0:22:53.639
<v Speaker 1>you shrink below certain thresholds, quantum effects begin to override

0:22:53.680 --> 0:22:57.280
<v Speaker 1>your classical computer design, and electrons no longer follow the

0:22:57.320 --> 0:23:00.000
<v Speaker 1>pathways you've made for them, and our electronics are tod

0:23:00.000 --> 0:23:02.600
<v Speaker 1>in it upon electrons doing what we want them to do.

0:23:02.960 --> 0:23:05.840
<v Speaker 1>At the quantum level, electrons do lots of strange things,

0:23:06.080 --> 0:23:09.520
<v Speaker 1>things we can't necessarily control or predict, and that means

0:23:09.800 --> 0:23:13.320
<v Speaker 1>our electronics and computers that are built on these components

0:23:14.280 --> 0:23:18.160
<v Speaker 1>cannot really work properly. They will will become unreliable, they'll

0:23:18.200 --> 0:23:21.600
<v Speaker 1>become error prone. We can't we can't keep going this

0:23:21.720 --> 0:23:26.240
<v Speaker 1>route indefinitely. We will eventually hit that fundamental physical level

0:23:26.320 --> 0:23:29.800
<v Speaker 1>based upon how we build things today. So something has

0:23:29.880 --> 0:23:32.960
<v Speaker 1>to change now. Dr Cocu said, if we cling to

0:23:33.000 --> 0:23:35.879
<v Speaker 1>silicon as the basis for our technology moving forward, then

0:23:35.880 --> 0:23:39.520
<v Speaker 1>eventually Silicon Valley could become a new rust belt. We

0:23:39.560 --> 0:23:42.280
<v Speaker 1>will hit that ultimate limit of what we're capable of

0:23:42.320 --> 0:23:45.200
<v Speaker 1>doing using that technology, and we will progress no further.

0:23:45.520 --> 0:23:48.400
<v Speaker 1>So we'll need to shift to a new paradigm. Dr

0:23:48.480 --> 0:23:51.000
<v Speaker 1>Kaku mentioned several technologies who felt were going to be

0:23:51.040 --> 0:23:53.760
<v Speaker 1>instrumental in pushing us past the end of the silicon

0:23:53.880 --> 0:23:56.399
<v Speaker 1>chip age and Moore's law, and he talked about the

0:23:56.440 --> 0:24:00.159
<v Speaker 1>four great technological revolutions. The first of those would the

0:24:00.200 --> 0:24:03.560
<v Speaker 1>development of the steam engine, which led to an incredibly

0:24:03.600 --> 0:24:07.920
<v Speaker 1>productive period and the Industrial Revolution. Understanding and leveraging the

0:24:08.000 --> 0:24:11.159
<v Speaker 1>laws of thermodynamics allowed us to create new ways to

0:24:11.200 --> 0:24:14.280
<v Speaker 1>do work and travel. We were able to create engines

0:24:14.359 --> 0:24:18.480
<v Speaker 1>that could harness the power of thermodynamics and translated into work.

0:24:19.200 --> 0:24:22.720
<v Speaker 1>About at eight decades after the invention of the steam engine,

0:24:22.800 --> 0:24:26.320
<v Speaker 1>physicists were getting a much better understanding of some other

0:24:26.359 --> 0:24:31.040
<v Speaker 1>scientific principles like magnetism and electricity, which led to inventions

0:24:31.080 --> 0:24:35.720
<v Speaker 1>like radio and then television. Decades after that, engineers and

0:24:35.760 --> 0:24:40.720
<v Speaker 1>scientists invented the transistor, the third of the technological revolutions.

0:24:40.760 --> 0:24:43.960
<v Speaker 1>That transistor made micro computers possible, as well as other

0:24:44.000 --> 0:24:46.840
<v Speaker 1>devices like lasers, and it allowed us to go to space.

0:24:46.960 --> 0:24:50.119
<v Speaker 1>It created the space industry. In fact, the space industry

0:24:50.920 --> 0:24:56.040
<v Speaker 1>pretty much gave the incentive to development of transistors and manaturization.

0:24:56.640 --> 0:24:59.119
<v Speaker 1>We had a goal, we wanted to send people to

0:24:59.160 --> 0:25:01.359
<v Speaker 1>the Moon, and that meant that we were going to

0:25:01.480 --> 0:25:04.440
<v Speaker 1>have to make some big advancements in science and technology

0:25:04.480 --> 0:25:08.320
<v Speaker 1>in order to make that possible. Space, as in the

0:25:08.359 --> 0:25:11.600
<v Speaker 1>space inside of a capsule, is at a premium. You

0:25:11.600 --> 0:25:13.720
<v Speaker 1>want to make sure things are lightweight, you want to

0:25:13.720 --> 0:25:16.359
<v Speaker 1>make sure things are compact, and that meant that we

0:25:16.359 --> 0:25:19.520
<v Speaker 1>couldn't rely upon the massive circuitry of the past. We

0:25:19.640 --> 0:25:23.560
<v Speaker 1>had to create other means to manaturize things and make

0:25:23.600 --> 0:25:26.840
<v Speaker 1>it more practical for applications like space travel. And uh,

0:25:27.880 --> 0:25:31.840
<v Speaker 1>mitchio Kaku is very excited about space travel. He's very

0:25:31.840 --> 0:25:34.840
<v Speaker 1>excited the fact that we are dedicating ourselves to going

0:25:34.880 --> 0:25:37.720
<v Speaker 1>back to the Moon, first with an unmanned probe that

0:25:37.800 --> 0:25:41.600
<v Speaker 1>should land on the Moon in two thousand nineteen, then

0:25:41.680 --> 0:25:46.440
<v Speaker 1>eventually with a a base in orbit around the Moon

0:25:46.440 --> 0:25:48.720
<v Speaker 1>which will act as sort of a launching ground for

0:25:49.080 --> 0:25:53.680
<v Speaker 1>missions towards Mars. And he talked about how that's very

0:25:53.680 --> 0:25:57.320
<v Speaker 1>important and also mentioned Elon Musk's follow up to the

0:25:57.359 --> 0:26:01.240
<v Speaker 1>Falcon nine Heavy Rocket, which is called the b f R.

0:26:01.440 --> 0:26:04.840
<v Speaker 1>B stands for big, our stands for rocket, and F

0:26:05.119 --> 0:26:09.120
<v Speaker 1>as Dr CaCu says, stands for well, let your imagination

0:26:09.160 --> 0:26:11.720
<v Speaker 1>take over. The Fourth Revolution is the one that's happening

0:26:11.840 --> 0:26:18.080
<v Speaker 1>right now. Dr CaCu says. It involves stuff like biotechnology, nanotechnology,

0:26:18.240 --> 0:26:23.560
<v Speaker 1>artificial intelligence, and related technologies. It's also about computing models

0:26:23.600 --> 0:26:27.120
<v Speaker 1>like neural networks, which mimic the neural structure of brains.

0:26:27.520 --> 0:26:30.359
<v Speaker 1>The neural network is made up of nodes that behave

0:26:30.440 --> 0:26:34.119
<v Speaker 1>like neurons, like the neurons the neural cells we have

0:26:34.240 --> 0:26:37.520
<v Speaker 1>in our brains. There are interconnections with those nodes to

0:26:37.720 --> 0:26:41.439
<v Speaker 1>other artificial neurons, and processing information with a neural network

0:26:41.480 --> 0:26:44.280
<v Speaker 1>allows you to do some interesting things like machine learning.

0:26:44.680 --> 0:26:49.240
<v Speaker 1>Computers relying on an artificial neural network can learn from data,

0:26:49.359 --> 0:26:52.480
<v Speaker 1>and they can get more proficient at handling that information

0:26:52.640 --> 0:26:57.040
<v Speaker 1>as they get more experience, so they improve themselves. Over time,

0:26:57.400 --> 0:27:00.560
<v Speaker 1>the most efficient pathways start to win now over the

0:27:00.640 --> 0:27:04.560
<v Speaker 1>least efficient pathways, and you can teach computers. Now I've

0:27:04.560 --> 0:27:07.720
<v Speaker 1>talked about this before, about teaching computers how to recognize

0:27:07.760 --> 0:27:11.479
<v Speaker 1>what a cat is, for example, which is a somewhat

0:27:11.520 --> 0:27:14.880
<v Speaker 1>trivial version of this, but neural networks are being used

0:27:14.920 --> 0:27:19.160
<v Speaker 1>across multiple industries to solve very difficult problems. He also

0:27:19.200 --> 0:27:22.560
<v Speaker 1>mentioned artificial intelligence, which will augment our abilities to make

0:27:22.600 --> 0:27:25.280
<v Speaker 1>decisions and take actions, and he stressed that he felt

0:27:25.280 --> 0:27:30.000
<v Speaker 1>AI was not poised to replace human beings, but help them.

0:27:30.240 --> 0:27:33.399
<v Speaker 1>He laid out the two big arguments that tend to

0:27:33.720 --> 0:27:37.680
<v Speaker 1>be be presented in AI, sort of the Zuckerberg argument

0:27:38.040 --> 0:27:41.960
<v Speaker 1>versus the Elon Musk argument, and the Zuckerberg argument is

0:27:42.119 --> 0:27:44.240
<v Speaker 1>AI is going to be a huge help. It's going

0:27:44.320 --> 0:27:46.879
<v Speaker 1>to benefit us. It's going to let us do what

0:27:46.920 --> 0:27:49.119
<v Speaker 1>we want to do better and faster. It's going to

0:27:49.200 --> 0:27:52.280
<v Speaker 1>create opportunities that do not exist right now that we

0:27:52.359 --> 0:27:55.560
<v Speaker 1>can't even predict because we aren't in that age yet.

0:27:56.119 --> 0:27:58.399
<v Speaker 1>Musk says it's going to lead to killer robots and

0:27:58.400 --> 0:28:00.919
<v Speaker 1>we're all gonna die now. I am are simplifying on

0:28:01.040 --> 0:28:03.840
<v Speaker 1>both sides, more on Musk than on Zuckerberg for a

0:28:03.840 --> 0:28:08.000
<v Speaker 1>comedic effect. Musk says AI could potentially pose an existential

0:28:08.040 --> 0:28:10.040
<v Speaker 1>threat to the human race, saying that if you were

0:28:10.080 --> 0:28:13.080
<v Speaker 1>to create AI um and you don't have good controls

0:28:13.119 --> 0:28:16.679
<v Speaker 1>in place, then it could be the end of humanity.

0:28:16.760 --> 0:28:20.119
<v Speaker 1>It could eventually decide that we are bad and that

0:28:20.200 --> 0:28:22.840
<v Speaker 1>we need to be stopped. Well, CaCu seems to fall

0:28:22.960 --> 0:28:26.119
<v Speaker 1>more on Zuckerbird's side than Musk's side on this. He

0:28:26.160 --> 0:28:29.480
<v Speaker 1>said we should always be aware of how we implement

0:28:29.520 --> 0:28:32.280
<v Speaker 1>AI and how we design it, but that we shouldn't

0:28:32.320 --> 0:28:34.960
<v Speaker 1>worry in the near term about AI going all terminator

0:28:35.000 --> 0:28:38.280
<v Speaker 1>on us and wiping us out. As we develop AI

0:28:38.320 --> 0:28:40.920
<v Speaker 1>and as it becomes more sophisticated, we can talk about

0:28:40.960 --> 0:28:43.960
<v Speaker 1>how to build in fail safes that act on the

0:28:44.040 --> 0:28:46.560
<v Speaker 1>AI as sort of a limitter so that it doesn't

0:28:46.600 --> 0:28:50.040
<v Speaker 1>cause harm. The whole field of thought is fascinating to me,

0:28:50.080 --> 0:28:52.240
<v Speaker 1>and it gets way more complicated than just put a

0:28:52.320 --> 0:28:55.040
<v Speaker 1>chip in the computer's brain so that turns off if

0:28:55.040 --> 0:28:57.640
<v Speaker 1>it thinks bad thoughts. But I'm gonna leave that whole

0:28:57.640 --> 0:29:00.240
<v Speaker 1>discussion for another show because I think that that's something

0:29:00.240 --> 0:29:02.200
<v Speaker 1>that needs to be an actual discussion. I need to

0:29:02.240 --> 0:29:04.640
<v Speaker 1>get people on the show and we can all talk

0:29:04.680 --> 0:29:07.720
<v Speaker 1>about these implications and kind of argue it all out,

0:29:07.920 --> 0:29:10.360
<v Speaker 1>not to have a fight, but rather to just kind

0:29:10.400 --> 0:29:12.360
<v Speaker 1>of see all sides of the issue and Of course,

0:29:12.640 --> 0:29:16.520
<v Speaker 1>he also brought up quantum computing, because everything at IBM

0:29:16.680 --> 0:29:20.000
<v Speaker 1>Think ten seems to be about quantum computing at some point,

0:29:20.400 --> 0:29:22.240
<v Speaker 1>and how that could be a huge help for human

0:29:22.280 --> 0:29:25.080
<v Speaker 1>efforts moving forward. Though out of all these topics, he

0:29:25.160 --> 0:29:28.320
<v Speaker 1>was really most interested in discussing neural networks and artificial intelligence,

0:29:28.360 --> 0:29:31.000
<v Speaker 1>I would say, and much of his presentation was in

0:29:31.040 --> 0:29:33.800
<v Speaker 1>fact about space travel. Dr Cocus stress that we need

0:29:33.880 --> 0:29:37.080
<v Speaker 1>healthy and robust space program, not just so that we

0:29:37.120 --> 0:29:39.520
<v Speaker 1>can learn more about our Solar system and beyond, though

0:29:39.560 --> 0:29:43.520
<v Speaker 1>that is very important, but also for the actual survival

0:29:43.720 --> 0:29:47.080
<v Speaker 1>of the human race long term, because it's only a

0:29:47.080 --> 0:29:51.400
<v Speaker 1>matter of time before we have a cataclysmic event on

0:29:51.440 --> 0:29:53.760
<v Speaker 1>the Earth, sort of like a giant meteor or a

0:29:53.800 --> 0:29:57.320
<v Speaker 1>comment that collides with the Earth. That will happen eventually.

0:29:58.120 --> 0:30:00.760
<v Speaker 1>It might not happen for thousands of years rs, but

0:30:00.840 --> 0:30:04.400
<v Speaker 1>it will happen. It's statistically a certainty that at some

0:30:04.480 --> 0:30:06.720
<v Speaker 1>point it will happen. It happened before and it will

0:30:06.720 --> 0:30:09.520
<v Speaker 1>happen again, and that could be an extinction level events.

0:30:09.520 --> 0:30:11.960
<v Speaker 1>So we need a robust space program so that we

0:30:11.960 --> 0:30:16.280
<v Speaker 1>can do stuff like detect such threats decades before they

0:30:16.280 --> 0:30:21.280
<v Speaker 1>are imminent and then take measures to deflect those threats

0:30:21.360 --> 0:30:24.000
<v Speaker 1>so that we are actually safe. It would also help

0:30:24.080 --> 0:30:26.440
<v Speaker 1>ensure the survival of humans if we spread out a bit,

0:30:26.920 --> 0:30:30.600
<v Speaker 1>if we started to colonize other planets. Spreading ourselves out

0:30:31.200 --> 0:30:35.080
<v Speaker 1>ensures the possibility that the human race survives if something

0:30:35.120 --> 0:30:38.560
<v Speaker 1>goes wrong on any one given location, and at that

0:30:38.640 --> 0:30:42.200
<v Speaker 1>point we have an insurance policy against extinction events. Dr

0:30:42.280 --> 0:30:45.080
<v Speaker 1>Cock who touched on augmented reality as well. He talked

0:30:45.120 --> 0:30:47.920
<v Speaker 1>about glasses and headsets that allow you to see information

0:30:47.960 --> 0:30:50.920
<v Speaker 1>overlaid on top of the world around you. He also

0:30:50.920 --> 0:30:53.640
<v Speaker 1>talked about voice recognition tools that let you speak directly

0:30:53.720 --> 0:30:57.080
<v Speaker 1>to this technology, calling up information you need for any

0:30:57.080 --> 0:31:00.760
<v Speaker 1>given situation. You could have specific data sets and use

0:31:01.520 --> 0:31:03.840
<v Speaker 1>those data sets with use cases. For people who have

0:31:04.080 --> 0:31:07.920
<v Speaker 1>specialized trades, for example, like electrical engineers or heart surgeons,

0:31:08.360 --> 0:31:13.360
<v Speaker 1>they could have very carefully customized data sets that aid

0:31:13.440 --> 0:31:17.320
<v Speaker 1>them in their specific occupations. They also talked about how

0:31:17.320 --> 0:31:19.280
<v Speaker 1>in the future will have contact lenses that will be

0:31:19.320 --> 0:31:22.680
<v Speaker 1>able to do this this idea of having augmented reality contacts.

0:31:22.720 --> 0:31:25.360
<v Speaker 1>You put the contact in it acts like a computer screen.

0:31:25.400 --> 0:31:28.360
<v Speaker 1>It can overlay digital information on top of the view

0:31:28.400 --> 0:31:30.800
<v Speaker 1>you have of the world around you in real time,

0:31:31.080 --> 0:31:34.600
<v Speaker 1>and it will tell you all about stuff that's around you.

0:31:34.600 --> 0:31:37.440
<v Speaker 1>You can learn about, let's say, a building that you're

0:31:37.520 --> 0:31:41.320
<v Speaker 1>looking at, or they can help explain a scientific principle

0:31:41.600 --> 0:31:44.800
<v Speaker 1>that you are encountering. Maybe you're at a talk like

0:31:44.880 --> 0:31:48.080
<v Speaker 1>the one that Dr Cocku was giving and your augmented

0:31:48.120 --> 0:31:51.680
<v Speaker 1>reality contact lens is giving you illustrations that augment that

0:31:51.800 --> 0:31:56.680
<v Speaker 1>talk and help you better understand what he's trying to express.

0:31:58.080 --> 0:32:00.600
<v Speaker 1>Or you might be at a party in your contact

0:32:00.640 --> 0:32:03.000
<v Speaker 1>lens is telling you which people at the party are important,

0:32:03.000 --> 0:32:04.960
<v Speaker 1>so you know who to suck up to. That was

0:32:04.960 --> 0:32:08.000
<v Speaker 1>actually Dr Cocku's example. He said, this will be a

0:32:08.040 --> 0:32:10.320
<v Speaker 1>great tool if you're ever at a cocktail party and

0:32:10.320 --> 0:32:12.440
<v Speaker 1>you want to know who's important so that you can

0:32:12.600 --> 0:32:15.720
<v Speaker 1>sidle up to them and kiss their butt. Um. I

0:32:15.720 --> 0:32:18.520
<v Speaker 1>thought it was a clever and funny example. Dr Cocku,

0:32:18.600 --> 0:32:21.360
<v Speaker 1>by the way, is a very funny person. Hearing him

0:32:21.600 --> 0:32:25.280
<v Speaker 1>um make jokes as he's talking about futurism was very refreshing.

0:32:25.840 --> 0:32:28.880
<v Speaker 1>Dr cock who also talked about how display technology has

0:32:28.920 --> 0:32:31.280
<v Speaker 1>become far more advanced and we have displays now that

0:32:31.320 --> 0:32:34.640
<v Speaker 1>are flexible and that there are paper thin with things

0:32:34.640 --> 0:32:37.120
<v Speaker 1>like oh lad displays, and then the future will have

0:32:37.160 --> 0:32:40.040
<v Speaker 1>digitized paper everywhere, so you could have a sheet of

0:32:40.040 --> 0:32:42.560
<v Speaker 1>paper that could be literally anything because it can be

0:32:42.560 --> 0:32:44.920
<v Speaker 1>a display. It's not really paper, it's a display that

0:32:44.960 --> 0:32:49.320
<v Speaker 1>could show any potential any potential information you need. You

0:32:49.320 --> 0:32:52.080
<v Speaker 1>can have a wall coded in digitized paper and be

0:32:52.160 --> 0:32:55.560
<v Speaker 1>digitized wallpaper, and that wall becomes a computing surface that

0:32:55.640 --> 0:32:58.640
<v Speaker 1>you can use. So let's say you've got this wallpaper display.

0:32:58.760 --> 0:33:00.520
<v Speaker 1>You could walk up to the wall all you could

0:33:00.520 --> 0:33:02.520
<v Speaker 1>talk to it. You could pull up information about any

0:33:02.560 --> 0:33:05.400
<v Speaker 1>given subject, and you could interact with an AI chatbot

0:33:05.920 --> 0:33:08.400
<v Speaker 1>to answer questions, or you help make decisions, kind of

0:33:08.400 --> 0:33:11.959
<v Speaker 1>like Jarvis in Iron Man. Dr Cock who gave an

0:33:11.960 --> 0:33:15.320
<v Speaker 1>example of someone waking up at night and they have

0:33:15.440 --> 0:33:19.800
<v Speaker 1>chest pains and they start talking to the wall, kind

0:33:19.800 --> 0:33:22.360
<v Speaker 1>of having a robo doctor right there to find out

0:33:22.680 --> 0:33:26.480
<v Speaker 1>if the symptoms they are suffering from indicate something serious

0:33:26.520 --> 0:33:29.000
<v Speaker 1>like a heart attack, and if so, the digital assistant

0:33:29.360 --> 0:33:33.320
<v Speaker 1>helps by reaching out to emergency medical personnel and getting

0:33:33.320 --> 0:33:36.960
<v Speaker 1>things ready so that that the the the person in

0:33:37.040 --> 0:33:40.200
<v Speaker 1>question can get medical attention, or if it's something more

0:33:40.280 --> 0:33:44.520
<v Speaker 1>benign like just indigestion. Dr Cock who also talked about

0:33:44.560 --> 0:33:48.760
<v Speaker 1>trying to foil aging, both through genetic approaches and through

0:33:48.800 --> 0:33:51.920
<v Speaker 1>digital ones. He talked about identifying the genes that are

0:33:51.960 --> 0:33:55.200
<v Speaker 1>responsible for aging and finding a way to deactivate them

0:33:55.480 --> 0:33:58.840
<v Speaker 1>so that the aging process stops once you reach adulthood.

0:33:59.160 --> 0:34:01.720
<v Speaker 1>From an external point of view, you would always appear

0:34:01.760 --> 0:34:05.240
<v Speaker 1>to be, say thirty years old. However, Dr Cock, who

0:34:05.320 --> 0:34:07.880
<v Speaker 1>also had not acknowledged that this wouldn't necessarily mean you

0:34:07.920 --> 0:34:10.480
<v Speaker 1>never die of old age, because your organs could continue

0:34:10.520 --> 0:34:14.680
<v Speaker 1>to deteriorate just from use over years and years and years.

0:34:14.800 --> 0:34:17.520
<v Speaker 1>You might live much longer, but eventually stuff would start

0:34:17.560 --> 0:34:19.920
<v Speaker 1>to wear out, and that would require us to find

0:34:20.000 --> 0:34:23.000
<v Speaker 1>ways to build new organs. Now we've started to do

0:34:23.040 --> 0:34:25.719
<v Speaker 1>that already, but we've got other major organs that we

0:34:25.760 --> 0:34:29.160
<v Speaker 1>haven't yet been able to build, like a liver, but

0:34:29.280 --> 0:34:33.760
<v Speaker 1>that might preserve someone's life well beyond today's lifespans, perhaps

0:34:33.760 --> 0:34:38.120
<v Speaker 1>even indefinitely. And then he mentioned digital immortality. This is

0:34:38.120 --> 0:34:41.280
<v Speaker 1>a very different approach. This is where you somehow capture

0:34:41.320 --> 0:34:43.920
<v Speaker 1>all the information that makes a person who he or

0:34:44.000 --> 0:34:46.960
<v Speaker 1>she is. Think of it like a three D scan,

0:34:47.239 --> 0:34:50.359
<v Speaker 1>except for who you are, not what you look like

0:34:51.080 --> 0:34:53.600
<v Speaker 1>all of your memories and your thoughts and your emotional

0:34:53.640 --> 0:34:56.560
<v Speaker 1>responses to anything, the way you think, the way you

0:34:56.600 --> 0:34:59.400
<v Speaker 1>come up with ideas, all of that would end up

0:34:59.440 --> 0:35:01.759
<v Speaker 1>being capt shared, and you'd end up with a simulation

0:35:02.440 --> 0:35:06.040
<v Speaker 1>of you or all practical purposes, and it would behave

0:35:06.200 --> 0:35:09.520
<v Speaker 1>as you would in any given situation, assuming that the

0:35:09.640 --> 0:35:13.120
<v Speaker 1>simulation was as close to perfect as possible. Now, would

0:35:13.160 --> 0:35:16.799
<v Speaker 1>you then say that that construct is in fact you, Well,

0:35:16.840 --> 0:35:19.600
<v Speaker 1>if you think of yourself in terms of your fleshy existence, no,

0:35:19.920 --> 0:35:22.440
<v Speaker 1>you wouldn't. The version that you would be looking at

0:35:22.920 --> 0:35:26.080
<v Speaker 1>would be a simulation, and you, however, would eventually age

0:35:26.120 --> 0:35:29.120
<v Speaker 1>and die. But if you think of yourself as your

0:35:29.160 --> 0:35:33.560
<v Speaker 1>collection of experiences and your thoughts and your emotions, then

0:35:33.640 --> 0:35:37.080
<v Speaker 1>maybe you might say the simulation is you, but it's

0:35:37.080 --> 0:35:40.840
<v Speaker 1>another instance of you. Now, that doesn't solve the problem

0:35:41.000 --> 0:35:43.839
<v Speaker 1>that your own experience of being you would someday come

0:35:43.880 --> 0:35:46.840
<v Speaker 1>to an end, and a simulated jerk face version of

0:35:46.880 --> 0:35:50.000
<v Speaker 1>you would keep on going as if no one cared,

0:35:50.280 --> 0:35:53.960
<v Speaker 1>as long as no one unplugged them jerk face. Then

0:35:54.080 --> 0:35:58.120
<v Speaker 1>Dr Cocu said something I found really fascinating, and I

0:35:58.160 --> 0:36:00.879
<v Speaker 1>hadn't really considered before He said that if you could

0:36:00.880 --> 0:36:05.640
<v Speaker 1>digitize a person, boil their essence down into pure information,

0:36:06.160 --> 0:36:09.640
<v Speaker 1>and then you encode that information using a laser beam,

0:36:09.960 --> 0:36:12.880
<v Speaker 1>you could fire that laser beam at distant targets like

0:36:13.000 --> 0:36:16.080
<v Speaker 1>other planets in our Solar system, or even beyond. Let's

0:36:16.080 --> 0:36:20.160
<v Speaker 1>say you shoot it toward Alpha Centauri. Within four years,

0:36:20.200 --> 0:36:24.520
<v Speaker 1>you would get there. You could have minds travel vast

0:36:24.840 --> 0:36:28.719
<v Speaker 1>distances at the speed of light. Matter can't travel at

0:36:28.760 --> 0:36:31.879
<v Speaker 1>the speed of light, but information can. Of course, I'm

0:36:31.880 --> 0:36:34.680
<v Speaker 1>not sure what you could do once you've got to

0:36:34.719 --> 0:36:37.400
<v Speaker 1>where you were going, because if you're information encoded on

0:36:37.440 --> 0:36:40.480
<v Speaker 1>a medium, I can't see any way you could meaningfully

0:36:40.600 --> 0:36:43.880
<v Speaker 1>do anything at all or perceive anything. You would just

0:36:43.960 --> 0:36:46.640
<v Speaker 1>have just information shooting out there, kind of like how

0:36:46.760 --> 0:36:50.160
<v Speaker 1>radio waves can radiate out into space. That doesn't necessarily

0:36:50.160 --> 0:36:52.959
<v Speaker 1>mean we can do anything with them. A program isn't

0:36:53.080 --> 0:36:56.279
<v Speaker 1>running if you don't execute it right, Like if you

0:36:56.320 --> 0:36:59.600
<v Speaker 1>have a computer game on a disk. Imagine an old

0:36:59.640 --> 0:37:02.120
<v Speaker 1>disc you've got, you put it in your computer, and

0:37:02.160 --> 0:37:04.480
<v Speaker 1>you don't run the program. You just put it in

0:37:04.480 --> 0:37:07.399
<v Speaker 1>the computer, but the computer is not engaging the disk

0:37:07.440 --> 0:37:09.520
<v Speaker 1>at all. It's not like the game is actually running

0:37:09.560 --> 0:37:11.640
<v Speaker 1>on your machine. It's not like it's making any sort

0:37:11.680 --> 0:37:15.399
<v Speaker 1>of activity, but still, this is an intriguing idea. It

0:37:15.440 --> 0:37:18.319
<v Speaker 1>could be a new form of space exploration, assuming we

0:37:18.360 --> 0:37:21.160
<v Speaker 1>figure out how to make that information useful, so that

0:37:21.239 --> 0:37:24.480
<v Speaker 1>can either communicate back to us about what it has discovered,

0:37:24.800 --> 0:37:27.440
<v Speaker 1>or it can somehow go about and take actions of

0:37:27.480 --> 0:37:30.680
<v Speaker 1>its own across the universe. I just don't know how

0:37:30.680 --> 0:37:34.480
<v Speaker 1>that would work. Dr Kko's final section was about brain

0:37:34.560 --> 0:37:37.759
<v Speaker 1>computer interfaces. Now, these are the technologies that allow us

0:37:37.760 --> 0:37:41.880
<v Speaker 1>to communicate directly with technologies through thought. It's kind of

0:37:41.920 --> 0:37:45.799
<v Speaker 1>a technological telepathy. It's still a very early field, but

0:37:45.840 --> 0:37:48.600
<v Speaker 1>there are examples out there and have been for a

0:37:48.600 --> 0:37:52.439
<v Speaker 1>decade or more. These are not perfect methods, and each

0:37:52.480 --> 0:37:56.319
<v Speaker 1>method has advantages and disadvantages. The best way to get

0:37:56.440 --> 0:38:00.200
<v Speaker 1>high resolution data from a person that is consistently reliable,

0:38:00.360 --> 0:38:03.200
<v Speaker 1>or at least more reliable than the alternatives, is to

0:38:03.280 --> 0:38:08.359
<v Speaker 1>embed sensors directly onto that person's brain. So it requires

0:38:08.520 --> 0:38:11.600
<v Speaker 1>brain surgery. Then you have the problem of figuring out

0:38:11.600 --> 0:38:14.680
<v Speaker 1>how do you send signals from the sensors you've implanted

0:38:14.680 --> 0:38:17.720
<v Speaker 1>in the brain to the target technologies. Now, you could

0:38:18.400 --> 0:38:22.560
<v Speaker 1>include wires or an antenna that protrudes from the brain

0:38:22.680 --> 0:38:26.200
<v Speaker 1>through the skull. But this also presents a problem because

0:38:26.239 --> 0:38:29.280
<v Speaker 1>you've created the potential for contaminants to infect the brain.

0:38:29.480 --> 0:38:33.320
<v Speaker 1>Like anytime you've got something that's breaking that blood brain barrier,

0:38:33.640 --> 0:38:36.920
<v Speaker 1>that's bad news. So you have to be super careful

0:38:36.960 --> 0:38:39.239
<v Speaker 1>with this. And the skull is pretty thick. It's thick

0:38:39.360 --> 0:38:42.000
<v Speaker 1>enough to make it tricky to send signals through the skull.

0:38:42.120 --> 0:38:46.239
<v Speaker 1>So a wireless solution, while it might be possible, is

0:38:46.320 --> 0:38:50.040
<v Speaker 1>not ideal. It might end up being hard to detect

0:38:50.280 --> 0:38:54.160
<v Speaker 1>legitimate signals. Or you could go the non invasive route

0:38:54.239 --> 0:38:56.440
<v Speaker 1>and you could use an e G headset to pick

0:38:56.520 --> 0:38:59.920
<v Speaker 1>up brain waves. Now those don't require surgery, but sometimes

0:39:00.080 --> 0:39:03.360
<v Speaker 1>are not terribly accurate. They can pick up noise that

0:39:03.480 --> 0:39:07.040
<v Speaker 1>looks like brain waves, but it's actually just interference. Uh,

0:39:07.120 --> 0:39:09.840
<v Speaker 1>they can be false positives, or it can fail to

0:39:10.000 --> 0:39:13.960
<v Speaker 1>register legitimate commands as something that's meaningful. So you might

0:39:14.000 --> 0:39:18.920
<v Speaker 1>be thinking, now type the word dog, but it's nothing's

0:39:18.960 --> 0:39:21.400
<v Speaker 1>happening because it hasn't picked it up as a legitimate command.

0:39:22.120 --> 0:39:24.520
<v Speaker 1>So this doesn't require a surgeon to operate on you,

0:39:24.560 --> 0:39:26.600
<v Speaker 1>but it also does not give you as accurate a

0:39:26.640 --> 0:39:30.640
<v Speaker 1>response as an intercranial approach would. However, we do have

0:39:30.719 --> 0:39:33.800
<v Speaker 1>some examples of these technologies that allow people who otherwise

0:39:33.840 --> 0:39:37.719
<v Speaker 1>couldn't control things with their bodies to be able to

0:39:37.719 --> 0:39:40.359
<v Speaker 1>have control over things. And a lot of it comes

0:39:40.360 --> 0:39:44.279
<v Speaker 1>into communication, right, using a computer interface to communicate with

0:39:44.360 --> 0:39:47.800
<v Speaker 1>other people, you think, and then the computer either speaks

0:39:47.920 --> 0:39:50.960
<v Speaker 1>or types things out on your behalf and it opens

0:39:51.000 --> 0:39:53.160
<v Speaker 1>up a channel of communication where otherwise you would be

0:39:53.200 --> 0:39:57.000
<v Speaker 1>unable to do so. Or we can pair that type

0:39:57.040 --> 0:40:00.439
<v Speaker 1>of technology with something like an exoskeleton, and of someone

0:40:00.440 --> 0:40:03.799
<v Speaker 1>who has lost mobility the chance to regain it. They

0:40:03.920 --> 0:40:08.160
<v Speaker 1>can use their mind to send signals to the exoskeleton

0:40:08.280 --> 0:40:11.279
<v Speaker 1>and use that to move them around. One day, we

0:40:11.360 --> 0:40:14.920
<v Speaker 1>might extend this so that we have robotic bodies that

0:40:15.000 --> 0:40:18.640
<v Speaker 1>we can control remotely using our minds, giving us telepresence

0:40:18.920 --> 0:40:22.920
<v Speaker 1>into distant locations. Of course, the further out we go,

0:40:23.080 --> 0:40:25.200
<v Speaker 1>the more we'll have to deal with the limitation of

0:40:25.239 --> 0:40:28.160
<v Speaker 1>remote control. Because even if we had a perfect system

0:40:28.280 --> 0:40:31.440
<v Speaker 1>that let us communicate with a robot that's light years

0:40:31.480 --> 0:40:33.920
<v Speaker 1>away from us, so we can send signals to it

0:40:33.960 --> 0:40:36.480
<v Speaker 1>and we can receive signals back from it, somehow there

0:40:36.480 --> 0:40:40.120
<v Speaker 1>would still be tremendous lag because information is still only

0:40:40.120 --> 0:40:42.439
<v Speaker 1>going to travel at the speed of light. So if

0:40:42.440 --> 0:40:44.640
<v Speaker 1>a robot is light years away, that means it literally

0:40:44.640 --> 0:40:47.640
<v Speaker 1>takes years for a command you send to be received

0:40:47.640 --> 0:40:50.759
<v Speaker 1>by the robot, and years again for the robot to

0:40:50.840 --> 0:40:53.960
<v Speaker 1>send the results back to you. So it would be

0:40:54.000 --> 0:40:57.759
<v Speaker 1>like the longest game of mail chess, like where you're

0:40:57.800 --> 0:41:00.600
<v Speaker 1>mailing your move back to your opponent and over again,

0:41:00.640 --> 0:41:03.920
<v Speaker 1>but still super cool. Dr Cocku ended his talk by

0:41:03.920 --> 0:41:08.239
<v Speaker 1>reminding us that without pursuit of these new forms of technologies,

0:41:08.280 --> 0:41:11.960
<v Speaker 1>we could find ourselves clinging to diminishing returns with classical computing,

0:41:12.120 --> 0:41:14.840
<v Speaker 1>and that was a really interesting presentation. I do have

0:41:14.920 --> 0:41:17.600
<v Speaker 1>one more speaker to talk about, but first let's take

0:41:17.640 --> 0:41:27.919
<v Speaker 1>another quick break to thank our sponsor. The last person

0:41:28.000 --> 0:41:29.520
<v Speaker 1>I want to talk about in this episode is a

0:41:29.560 --> 0:41:32.840
<v Speaker 1>remarkable young man and his name is Tonme boks Sheet.

0:41:33.200 --> 0:41:36.279
<v Speaker 1>He's a programmer. He's an expert on deep learning and

0:41:36.400 --> 0:41:42.680
<v Speaker 1>artificial intelligence, and he's fourteen freaking years old. Box She's

0:41:42.719 --> 0:41:45.560
<v Speaker 1>father is a computer programmer, and ten May began learning

0:41:45.560 --> 0:41:48.319
<v Speaker 1>about coding and programming when he was just five years old,

0:41:48.360 --> 0:41:51.400
<v Speaker 1>and he loved it, and so he studied it intently.

0:41:51.680 --> 0:41:54.120
<v Speaker 1>When he was seven, he started up a YouTube channel

0:41:54.160 --> 0:41:57.320
<v Speaker 1>and he began to upload videos about how to code

0:41:57.719 --> 0:42:00.759
<v Speaker 1>and develop for the web. He started to developing for

0:42:00.880 --> 0:42:04.120
<v Speaker 1>iOS when he was eight, and Apple published his first

0:42:04.160 --> 0:42:07.040
<v Speaker 1>app when he was nine. That was an app, by

0:42:07.080 --> 0:42:10.960
<v Speaker 1>the way, that taught multiplication to kids. When he was eleven,

0:42:11.480 --> 0:42:14.640
<v Speaker 1>he caught the attention of IBM. See box She saw

0:42:14.680 --> 0:42:17.719
<v Speaker 1>a video about IBM Watson and how that platform was

0:42:17.719 --> 0:42:21.279
<v Speaker 1>advancing artificial intelligence, and he found it absolutely fascinating. So

0:42:21.320 --> 0:42:23.799
<v Speaker 1>he also started to work with an alpha build of

0:42:23.840 --> 0:42:26.520
<v Speaker 1>a tool that IBM had developed that was meant to

0:42:26.520 --> 0:42:30.960
<v Speaker 1>convert documents from one format into other formats. Box She

0:42:31.080 --> 0:42:33.920
<v Speaker 1>discovered a bug in the code, and he sent a

0:42:33.920 --> 0:42:36.440
<v Speaker 1>bug report to the development team to let them know

0:42:36.520 --> 0:42:39.680
<v Speaker 1>about it. Some IBM developers ended up reaching out to

0:42:39.760 --> 0:42:42.919
<v Speaker 1>box She in response, and a new partnership began to form.

0:42:43.600 --> 0:42:46.480
<v Speaker 1>Box She, by the way, isn't truly an IBM partner

0:42:46.680 --> 0:42:49.600
<v Speaker 1>because he does not get compensated. He doesn't get paid

0:42:49.640 --> 0:42:51.880
<v Speaker 1>for this, but he does work with IBM on a

0:42:51.920 --> 0:42:56.480
<v Speaker 1>lot of projects. Right now. Uh he's creating novel approaches

0:42:56.520 --> 0:42:59.880
<v Speaker 1>to computing and he's finding new ways to leverage data,

0:43:00.200 --> 0:43:04.200
<v Speaker 1>and since his communications with IBM, he has ended up

0:43:04.200 --> 0:43:06.840
<v Speaker 1>going on tours around the world to talk about the

0:43:06.880 --> 0:43:10.200
<v Speaker 1>next advancements and data processing and data analysis, as well

0:43:10.239 --> 0:43:14.439
<v Speaker 1>as artificial intelligence and brain computer interfaces and the work

0:43:14.440 --> 0:43:17.880
<v Speaker 1>he's doing in those fields. He decided to talk about

0:43:17.960 --> 0:43:20.319
<v Speaker 1>three of the projects that he was interested in, all

0:43:20.400 --> 0:43:23.560
<v Speaker 1>three relating to healthcare, and he said that healthcare is

0:43:23.560 --> 0:43:26.920
<v Speaker 1>one of those fields where deep learning and big data

0:43:27.080 --> 0:43:30.719
<v Speaker 1>are really important because there's tons and tons and tons

0:43:30.800 --> 0:43:35.080
<v Speaker 1>of information in the healthcare sphere and it's useful information

0:43:35.360 --> 0:43:39.759
<v Speaker 1>in theory. In practice, however, it can often not be useful. Now,

0:43:39.760 --> 0:43:41.799
<v Speaker 1>the reason I say that is, imagine that you are

0:43:41.840 --> 0:43:45.040
<v Speaker 1>a doctor. Some of you probably are doctors. For the

0:43:45.080 --> 0:43:47.319
<v Speaker 1>rest of you. Imagine that you are a doctor, and

0:43:47.400 --> 0:43:50.080
<v Speaker 1>you're a good doctor. You're you're you're good at what

0:43:50.120 --> 0:43:53.680
<v Speaker 1>you do. You understand your field. However, there are always

0:43:53.719 --> 0:43:59.400
<v Speaker 1>more advancements being made in the pioneering edge of medicine.

0:43:59.800 --> 0:44:02.480
<v Speaker 1>They you may or may not be familiar with. So

0:44:02.640 --> 0:44:05.520
<v Speaker 1>part of your job isn't just treating your patients. It's

0:44:05.680 --> 0:44:09.759
<v Speaker 1>learning more about developments in medicine. So you have to

0:44:09.800 --> 0:44:12.040
<v Speaker 1>go and seek out that information. You have to learn

0:44:12.080 --> 0:44:14.319
<v Speaker 1>about it, you have to comprehend it. Then you have

0:44:14.360 --> 0:44:16.799
<v Speaker 1>to put it into practice if it makes sense as

0:44:17.040 --> 0:44:21.160
<v Speaker 1>as your role as doctor. And while you're doing this,

0:44:21.239 --> 0:44:24.080
<v Speaker 1>while you're learning about the latest and greatest stuff, pioneers

0:44:24.080 --> 0:44:28.080
<v Speaker 1>are finding even more breakthroughs in medicine. And you have

0:44:28.120 --> 0:44:30.640
<v Speaker 1>to keep doing this. You have to keep learning. It's

0:44:30.640 --> 0:44:34.880
<v Speaker 1>a never ending process. And if you are a doctor

0:44:34.960 --> 0:44:38.239
<v Speaker 1>working in a in a in a large city that

0:44:38.280 --> 0:44:41.719
<v Speaker 1>has access to a lot of uh like cutting edge

0:44:41.760 --> 0:44:46.280
<v Speaker 1>research centers, then you have those assets at your disposal.

0:44:46.360 --> 0:44:49.520
<v Speaker 1>You might be able to reference or refer rather a

0:44:49.560 --> 0:44:53.040
<v Speaker 1>patient to one of those specialists who can then use

0:44:53.120 --> 0:44:56.400
<v Speaker 1>their their expertise and the latest and greatest information to

0:44:56.480 --> 0:44:59.719
<v Speaker 1>help that patient. But the further out you are from

0:44:59.760 --> 0:45:03.680
<v Speaker 1>those centers, the less of that support you're going to get,

0:45:03.800 --> 0:45:05.520
<v Speaker 1>and you'll have to do more and more of this

0:45:05.640 --> 0:45:07.480
<v Speaker 1>on your own, which leaves it up to you to

0:45:07.600 --> 0:45:11.359
<v Speaker 1>learn everything and that is just not humanly possible. That's

0:45:11.400 --> 0:45:15.520
<v Speaker 1>where deep learning and big data come in. So with

0:45:15.600 --> 0:45:19.160
<v Speaker 1>deep learning, you can design computer algorithms that are looking

0:45:19.440 --> 0:45:25.000
<v Speaker 1>deeply into the results of any given scenario. So let's

0:45:25.200 --> 0:45:29.560
<v Speaker 1>take drugs as a as a as A as an example,

0:45:30.320 --> 0:45:34.000
<v Speaker 1>clinical trials are great. Clinical trials are how we determine

0:45:34.120 --> 0:45:38.279
<v Speaker 1>whether or not a drug is effective, whether or not

0:45:38.560 --> 0:45:44.880
<v Speaker 1>it poses the potential to give patients UH adverse side effects.

0:45:45.320 --> 0:45:47.920
<v Speaker 1>These are really important things, and all drugs have to

0:45:47.960 --> 0:45:52.000
<v Speaker 1>go through lengthy clinical trials before they can be used

0:45:52.040 --> 0:45:58.560
<v Speaker 1>in medical applications. However, clinical trials are not perfect because

0:45:58.800 --> 0:46:04.000
<v Speaker 1>it is impossible to have a truly representative population of

0:46:04.280 --> 0:46:07.880
<v Speaker 1>volunteers in these clinical trials. You're never going to get

0:46:08.640 --> 0:46:17.520
<v Speaker 1>a full demographically representative population of people testing out your drug. UH. Eventually,

0:46:17.719 --> 0:46:22.560
<v Speaker 1>you're going to get approval. Let's say that the drug

0:46:22.600 --> 0:46:28.120
<v Speaker 1>is effective and doesn't show any UH implications of truly

0:46:28.160 --> 0:46:30.719
<v Speaker 1>adverse sight effects. You get it approved, it goes out

0:46:30.760 --> 0:46:33.000
<v Speaker 1>into the market. Suddenly, it is now out in the

0:46:33.040 --> 0:46:36.840
<v Speaker 1>world where more than seven billion people live. And because

0:46:36.880 --> 0:46:39.720
<v Speaker 1>more than seven billion people live there, they're all sorts

0:46:39.719 --> 0:46:44.520
<v Speaker 1>of different body types, body chemistryes, potential drug interactions going

0:46:44.520 --> 0:46:47.200
<v Speaker 1>on because people could be taking other drugs that could

0:46:47.840 --> 0:46:51.720
<v Speaker 1>change the way your new drug interacts with their bodies.

0:46:52.320 --> 0:46:56.960
<v Speaker 1>And suddenly you've got things that are happening where you

0:46:57.280 --> 0:47:00.120
<v Speaker 1>aren't sure if your drug is responsible for maybe some

0:47:00.160 --> 0:47:02.600
<v Speaker 1>adverse side effects or not. In fact, you can't even

0:47:02.600 --> 0:47:05.080
<v Speaker 1>really be sure in clinical trials. If you observe it

0:47:05.160 --> 0:47:07.600
<v Speaker 1>frequently enough, you could say, well, chances are the drug

0:47:07.680 --> 0:47:10.479
<v Speaker 1>is causing these side effects, but you can't just say

0:47:10.480 --> 0:47:14.520
<v Speaker 1>that based upon one instance because there are too many

0:47:14.600 --> 0:47:17.800
<v Speaker 1>unknown variables. It's like that way with humans. We humans

0:47:17.800 --> 0:47:21.040
<v Speaker 1>are complicated people. And maybe that the person who was

0:47:21.040 --> 0:47:23.400
<v Speaker 1>in the clinical trial had taken some aspirin that morning

0:47:23.440 --> 0:47:26.319
<v Speaker 1>and the aspirin interacted with the drug in a way

0:47:26.719 --> 0:47:30.680
<v Speaker 1>that was unexpected, and thus the person in the trial

0:47:30.760 --> 0:47:34.160
<v Speaker 1>had an adverse side effect. But if they hadn't taken

0:47:34.200 --> 0:47:36.279
<v Speaker 1>the aspirin, they would have been fine. Like they're They're

0:47:36.280 --> 0:47:40.040
<v Speaker 1>all these unknowns that can take place during clinical trials.

0:47:40.120 --> 0:47:43.640
<v Speaker 1>So what Bakshi was arguing is that if you use

0:47:43.719 --> 0:47:48.360
<v Speaker 1>deep learning, you can look across the results of real

0:47:48.760 --> 0:47:52.879
<v Speaker 1>life cases of people taking drugs and reporting any sort

0:47:52.880 --> 0:47:55.480
<v Speaker 1>of side effects they might have felt, and used that

0:47:55.600 --> 0:47:58.200
<v Speaker 1>to start to draw more conclusions. You could even do

0:47:58.239 --> 0:48:00.680
<v Speaker 1>this by looking at social media. So in other words,

0:48:00.719 --> 0:48:04.880
<v Speaker 1>you could look at instances of a drug being mentioned

0:48:04.920 --> 0:48:09.480
<v Speaker 1>in social media and looking at any possible descriptions of

0:48:09.520 --> 0:48:13.120
<v Speaker 1>how a person felt after they took that drug and

0:48:13.280 --> 0:48:17.839
<v Speaker 1>mine the entire sphere of social media for instances like

0:48:17.920 --> 0:48:20.640
<v Speaker 1>that and add that into a database. Now, this would

0:48:20.640 --> 0:48:23.120
<v Speaker 1>be way too much for any human to handle, but

0:48:23.160 --> 0:48:26.000
<v Speaker 1>if you put it into the realm of computers, they

0:48:26.000 --> 0:48:29.600
<v Speaker 1>could look around, look for data points, try and see

0:48:29.800 --> 0:48:31.799
<v Speaker 1>how many of those data points there are. Is there

0:48:32.000 --> 0:48:35.760
<v Speaker 1>a significant number? Is there enough to suggest that perhaps

0:48:35.760 --> 0:48:38.560
<v Speaker 1>there is something actually going on here, or is it

0:48:39.040 --> 0:48:44.120
<v Speaker 1>an outlier that isn't indicative of anything meaningful. Computers can

0:48:44.160 --> 0:48:46.840
<v Speaker 1>help do this, and that can help people start to

0:48:47.840 --> 0:48:51.320
<v Speaker 1>consider what drugs they want to prescribe to patients. People

0:48:51.360 --> 0:48:54.480
<v Speaker 1>being doctors, So a doctor could look at their patient

0:48:54.680 --> 0:48:57.120
<v Speaker 1>and let's say the doctor she's looking at her patients,

0:48:57.160 --> 0:49:01.160
<v Speaker 1>she says, well, I want I want to prescribe medication

0:49:01.200 --> 0:49:04.320
<v Speaker 1>to treat you, and I've got a couple of different options.

0:49:04.480 --> 0:49:09.480
<v Speaker 1>So based upon who you are, your body type, your

0:49:09.520 --> 0:49:13.200
<v Speaker 1>body chemistry, the other medications you might be on, I'm

0:49:13.239 --> 0:49:16.560
<v Speaker 1>going to take a look at this information that has

0:49:16.600 --> 0:49:23.320
<v Speaker 1>been curated by algorithms that have mined this huge data

0:49:23.360 --> 0:49:26.439
<v Speaker 1>set and brought back all these results, and based upon

0:49:26.440 --> 0:49:31.000
<v Speaker 1>this information, I am more likely to prescribe drug b

0:49:31.640 --> 0:49:35.680
<v Speaker 1>to you because too, from what I see here, it

0:49:35.760 --> 0:49:38.879
<v Speaker 1>is the least likely to cause any really bad side

0:49:38.920 --> 0:49:42.280
<v Speaker 1>effects and the most likely to be efficacious in treating

0:49:42.480 --> 0:49:47.120
<v Speaker 1>your disease or whatever. And that was one of the

0:49:47.160 --> 0:49:51.720
<v Speaker 1>three ways that tom may backshe was citing as being

0:49:51.840 --> 0:49:55.719
<v Speaker 1>an important way to use dev learning really just kind

0:49:55.719 --> 0:50:02.360
<v Speaker 1>of finding out ways to avoid having negative drug interactions.

0:50:02.880 --> 0:50:07.600
<v Speaker 1>This idea of leveraging information that is out there that

0:50:07.640 --> 0:50:11.560
<v Speaker 1>otherwise is you know, it's it's useful, but it's unstructured

0:50:11.760 --> 0:50:15.280
<v Speaker 1>and it's not being harnessed in any meaningful way. Changing

0:50:15.320 --> 0:50:18.720
<v Speaker 1>that by using a neural network and using open source

0:50:18.800 --> 0:50:23.920
<v Speaker 1>databases like FDA Drug Adverse Database and social media to

0:50:23.920 --> 0:50:27.600
<v Speaker 1>try and predict if any one particular person will suffer

0:50:27.640 --> 0:50:32.520
<v Speaker 1>negative events from any particular drug. I found that really fascinating.

0:50:33.120 --> 0:50:37.240
<v Speaker 1>The idea of not just using the official databases, the

0:50:37.400 --> 0:50:42.200
<v Speaker 1>medical resources that have accumulated over the course of decades

0:50:42.360 --> 0:50:48.359
<v Speaker 1>of work, but also the more anecdotal evidence and I

0:50:48.480 --> 0:50:50.680
<v Speaker 1>hesitate to use those two words together, but the more

0:50:50.719 --> 0:50:54.600
<v Speaker 1>anecdotal accounts, let's say, of people who are using those drugs,

0:50:54.640 --> 0:50:58.279
<v Speaker 1>who are reporting, you know, just casually on what it

0:50:58.400 --> 0:51:02.080
<v Speaker 1>is they're experiencing and using that information to help kind

0:51:02.080 --> 0:51:05.640
<v Speaker 1>of create a much larger, more informal clinical trial in

0:51:05.680 --> 0:51:10.000
<v Speaker 1>the real world that can end up having real impact

0:51:10.320 --> 0:51:12.879
<v Speaker 1>on the future of how that those particular drugs are

0:51:12.920 --> 0:51:15.239
<v Speaker 1>are used in the future. I used the future a

0:51:15.239 --> 0:51:17.399
<v Speaker 1>couple of times there, but that's just because I'm thinking

0:51:17.400 --> 0:51:21.319
<v Speaker 1>about it so much. Then bok she transitioned to talk

0:51:21.360 --> 0:51:24.160
<v Speaker 1>about another project he's been working on that is called

0:51:24.280 --> 0:51:28.400
<v Speaker 1>the Cognitive Story, and this is a story about augmenting

0:51:28.400 --> 0:51:31.640
<v Speaker 1>people's lives with the power of cognitive computing and artificial

0:51:31.680 --> 0:51:34.640
<v Speaker 1>intelligence and brain computer interfaces. So this kind of ties

0:51:34.680 --> 0:51:38.600
<v Speaker 1>into what Dr Mitchiokaku had talked about earlier during the conference.

0:51:39.200 --> 0:51:43.520
<v Speaker 1>Uh In this in this particular case, uh Tom may Bak,

0:51:43.560 --> 0:51:47.960
<v Speaker 1>she was talking about a woman named Boo, and the

0:51:48.200 --> 0:51:54.239
<v Speaker 1>woman has Rhetz syndrome, which has made her almost completely

0:51:54.280 --> 0:51:59.680
<v Speaker 1>non communicative. She's quadriplegic and almost incapable of communicating except

0:51:59.680 --> 0:52:02.799
<v Speaker 1>to the those who know her best, who can interpret

0:52:03.400 --> 0:52:07.080
<v Speaker 1>what Boo is trying to communicate, and they can therefore

0:52:08.640 --> 0:52:12.640
<v Speaker 1>help her throughout the day. But anyone who doesn't know

0:52:12.760 --> 0:52:19.640
<v Speaker 1>Boo with that level of familiarity is not going to

0:52:19.640 --> 0:52:22.440
<v Speaker 1>be able to understand what she's trying to communicate at

0:52:22.440 --> 0:52:26.440
<v Speaker 1>any given time. And so Bakshi and the team he's

0:52:26.480 --> 0:52:29.640
<v Speaker 1>working with have been trying to develop a tool that

0:52:29.680 --> 0:52:33.840
<v Speaker 1>allows Boo to communicate with other people, and it requires

0:52:33.880 --> 0:52:36.920
<v Speaker 1>several steps. The first of those steps is finding a

0:52:36.960 --> 0:52:41.600
<v Speaker 1>way to interpret booze brain waves so that Boo doesn't

0:52:41.640 --> 0:52:46.760
<v Speaker 1>have to struggle, she just thinks, and then those thoughts

0:52:46.760 --> 0:52:50.680
<v Speaker 1>can be communicated to the outside world. Um and so

0:52:50.800 --> 0:52:53.560
<v Speaker 1>that would require doing what I had talked about previously,

0:52:53.600 --> 0:52:56.120
<v Speaker 1>finding that brain computer interface. In this case, they went

0:52:56.200 --> 0:52:59.200
<v Speaker 1>with the e G model, the noninvasive model. They had

0:52:59.200 --> 0:53:03.359
<v Speaker 1>two three D print a specific headset for Boo so

0:53:03.440 --> 0:53:07.360
<v Speaker 1>that it could comfortably sit on her head. Rett syndrome

0:53:07.360 --> 0:53:10.600
<v Speaker 1>means that she's very, very sensitive, and you can't have

0:53:10.719 --> 0:53:13.840
<v Speaker 1>something heavy or bulky on her because it would be

0:53:14.160 --> 0:53:16.719
<v Speaker 1>caused so much discomfort that it would not be of

0:53:16.760 --> 0:53:19.960
<v Speaker 1>any real help. It would actually it would hurt her physically.

0:53:20.280 --> 0:53:23.399
<v Speaker 1>And then then you have to train the technology. It's

0:53:23.400 --> 0:53:25.840
<v Speaker 1>not just enough that you are able to detect brain waves.

0:53:26.560 --> 0:53:30.200
<v Speaker 1>It's not like all humans have brain waves that follow

0:53:30.280 --> 0:53:33.399
<v Speaker 1>the exact same patterns. And therefore, if I think yes

0:53:33.520 --> 0:53:36.880
<v Speaker 1>or no, and you think yes or no, it's exactly

0:53:36.920 --> 0:53:39.279
<v Speaker 1>the same as it in my brain as it is

0:53:39.320 --> 0:53:41.880
<v Speaker 1>in your brain. So they have to train it with

0:53:41.960 --> 0:53:44.960
<v Speaker 1>booze own brain waves. And that also means they have

0:53:45.000 --> 0:53:50.000
<v Speaker 1>to rely heavily upon Booze Mother for the interpretation of

0:53:50.080 --> 0:53:55.520
<v Speaker 1>Booze communications, because again, without knowing Boo in this level

0:53:55.520 --> 0:54:01.000
<v Speaker 1>of familiarity, they can't know what any particular brain wave represents.

0:54:01.000 --> 0:54:03.600
<v Speaker 1>They can detect the brain waves, but detecting it is

0:54:03.600 --> 0:54:06.520
<v Speaker 1>one thing. Knowing what it means is something else. So

0:54:06.840 --> 0:54:10.120
<v Speaker 1>they work with Booze Mother, who has been given the

0:54:10.120 --> 0:54:14.719
<v Speaker 1>title of intimate interpreter, to interpret what those brain waves mean.

0:54:15.360 --> 0:54:18.880
<v Speaker 1>And right right now, they're able to kind of go

0:54:18.960 --> 0:54:21.400
<v Speaker 1>with a binary approach, a yes or no, but they

0:54:21.440 --> 0:54:25.120
<v Speaker 1>want to extend that so that Boo can communicate more

0:54:25.200 --> 0:54:28.480
<v Speaker 1>complicated thoughts and not just respond to a series of

0:54:28.560 --> 0:54:33.520
<v Speaker 1>yes no questions. To narrow down what it is she wants. Um,

0:54:33.560 --> 0:54:37.240
<v Speaker 1>this is going to require lots and lots of data gathering.

0:54:37.280 --> 0:54:39.959
<v Speaker 1>You have to do a lot of sessions with Boo

0:54:40.040 --> 0:54:45.239
<v Speaker 1>wearing the e G headset, thinking things, measuring them, interpreting

0:54:45.320 --> 0:54:49.200
<v Speaker 1>what those those measurements mean, and then mapping that to

0:54:50.120 --> 0:54:53.919
<v Speaker 1>the system. They want to use neural networks and deep

0:54:54.040 --> 0:54:59.719
<v Speaker 1>learning to detect which of those signals represent actual commands,

0:55:00.080 --> 0:55:04.360
<v Speaker 1>which ones might be noise or interference or just a

0:55:04.440 --> 0:55:08.120
<v Speaker 1>random little blip from the brain. And you have to

0:55:08.160 --> 0:55:11.440
<v Speaker 1>differentiate those if you want it to be a meaningful experience,

0:55:11.480 --> 0:55:15.960
<v Speaker 1>if you want to make sure that the thing you

0:55:16.000 --> 0:55:19.960
<v Speaker 1>are recording is in fact an actual command and not

0:55:20.160 --> 0:55:26.400
<v Speaker 1>just random information, because otherwise, obviously you would be acting upon, uh,

0:55:26.600 --> 0:55:29.799
<v Speaker 1>just blips like blips that don't that don't indicate any

0:55:29.840 --> 0:55:35.160
<v Speaker 1>actual request or question or response. You have to cut

0:55:35.160 --> 0:55:39.000
<v Speaker 1>out all that noise. Um Box. She also gave us

0:55:39.000 --> 0:55:41.960
<v Speaker 1>an example, showed us a black screen and on that

0:55:42.000 --> 0:55:45.279
<v Speaker 1>black screen, occasionally a red square would appear, and Box

0:55:45.400 --> 0:55:48.040
<v Speaker 1>she said, well, when that black screen is black and

0:55:48.040 --> 0:55:50.520
<v Speaker 1>you're just concentrating on it, eventually your mind kind of

0:55:50.560 --> 0:55:54.040
<v Speaker 1>goes at rest and your alpha waves will start to spike,

0:55:54.440 --> 0:55:57.080
<v Speaker 1>because that's those are the brain waves that are associated

0:55:57.120 --> 0:56:01.640
<v Speaker 1>with relaxation and uh, you know, just just relaxed focus.

0:56:02.200 --> 0:56:04.880
<v Speaker 1>And then when the red square appears, you would expect

0:56:04.920 --> 0:56:10.279
<v Speaker 1>to see those alpha waves drop because you were shown something,

0:56:10.280 --> 0:56:13.600
<v Speaker 1>you were stimulated by the red square you. You had

0:56:13.640 --> 0:56:16.399
<v Speaker 1>stimuli there and your brain reacted and box. She said.

0:56:17.320 --> 0:56:20.080
<v Speaker 1>The thing is sometimes you'll get spikes even when there's

0:56:20.120 --> 0:56:22.600
<v Speaker 1>no red square. So that's the trick is figuring out

0:56:22.680 --> 0:56:28.640
<v Speaker 1>how to eliminate those those outliers, those false hits, and

0:56:28.719 --> 0:56:32.720
<v Speaker 1>make sure that the information you're gathering is actually real stuff.

0:56:33.560 --> 0:56:38.359
<v Speaker 1>The last thing that bok She touched upon was in

0:56:38.680 --> 0:56:43.200
<v Speaker 1>concern of mental health. UM He's in a collaboration with

0:56:43.239 --> 0:56:47.200
<v Speaker 1>several other people to create an early warning system for depression.

0:56:47.680 --> 0:56:51.680
<v Speaker 1>He started with looking at depression in teens and also

0:56:51.719 --> 0:56:54.640
<v Speaker 1>to create a therapist chatbot that would help teens deal

0:56:54.680 --> 0:56:58.440
<v Speaker 1>with depression and prevent teen suicide. He cited a very

0:56:58.480 --> 0:57:02.560
<v Speaker 1>troubling statistic and said that in Australia, more than forty

0:57:03.600 --> 0:57:09.440
<v Speaker 1>of teenagers calling helplines per year don't even get another

0:57:09.480 --> 0:57:13.080
<v Speaker 1>person on the phone. The call goes unanswered, which means

0:57:13.080 --> 0:57:15.160
<v Speaker 1>there are thousands of kids who need help but they

0:57:15.160 --> 0:57:17.720
<v Speaker 1>are not getting it because the helpline can't afford to

0:57:17.760 --> 0:57:21.080
<v Speaker 1>pay enough staff to staff all the phones all the time.

0:57:21.760 --> 0:57:25.360
<v Speaker 1>In the United States, of the teens who committed suicide

0:57:25.960 --> 0:57:30.720
<v Speaker 1>were uh found later to have given off signs or patterns,

0:57:30.880 --> 0:57:34.120
<v Speaker 1>but humans aren't always good at picking up on that.

0:57:34.280 --> 0:57:37.600
<v Speaker 1>Like in hindsight, we could say, oh, there was this sign,

0:57:37.680 --> 0:57:41.000
<v Speaker 1>this tragic sign that I did not notice, and if

0:57:41.040 --> 0:57:43.160
<v Speaker 1>I had, if I had noticed, maybe I could have

0:57:43.200 --> 0:57:46.960
<v Speaker 1>done something. This is a horrible tragedy for everybody. Obviously,

0:57:47.040 --> 0:57:50.320
<v Speaker 1>there's a a kid who's lost his or her life,

0:57:50.840 --> 0:57:53.880
<v Speaker 1>and then of course the people around that kid who

0:57:53.920 --> 0:57:57.480
<v Speaker 1>may blame themselves for not having picked up on subtle

0:57:57.560 --> 0:58:00.240
<v Speaker 1>signs that we humans just typically are not very good

0:58:00.440 --> 0:58:05.600
<v Speaker 1>and noticing. Tom They talked about creating algorithms that can

0:58:05.640 --> 0:58:10.160
<v Speaker 1>mine social media again looking for these signs, looking for

0:58:10.560 --> 0:58:15.720
<v Speaker 1>warning flags that someone may be going through depression. Maybe

0:58:15.800 --> 0:58:20.760
<v Speaker 1>there they are experiencing anxiety and stress, and maybe they

0:58:20.840 --> 0:58:26.200
<v Speaker 1>are are entertaining thoughts of self harm or suicide. And

0:58:26.280 --> 0:58:28.600
<v Speaker 1>there are a lot of different indicators that could potentially

0:58:28.720 --> 0:58:32.760
<v Speaker 1>lead someone to have that sort of concern about a person.

0:58:33.240 --> 0:58:36.000
<v Speaker 1>So the idea would be to design these algorithms that

0:58:36.480 --> 0:58:40.600
<v Speaker 1>could send an alert to someone who could step in

0:58:40.680 --> 0:58:45.000
<v Speaker 1>and intervene and perhaps give help to someone who needs

0:58:45.040 --> 0:58:50.080
<v Speaker 1>it because the indicators all show with that person is

0:58:50.120 --> 0:58:52.840
<v Speaker 1>on a really bad pathway. And also this idea of

0:58:52.840 --> 0:58:57.280
<v Speaker 1>a therapist chat bot UH is really intriguing. The idea

0:58:57.400 --> 0:59:00.560
<v Speaker 1>of a chat butt that is responsive in a way

0:59:00.800 --> 0:59:03.600
<v Speaker 1>that's meaningful. It doesn't feel like you're just talking to

0:59:03.680 --> 0:59:08.120
<v Speaker 1>a robot, that you're talking to an uncaring entity that's

0:59:08.200 --> 0:59:13.320
<v Speaker 1>just asking very tough or or very you know, dry

0:59:13.400 --> 0:59:16.200
<v Speaker 1>questions that wouldn't be helpful at all. It has to

0:59:16.200 --> 0:59:19.680
<v Speaker 1>be something that seems to evoke empathy. It seems to

0:59:19.680 --> 0:59:25.000
<v Speaker 1>be UH listening and caring about the person. And the

0:59:25.120 --> 0:59:27.800
<v Speaker 1>nice thing is that chatbots, of course never get tired,

0:59:27.960 --> 0:59:29.960
<v Speaker 1>they never have to go on break, They can always

0:59:29.960 --> 0:59:34.320
<v Speaker 1>be available. They can always provide some guidance and perhaps

0:59:34.840 --> 0:59:39.000
<v Speaker 1>lead someone to resources that might give them more help

0:59:39.040 --> 0:59:42.600
<v Speaker 1>and support when they need it most. And um and

0:59:42.640 --> 0:59:45.680
<v Speaker 1>they talked about how they had rolled this out for teenagers,

0:59:45.680 --> 0:59:48.840
<v Speaker 1>but now they're looking at using it for for veterans,

0:59:48.960 --> 0:59:51.800
<v Speaker 1>for people who have served in the armed forces and

0:59:51.920 --> 0:59:58.160
<v Speaker 1>maybe dealing with depression and other related UH problems and

0:59:58.760 --> 1:00:01.880
<v Speaker 1>feel like they don't have the resources around them to

1:00:01.920 --> 1:00:05.560
<v Speaker 1>help them cope with these issues. So I thought, I

1:00:05.560 --> 1:00:07.800
<v Speaker 1>found that really interesting to this idea of using not

1:00:07.840 --> 1:00:11.400
<v Speaker 1>just very powerful technologies to do cool stuff, but very

1:00:11.440 --> 1:00:16.280
<v Speaker 1>compassionate uses of technology. So that's all three of the

1:00:16.320 --> 1:00:19.960
<v Speaker 1>presenters that I wanted to cover for this episode. Like

1:00:20.000 --> 1:00:22.640
<v Speaker 1>I said before, I've got one more full day here

1:00:22.680 --> 1:00:25.120
<v Speaker 1>at Think eighteen. You never know what I might encounter.

1:00:25.200 --> 1:00:27.560
<v Speaker 1>I might end up having enough to to talk about

1:00:27.760 --> 1:00:32.360
<v Speaker 1>yet another episode. Um, we will see. I can't guarantee

1:00:32.400 --> 1:00:34.560
<v Speaker 1>that that will happen, but I'm going to explore, see

1:00:34.560 --> 1:00:36.479
<v Speaker 1>who I can talk to, see what I can find out,

1:00:37.120 --> 1:00:39.080
<v Speaker 1>and so maybe we'll get one more out of these,

1:00:39.120 --> 1:00:42.240
<v Speaker 1>but if not, it has been a pleasure attending this conference.

1:00:42.240 --> 1:00:44.120
<v Speaker 1>I got to talk to a lot of really smart

1:00:44.160 --> 1:00:47.280
<v Speaker 1>people and learn a lot about these topics that I've

1:00:47.280 --> 1:00:50.560
<v Speaker 1>always been interested in and had some understanding in, but

1:00:50.640 --> 1:00:53.400
<v Speaker 1>this time I felt like I was being absolutely immersed

1:00:53.560 --> 1:00:57.480
<v Speaker 1>in the ideas and it was really, really fascinating. It's

1:00:57.520 --> 1:01:02.200
<v Speaker 1>also mentally exhausting. I don't know how everyone is holding

1:01:02.280 --> 1:01:06.280
<v Speaker 1>up so well, because I feel like my brain is

1:01:06.320 --> 1:01:10.120
<v Speaker 1>slowly turning into sludge being exposed to all this really

1:01:10.200 --> 1:01:15.760
<v Speaker 1>really hyper detailed, complicated information. I hope you guys have

1:01:15.880 --> 1:01:18.640
<v Speaker 1>enjoyed this mini series. I hope to do more of these,

1:01:18.720 --> 1:01:23.280
<v Speaker 1>not just for tech conferences, but related events things that

1:01:23.360 --> 1:01:26.680
<v Speaker 1>touch upon technology. Obviously, because it is tech stuff. But

1:01:26.760 --> 1:01:28.320
<v Speaker 1>I hope to go to more of these sort of

1:01:28.360 --> 1:01:31.720
<v Speaker 1>things and record special episodes that do not again, they

1:01:31.720 --> 1:01:34.920
<v Speaker 1>don't replace our normal episodes of tech stuff, they just

1:01:35.120 --> 1:01:38.520
<v Speaker 1>augment them. It's like that augmented intelligence thing. If you

1:01:38.560 --> 1:01:42.000
<v Speaker 1>guys have suggestions for future episodes of tech Stuff, maybe

1:01:42.040 --> 1:01:44.960
<v Speaker 1>there's a particular technology I need to cover, a person

1:01:45.000 --> 1:01:48.760
<v Speaker 1>who's important in technology, a company that's instrumental in tech.

1:01:49.080 --> 1:01:51.880
<v Speaker 1>Maybe there's a conference or an event that you think

1:01:51.920 --> 1:01:55.000
<v Speaker 1>I absolutely need to go to because you've always wanted

1:01:55.040 --> 1:01:57.600
<v Speaker 1>to learn more about it and you think it would

1:01:57.640 --> 1:02:00.600
<v Speaker 1>be ideal for tech Stuff to attend. Let me know,

1:02:00.800 --> 1:02:03.000
<v Speaker 1>send me a message. The email address for the show

1:02:03.120 --> 1:02:05.920
<v Speaker 1>is text stuff at how stuff works dot com, or

1:02:06.000 --> 1:02:09.200
<v Speaker 1>drop me a line on Twitter or Facebook that sometimes

1:02:09.240 --> 1:02:10.760
<v Speaker 1>it is the fastest way to get in touch with me.

1:02:11.200 --> 1:02:14.160
<v Speaker 1>Those uh they handle for both of those is text

1:02:14.200 --> 1:02:17.680
<v Speaker 1>stuff hs W. Remember we've gotten Instagram account. You can

1:02:17.720 --> 1:02:20.000
<v Speaker 1>go follow that and see behind the scenes stuff and

1:02:20.120 --> 1:02:25.080
<v Speaker 1>other interesting tidbits. And every week on Wednesdays and Fridays,

1:02:25.120 --> 1:02:28.160
<v Speaker 1>I record the normal episodes of tech Stuff and I

1:02:28.240 --> 1:02:30.760
<v Speaker 1>usually stream it live on twitch tv, so you can

1:02:30.760 --> 1:02:33.080
<v Speaker 1>go to twitch dot tv slash text stuff. You can

1:02:33.080 --> 1:02:37.360
<v Speaker 1>watch me record episodes live that means I make mistakes

1:02:37.360 --> 1:02:40.480
<v Speaker 1>and you can watch me do it and stumble over myself.

1:02:40.560 --> 1:02:42.320
<v Speaker 1>There's also a chat room there so you can chat

1:02:42.360 --> 1:02:44.560
<v Speaker 1>with me, and during breaks, I do like to chat

1:02:44.600 --> 1:02:46.400
<v Speaker 1>with everybody in the chat room, see what's going on,

1:02:46.840 --> 1:02:49.080
<v Speaker 1>see if there's anything that they want me to cover

1:02:49.120 --> 1:02:52.360
<v Speaker 1>in specific or in particular I guess I should say,

1:02:52.560 --> 1:02:55.439
<v Speaker 1>And it's always a joy. So please come on by,

1:02:55.720 --> 1:02:58.000
<v Speaker 1>jump in the chat room, introduce yourself. I'd love to

1:02:58.000 --> 1:03:00.720
<v Speaker 1>see there, and I'll talk to you again really soon.

1:03:07.280 --> 1:03:09.680
<v Speaker 1>For more on this and thousands of other topics. Is

1:03:09.720 --> 1:03:20.760
<v Speaker 1>that how stuff works dot com