WEBVTT - Maximum Overclock

0:00:00.160 --> 0:00:06.720
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:06.880 --> 0:00:14.840
<v Speaker 1>Forward Thinking. Hello everyone, welcome to Forward Thinking the Podcast.

0:00:14.920 --> 0:00:18.680
<v Speaker 1>I'm Jonathan Strickland, I'm Lauren Buck Obama, and I'm Joe McCormick.

0:00:18.840 --> 0:00:22.599
<v Speaker 1>And today we wanted to talk a bit about autonomous cars,

0:00:22.680 --> 0:00:25.439
<v Speaker 1>those robo cars the future that are going to take

0:00:25.520 --> 0:00:30.160
<v Speaker 1>us everywhere we want to go, no problem whatsoever. They're

0:00:30.160 --> 0:00:32.959
<v Speaker 1>never gonna melt down, They're never going to turn on us,

0:00:33.240 --> 0:00:36.760
<v Speaker 1>they're never gonna start running down Sarah Connor, Joe, you

0:00:36.800 --> 0:00:38.960
<v Speaker 1>seem to well, should we explain a little bit what

0:00:39.080 --> 0:00:42.760
<v Speaker 1>autonomous cars first? What they are? Okay, an autonomous car,

0:00:42.800 --> 0:00:45.600
<v Speaker 1>at least the general consensus is that this is a

0:00:45.680 --> 0:00:50.400
<v Speaker 1>vehicle that has technology that allows the car to navigate

0:00:50.479 --> 0:00:54.400
<v Speaker 1>and drive through various landscapes without the need for a

0:00:54.480 --> 0:00:58.960
<v Speaker 1>human being to actually manually control the vehicle. That's that's

0:00:59.000 --> 0:01:01.840
<v Speaker 1>kind of the over all definition, I would say, of

0:01:01.880 --> 0:01:04.560
<v Speaker 1>an autonomous car. So you just hop into your Crossford

0:01:04.600 --> 0:01:07.399
<v Speaker 1>puzzle and then you're at work. Yeah, something like that. Yeah,

0:01:07.600 --> 0:01:09.760
<v Speaker 1>just like the way most of us drive, as it

0:01:09.800 --> 0:01:13.480
<v Speaker 1>turns out. Yeah, no, that's that's kind of the idea.

0:01:12.880 --> 0:01:17.360
<v Speaker 1>And yeah, slightly if your death's planned right, right. It's

0:01:17.400 --> 0:01:20.360
<v Speaker 1>a goal that a lot of different companies are working towards.

0:01:20.600 --> 0:01:25.800
<v Speaker 1>Google of course famously had their own autonomous car debuting

0:01:25.840 --> 0:01:30.480
<v Speaker 1>on the roadways of California, but we've seen other vehicles

0:01:30.920 --> 0:01:33.200
<v Speaker 1>kind of like well, other manufacturers follow suit. I mean,

0:01:33.240 --> 0:01:36.000
<v Speaker 1>like companies have started to make them now to sure. Yeah,

0:01:36.240 --> 0:01:39.440
<v Speaker 1>Lexus has its own that it's working on, but there

0:01:39.480 --> 0:01:42.200
<v Speaker 1>are others as well, and it's kind of interesting to

0:01:42.240 --> 0:01:45.399
<v Speaker 1>see this development. But we know that there are people

0:01:45.480 --> 0:01:48.559
<v Speaker 1>out there who have concerns, some of which I would

0:01:48.640 --> 0:01:52.880
<v Speaker 1>say are very legitimate concerns, some of which might be

0:01:52.920 --> 0:01:55.840
<v Speaker 1>a little more based on a misunderstanding of the technology.

0:01:55.840 --> 0:01:58.200
<v Speaker 1>And we went under the kind of talk about those

0:01:58.200 --> 0:02:02.200
<v Speaker 1>concerns and sort of what the potential approaches to a

0:02:02.360 --> 0:02:05.560
<v Speaker 1>suede fears. Okay, Joe, do you would you like to

0:02:05.560 --> 0:02:09.360
<v Speaker 1>take on the role? Yeah, my my angry confused luddite

0:02:09.480 --> 0:02:12.440
<v Speaker 1>uncle Jed. Okay, yeah, it is he the one who

0:02:12.480 --> 0:02:15.760
<v Speaker 1>said he was shooting at some crude Yeah, yeah, I

0:02:15.800 --> 0:02:17.519
<v Speaker 1>guess the wouldn't He was shooting us some food and

0:02:17.600 --> 0:02:19.680
<v Speaker 1>up from the ground came up up from the Grand

0:02:19.680 --> 0:02:22.040
<v Speaker 1>Care bubble, and food that would just be gross. Okay,

0:02:22.040 --> 0:02:25.040
<v Speaker 1>So Jet, Yeah, well, I mean I don't think Jed

0:02:25.160 --> 0:02:27.480
<v Speaker 1>likes this idea. Jed does not like the idea of

0:02:27.520 --> 0:02:30.680
<v Speaker 1>an autonomous car. So no, I mean it, uh it

0:02:30.840 --> 0:02:34.960
<v Speaker 1>frightens and confuses him. He uh, has he perhaps seen

0:02:35.000 --> 0:02:37.359
<v Speaker 1>the movie Maximum Overdrive? Is he upset about this thing

0:02:37.520 --> 0:02:40.040
<v Speaker 1>in the in the nineteen eighties, he saw the Stephen

0:02:40.120 --> 0:02:43.720
<v Speaker 1>King directed film Maximum Overdriving. He's got some concerns he'd

0:02:43.760 --> 0:02:46.640
<v Speaker 1>like to confront you with before he's really convinced about

0:02:46.760 --> 0:02:50.480
<v Speaker 1>the safety of this whole autonomous car deal. One of them,

0:02:50.280 --> 0:02:52.960
<v Speaker 1>I'm sure, Uncle Jed says, is I can't get my

0:02:53.040 --> 0:02:55.760
<v Speaker 1>computer to do what I want half the time. It

0:02:55.880 --> 0:02:58.160
<v Speaker 1>crashes every time I turn it on. You know, I

0:02:58.200 --> 0:03:01.040
<v Speaker 1>click on something on the internet and it never works.

0:03:01.240 --> 0:03:05.679
<v Speaker 1>You know, everything goes crazy. Right? Is that going to

0:03:05.760 --> 0:03:07.880
<v Speaker 1>happen to my car? And am I going to crash

0:03:07.919 --> 0:03:11.160
<v Speaker 1>into a telephone pole because I clicked on the wrong website?

0:03:11.240 --> 0:03:13.840
<v Speaker 1>That's a legitimate fear for someone who has a lot

0:03:13.880 --> 0:03:17.000
<v Speaker 1>of clicking going on whenever they're on the internet. All right, sure,

0:03:17.080 --> 0:03:18.920
<v Speaker 1>And and part of the thing is that obviously you're

0:03:18.960 --> 0:03:21.280
<v Speaker 1>not going to be visiting perhaps the websites of ill

0:03:21.320 --> 0:03:25.760
<v Speaker 1>repute on your car. So therefore there's slightly less danger

0:03:25.800 --> 0:03:27.639
<v Speaker 1>of running into the same kinds of problems that you

0:03:27.680 --> 0:03:30.320
<v Speaker 1>wouldn't run into on the internet in your car. Well,

0:03:30.360 --> 0:03:32.520
<v Speaker 1>let's make it a little more general. Just imagine Uncle

0:03:32.600 --> 0:03:36.600
<v Speaker 1>Jed is generally concerned that something's going to go wrong

0:03:36.680 --> 0:03:40.600
<v Speaker 1>with his autonomous car, that it's going to malfunction somehow. Okay,

0:03:40.680 --> 0:03:43.120
<v Speaker 1>this is going to lead the problem, and that's a

0:03:43.160 --> 0:03:46.360
<v Speaker 1>completely understandable fear. That's a couple of things I think

0:03:46.720 --> 0:03:49.320
<v Speaker 1>we can look at. One is that when it comes

0:03:49.360 --> 0:03:52.360
<v Speaker 1>to a general purpose computer like the kind that most

0:03:52.400 --> 0:03:54.400
<v Speaker 1>of us have on our desks or that we carry

0:03:54.400 --> 0:03:58.040
<v Speaker 1>around when a messenger bag or whatever, um, these computers

0:03:58.040 --> 0:03:59.560
<v Speaker 1>have to do a lot of different things. They have

0:03:59.680 --> 0:04:02.960
<v Speaker 1>to be able to handle different types of tasks. You're

0:04:02.960 --> 0:04:05.880
<v Speaker 1>gonna be loading on all kinds of software onto these

0:04:06.280 --> 0:04:09.680
<v Speaker 1>Sometimes pieces of software work will conflict with one another

0:04:09.840 --> 0:04:12.440
<v Speaker 1>because they were you know, when they were being designed.

0:04:12.800 --> 0:04:15.240
<v Speaker 1>It wasn't designed on a machine that was also running

0:04:15.360 --> 0:04:18.360
<v Speaker 1>you know, X number of other programs. So, for example,

0:04:18.360 --> 0:04:20.600
<v Speaker 1>if you have twenty programs on your computer and you're

0:04:20.760 --> 0:04:24.000
<v Speaker 1>regularly running four of them, it may very well be

0:04:24.080 --> 0:04:26.320
<v Speaker 1>that any one of those four would be fine on

0:04:26.360 --> 0:04:28.720
<v Speaker 1>its own, but when you start running them together, they

0:04:28.760 --> 0:04:31.840
<v Speaker 1>start to compete for resources. Your computer starts to have

0:04:31.920 --> 0:04:37.400
<v Speaker 1>trouble managing that those resources over time, and then problems happen.

0:04:37.560 --> 0:04:40.320
<v Speaker 1>Right in your car, your car is a much more

0:04:40.360 --> 0:04:44.719
<v Speaker 1>specific piece of machinery. It's not a general purpose device,

0:04:45.160 --> 0:04:49.600
<v Speaker 1>and so the computers aboard cars are very specifically tuned

0:04:49.720 --> 0:04:51.760
<v Speaker 1>to what they need to do, and they don't do

0:04:52.000 --> 0:04:55.040
<v Speaker 1>other stuff, and that's generally speaking, a pretty good thing.

0:04:55.080 --> 0:04:58.279
<v Speaker 1>It makes them more reliable in the long run because

0:04:58.320 --> 0:05:00.880
<v Speaker 1>there are fewer things that can enter fear with the

0:05:00.920 --> 0:05:05.479
<v Speaker 1>functioning of that device. So the likelihood of a full

0:05:05.520 --> 0:05:09.159
<v Speaker 1>malfunction the way you would experience on say a regular computer,

0:05:09.600 --> 0:05:13.239
<v Speaker 1>is much lower in something that's has that specific a purpose.

0:05:13.800 --> 0:05:17.200
<v Speaker 1>On top of that, I think that will we will

0:05:17.279 --> 0:05:19.799
<v Speaker 1>have plenty of things that will warn us when something's

0:05:19.839 --> 0:05:22.280
<v Speaker 1>not going well, and I don't think we're ever going

0:05:22.320 --> 0:05:25.680
<v Speaker 1>to reach the point where manual control is no longer

0:05:25.839 --> 0:05:30.640
<v Speaker 1>an option at all. So worst case scenario, you flip

0:05:30.680 --> 0:05:33.920
<v Speaker 1>the switch from robo to me and then you take over.

0:05:34.279 --> 0:05:38.640
<v Speaker 1>But I really think that the likelihood of computer crashes

0:05:38.720 --> 0:05:42.400
<v Speaker 1>becoming a common thing is not that high. And also

0:05:43.400 --> 0:05:45.280
<v Speaker 1>this is something that whenever you take your car and

0:05:45.360 --> 0:05:47.600
<v Speaker 1>to be serviced, I would imagine that's going to be

0:05:47.839 --> 0:05:54.040
<v Speaker 1>a routine part of getting your car the car right.

0:05:54.080 --> 0:05:55.800
<v Speaker 1>And I mean there are certain things that you will

0:05:56.160 --> 0:05:59.920
<v Speaker 1>we would expect to happen, like, for instance, as improvement

0:06:00.200 --> 0:06:03.159
<v Speaker 1>come for the software side of the autonomous car, because

0:06:03.200 --> 0:06:05.919
<v Speaker 1>really autonomous car is kind of like another computer in

0:06:05.920 --> 0:06:07.880
<v Speaker 1>the sense that you've got the hardware and the software.

0:06:08.120 --> 0:06:10.760
<v Speaker 1>But as improvements come along, then I would imagine there

0:06:10.760 --> 0:06:13.599
<v Speaker 1>will be things like firmware updates. This is where a

0:06:13.640 --> 0:06:17.599
<v Speaker 1>company will send out a kind of software that's very

0:06:17.640 --> 0:06:20.479
<v Speaker 1>fundamental to the function of a particular device. You see

0:06:20.520 --> 0:06:24.200
<v Speaker 1>this all the time, and things like phones, gaming consoles,

0:06:24.240 --> 0:06:27.960
<v Speaker 1>even computers, desktops and laptops can get firmware updates. I

0:06:27.960 --> 0:06:30.840
<v Speaker 1>would see that happening. But I really don't think that

0:06:30.920 --> 0:06:35.760
<v Speaker 1>the the common crash that we experience in our our

0:06:35.800 --> 0:06:38.400
<v Speaker 1>desktop and laptop lives would be something that's going to

0:06:38.560 --> 0:06:41.320
<v Speaker 1>plague us in a car setting. And lots of cars

0:06:41.360 --> 0:06:44.720
<v Speaker 1>already have micro controllers in them, right, Oh yeah, no, no,

0:06:44.760 --> 0:06:47.880
<v Speaker 1>they all do. I mean pretty much every car that's

0:06:47.920 --> 0:06:51.360
<v Speaker 1>been manufactured over the last couple of decades has had

0:06:51.600 --> 0:06:54.120
<v Speaker 1>some forms of micro controllers in them. Some of them

0:06:54.160 --> 0:06:57.440
<v Speaker 1>have fairly you know, uh, sophisticated computer systems in them,

0:06:57.440 --> 0:07:00.200
<v Speaker 1>which it's all meant to diagnose problems and to keep

0:07:00.200 --> 0:07:02.440
<v Speaker 1>tracked things, which is one of those things that people

0:07:02.480 --> 0:07:05.400
<v Speaker 1>complain about really because in order for you to really

0:07:05.440 --> 0:07:07.360
<v Speaker 1>know what's going on with your car, is these get

0:07:07.440 --> 0:07:09.800
<v Speaker 1>more and more complex, you have to really plug it

0:07:09.800 --> 0:07:13.080
<v Speaker 1>into a computer, and not everyone has the capability of

0:07:13.120 --> 0:07:15.080
<v Speaker 1>doing that, although we're starting to see some things like

0:07:15.480 --> 0:07:18.600
<v Speaker 1>some cool uh things coming out for smartphones where you

0:07:18.640 --> 0:07:20.880
<v Speaker 1>can actually attach it to your smartphone and you plug

0:07:21.000 --> 0:07:23.680
<v Speaker 1>screen yeah yeah, yeah, that special proprietary cable, you plug

0:07:23.720 --> 0:07:25.280
<v Speaker 1>it into your car, and then your smartphone tells you

0:07:25.320 --> 0:07:27.280
<v Speaker 1>what's wrong. It's a good way of finding out if

0:07:27.280 --> 0:07:30.000
<v Speaker 1>your mechanics on the up and up. Yeah, and also

0:07:30.080 --> 0:07:31.840
<v Speaker 1>not having to waste that, you know, two hours of

0:07:31.840 --> 0:07:34.000
<v Speaker 1>your life and however many dollars going into a mechanic

0:07:34.080 --> 0:07:36.120
<v Speaker 1>just to see what's wrong. So so we already have

0:07:36.480 --> 0:07:39.920
<v Speaker 1>computers in cars, it's just going to get more sophisticated.

0:07:39.920 --> 0:07:42.200
<v Speaker 1>And also the other thing I would answer, although I

0:07:42.280 --> 0:07:46.000
<v Speaker 1>don't like taking this approach very frequently because it's like saying, hey,

0:07:46.240 --> 0:07:48.240
<v Speaker 1>I know you're saying the future is bad, but the

0:07:48.280 --> 0:07:51.000
<v Speaker 1>present is bad too, because that's that's kind of a

0:07:51.080 --> 0:07:55.320
<v Speaker 1>lame argument. But cars breakdown already, right, I mean, stuff

0:07:55.360 --> 0:07:59.520
<v Speaker 1>goes wrong with cars. It physical things, and cars can

0:07:59.600 --> 0:08:02.920
<v Speaker 1>break and wear down and stop working, particularly if you're

0:08:02.920 --> 0:08:04.640
<v Speaker 1>not taking very good care of your car. But even

0:08:04.640 --> 0:08:07.440
<v Speaker 1>if you think you are, things can go wrong. And hypothetically,

0:08:07.480 --> 0:08:09.600
<v Speaker 1>if you have more computers watching that kind of thing,

0:08:09.800 --> 0:08:11.800
<v Speaker 1>that might help in the long run, because you might

0:08:12.040 --> 0:08:14.160
<v Speaker 1>get to the point where your car can tell you when, oh,

0:08:14.240 --> 0:08:16.560
<v Speaker 1>this piece is running low. Oh this oil is running low.

0:08:16.600 --> 0:08:18.960
<v Speaker 1>We need to do something about this before it breaks. Yeah.

0:08:19.000 --> 0:08:21.120
<v Speaker 1>For instance, my wife's car lets us know when the

0:08:21.320 --> 0:08:24.520
<v Speaker 1>tires need to get more air in them. So, uh,

0:08:24.560 --> 0:08:26.320
<v Speaker 1>you know, it used to be a few years ago.

0:08:26.720 --> 0:08:28.000
<v Speaker 1>The way you would notice that as when you walk

0:08:28.080 --> 0:08:30.840
<v Speaker 1>up to your car in the parking lot, you think, whoa, Oh,

0:08:30.920 --> 0:08:33.320
<v Speaker 1>I guess I can't drive. Yeah, I guess I need

0:08:33.360 --> 0:08:35.800
<v Speaker 1>to get to the closest gas station get some air

0:08:35.840 --> 0:08:39.320
<v Speaker 1>in these tires. So so Uncle Jed has another concern though,

0:08:39.400 --> 0:08:42.760
<v Speaker 1>hit me, Uncle Jed, Well, Uncle Jed is also he's

0:08:42.760 --> 0:08:47.480
<v Speaker 1>a very sweet man and uh, every year he buys

0:08:47.640 --> 0:08:51.800
<v Speaker 1>aunt Ruth a birthday present. That's very sweet of him.

0:08:51.840 --> 0:08:54.520
<v Speaker 1>But if he's got to get in an autonomous car,

0:08:55.160 --> 0:08:58.200
<v Speaker 1>that's some kind of computer, right it hooks up to

0:08:58.240 --> 0:09:02.760
<v Speaker 1>the internet. Sure isn't everybody gonna see exactly where he

0:09:02.800 --> 0:09:05.280
<v Speaker 1>goes all the time and know the store he goes

0:09:05.360 --> 0:09:08.040
<v Speaker 1>to to get aunt Ruth's birthday present and they're all

0:09:08.080 --> 0:09:09.800
<v Speaker 1>going to gab to her and she's going to know

0:09:09.840 --> 0:09:12.040
<v Speaker 1>what the president is before she gets it. So autonomous

0:09:12.040 --> 0:09:16.400
<v Speaker 1>cars spoiling birthdays. So essentially we're talking about privacy issue. Yes,

0:09:16.480 --> 0:09:17.959
<v Speaker 1>I think, you know, if we want to be more

0:09:17.960 --> 0:09:22.000
<v Speaker 1>more general than that. So, yeah, I can see where

0:09:22.040 --> 0:09:24.719
<v Speaker 1>the concern is there. Now I think that I think

0:09:24.760 --> 0:09:26.680
<v Speaker 1>a lot of these systems are going to have to

0:09:26.800 --> 0:09:31.679
<v Speaker 1>have built into them privacy measures because privacy is is

0:09:31.720 --> 0:09:34.800
<v Speaker 1>a huge issue for a lot of people, and I

0:09:34.840 --> 0:09:36.520
<v Speaker 1>don't think that's going to go away. In fact, it's

0:09:36.520 --> 0:09:38.920
<v Speaker 1>going to get more important as we get more involved

0:09:39.120 --> 0:09:42.960
<v Speaker 1>with computers in our cars. I think that the potential

0:09:43.320 --> 0:09:47.280
<v Speaker 1>solution for this is to do what Google says it does.

0:09:47.800 --> 0:09:49.760
<v Speaker 1>I'm assuming that what Google says it does is what

0:09:49.880 --> 0:09:52.959
<v Speaker 1>Google actually does. I'm not I don't work for Google's

0:09:53.000 --> 0:09:54.640
<v Speaker 1>I don't see behind the cartain, so I don't know

0:09:54.720 --> 0:09:56.400
<v Speaker 1>for sure, but I'm going to take them at their word.

0:09:57.160 --> 0:10:00.839
<v Speaker 1>Google's approach is to strip all the identified ying information

0:10:00.960 --> 0:10:05.080
<v Speaker 1>off of any particular vehicle when it's tracking things like traffic,

0:10:05.360 --> 0:10:08.840
<v Speaker 1>So that way, as you drive down the street, your

0:10:08.960 --> 0:10:11.480
<v Speaker 1>data is going to Google, so it knows how fast

0:10:11.480 --> 0:10:14.000
<v Speaker 1>you're going. This is assuming you're using a Google Maps

0:10:14.040 --> 0:10:17.880
<v Speaker 1>application on your smartphone ors device, So it knows that

0:10:17.960 --> 0:10:20.920
<v Speaker 1>there is a vehicle going down a particular road at

0:10:20.920 --> 0:10:23.840
<v Speaker 1>a particular speed, and then it it extrapolates from that

0:10:24.040 --> 0:10:27.240
<v Speaker 1>what the traffic conditions must be like on that particular road.

0:10:27.600 --> 0:10:29.920
<v Speaker 1>I would imagine that most of our systems will have

0:10:30.000 --> 0:10:32.920
<v Speaker 1>to have a similar thing in place. Now, what will

0:10:32.920 --> 0:10:35.200
<v Speaker 1>be interesting is to see how that pans out, because

0:10:35.200 --> 0:10:37.640
<v Speaker 1>I think law enforcement would be say, hey, no, it

0:10:37.640 --> 0:10:39.880
<v Speaker 1>would be awesome if we could track where everyone was

0:10:39.960 --> 0:10:42.599
<v Speaker 1>all the time, right. Sure. Some of the gossip that

0:10:42.600 --> 0:10:44.719
<v Speaker 1>I've heard about it is that cars eventually you're going

0:10:44.720 --> 0:10:47.400
<v Speaker 1>to have little black boxes the same way that airplanes do.

0:10:47.840 --> 0:10:49.200
<v Speaker 1>You know, when you get into the car. You don't

0:10:49.240 --> 0:10:50.959
<v Speaker 1>only use a key to get into the car, you

0:10:51.080 --> 0:10:53.480
<v Speaker 1>use a personalized key that tells the car that you

0:10:53.520 --> 0:10:56.319
<v Speaker 1>are the one driving it, for liability issues, for insurance,

0:10:56.360 --> 0:10:59.040
<v Speaker 1>for for traffic accidents, all all that kind of stuff.

0:10:59.400 --> 0:11:01.439
<v Speaker 1>And and so it might have you know, your own

0:11:01.480 --> 0:11:04.120
<v Speaker 1>personal information coated in when you when you get into

0:11:04.160 --> 0:11:07.120
<v Speaker 1>the car and therefore not talent ruth where you're going.

0:11:07.960 --> 0:11:10.080
<v Speaker 1>I could just imagine getting into the car and saying,

0:11:10.640 --> 0:11:13.200
<v Speaker 1>take me to the last place you were before you

0:11:13.320 --> 0:11:17.439
<v Speaker 1>came back home. Wow, Okay, I gotta rethink my plans

0:11:17.480 --> 0:11:21.720
<v Speaker 1>for the future of my travel alright. But anyway, Yeah, so,

0:11:21.720 --> 0:11:25.040
<v Speaker 1>so some of these questions we can't answer immediately simply

0:11:25.080 --> 0:11:26.960
<v Speaker 1>because we're not in that era yet. But I would

0:11:27.000 --> 0:11:30.280
<v Speaker 1>imagine that as we build out these systems, that's something

0:11:30.280 --> 0:11:32.520
<v Speaker 1>that we have to take into consideration because it's it's

0:11:32.679 --> 0:11:34.400
<v Speaker 1>Uncle Jed's not going to be the only guy to

0:11:34.440 --> 0:11:38.199
<v Speaker 1>be concerned about this. Certain people people rightfully are protective

0:11:38.240 --> 0:11:41.400
<v Speaker 1>of their privacy, and I think that's a healthy attitude. Well,

0:11:41.600 --> 0:11:45.720
<v Speaker 1>uncle Jed's got one real final concern and this maybe

0:11:45.760 --> 0:11:49.040
<v Speaker 1>ties more into that scary movie even more than the

0:11:49.080 --> 0:11:53.560
<v Speaker 1>other ones. But not scary movie. Not that scary. No, No, no,

0:11:53.640 --> 0:11:58.559
<v Speaker 1>Maximum overdrect the documentary about the future of right right

0:11:58.800 --> 0:12:04.920
<v Speaker 1>exactly autonomous of trucks, Alien take over um soda machines

0:12:05.000 --> 0:12:08.719
<v Speaker 1>chucking out cans at people. Well, nobody wants that, No,

0:12:09.400 --> 0:12:12.440
<v Speaker 1>But in the movie I think it's what is it?

0:12:12.520 --> 0:12:16.400
<v Speaker 1>Aliens take over our technology? What what if? Because Uncle

0:12:16.480 --> 0:12:20.400
<v Speaker 1>Jed's heard about these hackers, right and he he knows

0:12:20.480 --> 0:12:23.679
<v Speaker 1>that there's these hackers out there? What if the hackers

0:12:24.360 --> 0:12:29.560
<v Speaker 1>put a virus in his autonomous car? Yeah? Um, Uncle Jed,

0:12:29.760 --> 0:12:31.880
<v Speaker 1>Let me let me put your minded ease. First of all,

0:12:31.920 --> 0:12:36.480
<v Speaker 1>I think that getting access to a particular vehicles computer

0:12:36.559 --> 0:12:39.840
<v Speaker 1>will not be easy. The physical location of the computer,

0:12:39.880 --> 0:12:42.559
<v Speaker 1>I would imagine, would be difficult to reach without specific

0:12:42.679 --> 0:12:46.160
<v Speaker 1>kinds of tools. On top of that, reaching a car

0:12:46.280 --> 0:12:49.800
<v Speaker 1>through some sort of wireless means would be somewhat problematic,

0:12:49.800 --> 0:12:52.520
<v Speaker 1>I would imagine. Uh. In fact, I would be more

0:12:52.559 --> 0:12:57.839
<v Speaker 1>worried about hackers targeting the underlying infrastructure that exists within

0:12:58.280 --> 0:13:01.600
<v Speaker 1>say a city, than with in an actual car. Targeting

0:13:01.640 --> 0:13:03.959
<v Speaker 1>a specific car be very tricky and right because these

0:13:03.960 --> 0:13:06.240
<v Speaker 1>aren't going to be running all by themselves. They're going

0:13:06.280 --> 0:13:10.320
<v Speaker 1>to be working with an entire internet of structures that

0:13:10.440 --> 0:13:12.920
<v Speaker 1>is going to be helping them figure out where to go. Yeah,

0:13:12.960 --> 0:13:15.800
<v Speaker 1>if nothing else, you'll have mesh networks, which means that

0:13:15.960 --> 0:13:19.040
<v Speaker 1>you will have a network that is composed of a

0:13:19.080 --> 0:13:21.079
<v Speaker 1>certain number of vehicles in a certain place at a

0:13:21.080 --> 0:13:24.160
<v Speaker 1>certain time, and that number is constantly changing as vehicles

0:13:24.200 --> 0:13:27.280
<v Speaker 1>leave the road or into the road. And this is

0:13:27.320 --> 0:13:31.360
<v Speaker 1>a very complex system. It's difficult to even build, much

0:13:31.440 --> 0:13:34.760
<v Speaker 1>less hack into. But I really think targeting a specific

0:13:35.040 --> 0:13:39.080
<v Speaker 1>car is unrealistic, just like targeting a specific computer tends

0:13:39.120 --> 0:13:41.360
<v Speaker 1>to be unrealistic. And a lot of the problems that

0:13:41.400 --> 0:13:44.360
<v Speaker 1>we have with hackers getting access to people's computers has

0:13:44.440 --> 0:13:47.280
<v Speaker 1>to do with things like downloading malware and installing it

0:13:47.320 --> 0:13:49.880
<v Speaker 1>on your computer, which gives the opportunity for hackers to

0:13:50.520 --> 0:13:53.000
<v Speaker 1>uh to mess with you, or giving someone your password

0:13:53.200 --> 0:13:56.400
<v Speaker 1>or something like that, or not changing the factory default password.

0:13:56.720 --> 0:13:59.360
<v Speaker 1>Right right now, when you're talking about a car, because

0:13:59.400 --> 0:14:03.520
<v Speaker 1>of its specificity, because it's meant for a specific range

0:14:03.559 --> 0:14:06.599
<v Speaker 1>of features, I don't imagine that you will be downloading

0:14:06.640 --> 0:14:10.800
<v Speaker 1>stuff to your car to increase that. Like I can't

0:14:10.800 --> 0:14:13.280
<v Speaker 1>imagine it being something that the user could easily do

0:14:13.400 --> 0:14:15.320
<v Speaker 1>where Let's say that you think, oh, I want to

0:14:15.320 --> 0:14:17.040
<v Speaker 1>make Mike, I want my car to go twenty miles

0:14:17.080 --> 0:14:20.200
<v Speaker 1>per faster than what the factory setting allows. So I'm

0:14:20.200 --> 0:14:23.560
<v Speaker 1>going to download the speed demon a clock your engine, right, Yeah,

0:14:23.600 --> 0:14:26.480
<v Speaker 1>I'm gonna yeah, I'm gonna overclock as opposed to overdrive.

0:14:26.680 --> 0:14:29.640
<v Speaker 1>I would download that that some maximum overclock is what

0:14:29.680 --> 0:14:33.080
<v Speaker 1>we should call this episode. Um, but yeah, that's the

0:14:33.320 --> 0:14:35.960
<v Speaker 1>That's the idea I would say, is that it's it's

0:14:35.960 --> 0:14:39.120
<v Speaker 1>such a specific use that I can't imagine that we're

0:14:39.120 --> 0:14:43.000
<v Speaker 1>going to have the ability to download malware to our cars.

0:14:43.000 --> 0:14:46.080
<v Speaker 1>So it's only if the source is corrupted, which means

0:14:46.120 --> 0:14:49.200
<v Speaker 1>that that malware goes out to everybody. And uh, I

0:14:49.200 --> 0:14:52.600
<v Speaker 1>would and because it would be such a high value target,

0:14:52.760 --> 0:14:54.840
<v Speaker 1>I imagined that there would be a lot of security

0:14:54.840 --> 0:14:58.440
<v Speaker 1>around those systems, right, And you know, there's there's ways

0:14:58.440 --> 0:15:00.520
<v Speaker 1>that people could screw with your card today without having

0:15:00.520 --> 0:15:02.440
<v Speaker 1>a fancy computer running everything that it does. You know,

0:15:02.520 --> 0:15:04.280
<v Speaker 1>someone could come in and cut your brake line. Someone

0:15:04.320 --> 0:15:07.640
<v Speaker 1>could mess with the traffic system in your in your

0:15:07.720 --> 0:15:13.960
<v Speaker 1>county and script the traffic lights the ground. There's actually

0:15:13.960 --> 0:15:16.080
<v Speaker 1>a lot of stuff that people could do to cause

0:15:16.320 --> 0:15:20.720
<v Speaker 1>mayhem already again, you know, that's not necessarily the best argument, Like, well,

0:15:20.760 --> 0:15:23.480
<v Speaker 1>don't be scared of the future because the present is terrifying.

0:15:23.800 --> 0:15:26.640
<v Speaker 1>That's that's not not necessarily the way to get Uncle

0:15:26.720 --> 0:15:29.120
<v Speaker 1>Jed to sleep well at night. But no, it's it

0:15:29.280 --> 0:15:32.200
<v Speaker 1>is true that that really there are going to be

0:15:32.280 --> 0:15:34.960
<v Speaker 1>some challenges in the future. But the nice thing is

0:15:35.040 --> 0:15:38.120
<v Speaker 1>that by acknowledging the fact that there are challenges and

0:15:38.160 --> 0:15:41.800
<v Speaker 1>acknowledging the fact that there are potential worries, you can

0:15:41.800 --> 0:15:44.040
<v Speaker 1>take those into consideration when you're building things out. It's

0:15:44.080 --> 0:15:46.800
<v Speaker 1>not like this is a system that's hitting us tomorrow

0:15:47.080 --> 0:15:48.760
<v Speaker 1>and we're all just going to have to adjust to

0:15:48.800 --> 0:15:51.040
<v Speaker 1>it and then see how it shakes out. We are

0:15:51.120 --> 0:15:53.760
<v Speaker 1>aware of these things before the systems are in place,

0:15:53.840 --> 0:15:56.360
<v Speaker 1>which hopefully means that we will be able to take

0:15:56.360 --> 0:15:59.280
<v Speaker 1>that into consideration when we actually build everything out and

0:15:59.320 --> 0:16:02.000
<v Speaker 1>make it as safe as possible, which is really the

0:16:02.040 --> 0:16:05.080
<v Speaker 1>goal when you think about it of autonomous cars. I mean,

0:16:05.280 --> 0:16:07.600
<v Speaker 1>I've got just a couple of figures here. We've actually

0:16:07.600 --> 0:16:12.120
<v Speaker 1>seen a dramatic decline in fatalities in the United States

0:16:12.200 --> 0:16:15.080
<v Speaker 1>due to car accidents over the last few decades. And

0:16:15.120 --> 0:16:19.080
<v Speaker 1>it's mainly due to improvements in in the way that

0:16:19.280 --> 0:16:22.720
<v Speaker 1>vehicles are built and the way that laws have required

0:16:22.760 --> 0:16:24.720
<v Speaker 1>us to do things like were a seat belt. But

0:16:25.120 --> 0:16:28.480
<v Speaker 1>the decline has been pretty dramatic. Back in nineteen seventy two,

0:16:28.800 --> 0:16:33.640
<v Speaker 1>there were, according to the National Traffic Safety Administration, four

0:16:33.680 --> 0:16:38.440
<v Speaker 1>thousand nine fatalities in nineteen seventy two due to traffic accidents.

0:16:38.480 --> 0:16:41.560
<v Speaker 1>In twenty eleven it was thirty two thousand, three hundred

0:16:41.680 --> 0:16:45.040
<v Speaker 1>sixty seven, so more than more than a twenty thousand

0:16:45.240 --> 0:16:49.000
<v Speaker 1>person drop in those decades because of these Now, think

0:16:49.040 --> 0:16:53.080
<v Speaker 1>about that in the terms of every traffic accident and

0:16:53.160 --> 0:16:56.800
<v Speaker 1>how human error plays a part in that. Again, estimates range,

0:16:56.880 --> 0:16:59.560
<v Speaker 1>but usually human error is said to be a factor

0:16:59.560 --> 0:17:06.000
<v Speaker 1>in About are the numbers that I've seen? Yeah, it's it's.

0:17:06.040 --> 0:17:08.080
<v Speaker 1>It ranges again depending on how you define it, like

0:17:08.080 --> 0:17:10.320
<v Speaker 1>whether or not it was the sole contributor to an

0:17:10.359 --> 0:17:13.359
<v Speaker 1>accident or whether it was part of the problem. And

0:17:13.400 --> 0:17:17.080
<v Speaker 1>then the really funny thing is of those who cause

0:17:17.520 --> 0:17:20.679
<v Speaker 1>traffic accidents with their own human error, seventy percent of

0:17:20.720 --> 0:17:23.720
<v Speaker 1>them think they're better than average drivers. Right, Yeah, well,

0:17:23.800 --> 0:17:26.359
<v Speaker 1>this is the same sort of problem we see with multitaskers. Right,

0:17:26.440 --> 0:17:29.800
<v Speaker 1>there's very good evidence to show that multitasking means that

0:17:29.880 --> 0:17:32.880
<v Speaker 1>you your capacity to do any one of those multiple

0:17:32.880 --> 0:17:37.240
<v Speaker 1>tasks goes down. But there's a tiny percentage of people

0:17:37.240 --> 0:17:41.480
<v Speaker 1>who are actually capable multitaskers. They're called supertaskers. And so

0:17:41.640 --> 0:17:45.120
<v Speaker 1>two percent the population are supertaskers. The other percent believe

0:17:45.160 --> 0:17:47.600
<v Speaker 1>they belong in the two percent and and are lying

0:17:47.600 --> 0:17:50.399
<v Speaker 1>on their resumes. Yeah, so same sort of thing. If

0:17:50.520 --> 0:17:55.920
<v Speaker 1>if you've gone around anent of all accidents are caused

0:17:55.960 --> 0:17:58.440
<v Speaker 1>in part by human error. If you remove human error

0:17:58.480 --> 0:18:00.639
<v Speaker 1>out of that, that number drops so low. I mean,

0:18:00.720 --> 0:18:03.440
<v Speaker 1>think about that. That could affect everything, not just from

0:18:03.600 --> 0:18:08.360
<v Speaker 1>the fatalities, which would be amazing enough, but you wouldn't

0:18:08.440 --> 0:18:10.840
<v Speaker 1>have to worry so much about you know, insurance rates

0:18:10.840 --> 0:18:14.560
<v Speaker 1>could go down because accidents become so rare. You're you're

0:18:14.600 --> 0:18:16.800
<v Speaker 1>talking about the fact that you don't need to worry

0:18:16.840 --> 0:18:21.119
<v Speaker 1>about ensuring vehicles as much over time. Whether or not

0:18:21.160 --> 0:18:23.360
<v Speaker 1>that actually would pan out, I don't know. That's sort

0:18:23.359 --> 0:18:26.960
<v Speaker 1>of a business side thing, but it could happen. And also,

0:18:27.160 --> 0:18:29.560
<v Speaker 1>you don't worry about taking your baby out, your your

0:18:29.600 --> 0:18:31.800
<v Speaker 1>your brand new car out and getting it dinged on

0:18:31.840 --> 0:18:35.360
<v Speaker 1>its first joy ride, or your actual baby here here.

0:18:35.440 --> 0:18:37.719
<v Speaker 1>I I would imagine that many people would feel very

0:18:37.800 --> 0:18:41.639
<v Speaker 1>much safer carrying precious cargo through the streets robo baby

0:18:41.680 --> 0:18:48.560
<v Speaker 1>on board, I think about. Okay, Well, the good thing

0:18:48.680 --> 0:18:51.199
<v Speaker 1>is we have some more time before robo car has

0:18:51.280 --> 0:18:55.440
<v Speaker 1>become a thing that everyone is dealing with. So I'll

0:18:55.480 --> 0:18:58.720
<v Speaker 1>keep working on Uncle Jed. And in the meantime, for

0:18:58.760 --> 0:19:00.800
<v Speaker 1>all you listeners out there, if any of you have

0:19:00.960 --> 0:19:04.200
<v Speaker 1>any suggestions for topics that we should look at things

0:19:04.440 --> 0:19:06.399
<v Speaker 1>that are going to be unfolding in the future, whether

0:19:06.400 --> 0:19:10.399
<v Speaker 1>they're technology based or otherwise, I recommend you let us know.

0:19:10.480 --> 0:19:14.000
<v Speaker 1>In fact, go to the Forward Thinking website that's fw

0:19:14.040 --> 0:19:17.560
<v Speaker 1>thinking dot com and take a look see see the

0:19:17.600 --> 0:19:20.880
<v Speaker 1>blog posts, the podcast, the video series. It's up there,

0:19:21.080 --> 0:19:23.200
<v Speaker 1>and let us know what is it about the future

0:19:23.280 --> 0:19:25.040
<v Speaker 1>that has to be excited We can't wait to hear

0:19:25.080 --> 0:19:29.320
<v Speaker 1>from it. For more on this topic and the future

0:19:29.320 --> 0:19:39.679
<v Speaker 1>of technology, visit forward thinking dot Com, brought to you

0:19:39.720 --> 0:19:41.960
<v Speaker 1>by Toyota. Let's go places