WEBVTT - The Data Analyst

0:00:03.480 --> 0:00:07.760
<v Speaker 1>Tony, Michael, this past week, while you were resting, I

0:00:07.920 --> 0:00:10.640
<v Speaker 1>was hard at work crunching the numbers.

0:00:11.960 --> 0:00:13.720
<v Speaker 2>Did you come up with anything interesting?

0:00:13.880 --> 0:00:14.120
<v Speaker 3>Yes?

0:00:14.440 --> 0:00:17.639
<v Speaker 1>Actually, okay, looking at the breakdown here, it looks like

0:00:17.800 --> 0:00:21.360
<v Speaker 1>last season, Yohai intervened an average of two point seven

0:00:21.440 --> 0:00:24.799
<v Speaker 1>times an episode for what constituted an average of three

0:00:24.840 --> 0:00:29.040
<v Speaker 1>point two minutes of airtime per episode. I see, and

0:00:29.120 --> 0:00:31.360
<v Speaker 1>looking at the data for this current season, which we're

0:00:31.360 --> 0:00:33.600
<v Speaker 1>just getting started with, really, but so far that number

0:00:33.640 --> 0:00:38.200
<v Speaker 1>has been up a staggering four point seven interventions per episode,

0:00:38.760 --> 0:00:42.199
<v Speaker 1>which represents a whopping airtime of three point eight minutes

0:00:42.360 --> 0:00:44.840
<v Speaker 1>per episode. I don't know about you, but I find

0:00:44.840 --> 0:00:46.720
<v Speaker 1>this very troublingling.

0:00:47.920 --> 0:00:50.960
<v Speaker 4>I'm just not sure it's referred to as airtime anymore. Michael.

0:00:51.440 --> 0:00:53.520
<v Speaker 4>It's a podcast. It might be a bit arcade.

0:00:53.560 --> 0:00:55.960
<v Speaker 1>You should feel lucky that I'm calling at interventions and

0:00:56.000 --> 0:00:59.960
<v Speaker 1>not interruptions. Interventions is very general.

0:01:00.480 --> 0:01:02.400
<v Speaker 2>You were just cooled, dog, kay. I'm just gonna put

0:01:02.440 --> 0:01:03.080
<v Speaker 2>that out there.

0:01:03.160 --> 0:01:10.440
<v Speaker 1>Oh Ship for My Heart podcast one on one Studios

0:01:10.440 --> 0:01:15.360
<v Speaker 1>and Sports Illustrated Studios. This is choosing sides.

0:01:15.880 --> 0:01:26.039
<v Speaker 5>Yes, one wow, wow, Tony, I see.

0:01:26.200 --> 0:01:30.360
<v Speaker 1>For today's episode, it's titled the data analyst. And I

0:01:30.400 --> 0:01:32.640
<v Speaker 1>have to be honest with you right out of the gate,

0:01:32.760 --> 0:01:36.720
<v Speaker 1>I'm not a big data numbers person. For me, it's

0:01:36.720 --> 0:01:41.640
<v Speaker 1>about heart, guts, that's sports, all that stuff. Also, every

0:01:41.680 --> 0:01:44.120
<v Speaker 1>sport has statistics and data. You ever look at the

0:01:44.120 --> 0:01:45.399
<v Speaker 1>back of a baseball card, So.

0:01:45.440 --> 0:01:49.200
<v Speaker 2>Yes, every sport has statistics and data. But for example,

0:01:49.200 --> 0:01:51.320
<v Speaker 2>how many sensors does a baseball bat actually have?

0:01:51.560 --> 0:01:55.920
<v Speaker 1>When do you think of it? I can think of

0:01:55.960 --> 0:01:59.280
<v Speaker 1>the gun that measures the miles per hour of the fastball,

0:01:59.680 --> 0:02:01.360
<v Speaker 1>so that the sensor that's one.

0:02:01.520 --> 0:02:04.080
<v Speaker 2>Well, here's the thing. In a modern Formula one car,

0:02:04.280 --> 0:02:06.400
<v Speaker 2>you're looking at roughly two hundred and fifty or three

0:02:06.520 --> 0:02:09.760
<v Speaker 2>hundred sensors and they generate. These two hundred and fifty

0:02:09.800 --> 0:02:13.240
<v Speaker 2>three hundred sensors generate an immense amount of data, and

0:02:13.280 --> 0:02:14.880
<v Speaker 2>all of that data is being streamed back to the

0:02:14.880 --> 0:02:18.240
<v Speaker 2>team and it's constantly being processed and analyzed. And also

0:02:18.280 --> 0:02:21.240
<v Speaker 2>it's not just on the car, Michael, the tires have

0:02:21.400 --> 0:02:24.280
<v Speaker 2>these data sensors as well. The driver's gloves have sensors.

0:02:24.520 --> 0:02:26.239
<v Speaker 2>The F one tracks have sensors.

0:02:26.960 --> 0:02:30.000
<v Speaker 1>The driver's gloves, yes, have sensors on them.

0:02:30.800 --> 0:02:32.400
<v Speaker 2>Gonna come back to that also from a safety and

0:02:32.400 --> 0:02:33.160
<v Speaker 2>security reason.

0:02:33.360 --> 0:02:37.160
<v Speaker 1>Okay, well, what are they sensing? All these sensors sense.

0:02:41.160 --> 0:02:43.120
<v Speaker 1>No matter how many meetings you have, you didn't think

0:02:43.120 --> 0:02:44.200
<v Speaker 1>you'd come up with that one.

0:02:44.280 --> 0:02:47.040
<v Speaker 2>Okay, So to give you a few examples, they're sensing

0:02:47.160 --> 0:02:51.880
<v Speaker 2>things like lap time, tire pressure, breake pressure, frottile position,

0:02:52.080 --> 0:02:55.320
<v Speaker 2>fuel flow, the speed of the wind and how it's

0:02:55.320 --> 0:02:59.120
<v Speaker 2>going over the car, which sounds very poetic, break temperatures,

0:02:59.200 --> 0:03:01.960
<v Speaker 2>engine temperate, which is basically any temperature you can think of.

0:03:02.480 --> 0:03:05.040
<v Speaker 2>And to your point about the driver's gloves, Yes, they

0:03:05.040 --> 0:03:07.400
<v Speaker 2>have sensors and they monitor things like your heart rates.

0:03:07.400 --> 0:03:09.160
<v Speaker 1>I's gonna say all of those other things are just

0:03:09.240 --> 0:03:12.440
<v Speaker 1>measuring the car exactly when we've talked about the driver.

0:03:12.320 --> 0:03:14.040
<v Speaker 2>Yet, And that's what where the gloves come in. And

0:03:14.080 --> 0:03:16.600
<v Speaker 2>it's not the only part of the sensors, but these

0:03:16.639 --> 0:03:18.880
<v Speaker 2>sensors in the little fingertips of the glove are sensing

0:03:18.919 --> 0:03:21.040
<v Speaker 2>their heart rate. There's also an oximeter that measures the

0:03:21.080 --> 0:03:23.919
<v Speaker 2>amount of oxygen in the blood. And I'm just naming

0:03:23.960 --> 0:03:27.040
<v Speaker 2>a few examples right now. All of these sensors, this

0:03:27.160 --> 0:03:30.120
<v Speaker 2>is what's wild, is transmitted back in real time and

0:03:30.160 --> 0:03:34.840
<v Speaker 2>it generates around three terabytes of data for each car

0:03:35.120 --> 0:03:36.000
<v Speaker 2>during each race.

0:03:36.400 --> 0:03:37.640
<v Speaker 1>Wow, that means nothing to me.

0:03:37.720 --> 0:03:47.360
<v Speaker 2>Imagine stacking three hundred thousand Webster dictionaries. That would create

0:03:47.440 --> 0:03:50.640
<v Speaker 2>like a fifteen kilometer high stack of data. If you

0:03:50.760 --> 0:03:52.960
<v Speaker 2>printed out all the data that that's generating. I'm not

0:03:52.960 --> 0:03:53.680
<v Speaker 2>sure that helps you.

0:03:54.920 --> 0:03:56.600
<v Speaker 1>It's a shitload, is what it is.

0:03:56.640 --> 0:03:58.680
<v Speaker 2>There you get. That's another way of saying how much

0:03:58.760 --> 0:03:59.800
<v Speaker 2>data be Well.

0:04:00.040 --> 0:04:04.880
<v Speaker 1>I'm also now thinking once you have the data, Yeah,

0:04:04.960 --> 0:04:08.240
<v Speaker 1>the printed Webster dictionaries, I know that was a metaphor,

0:04:08.320 --> 0:04:09.680
<v Speaker 1>but what do you do with it?

0:04:09.720 --> 0:04:11.640
<v Speaker 2>Where do you go out in the wild now and say,

0:04:11.680 --> 0:04:11.960
<v Speaker 2>do you know.

0:04:13.600 --> 0:04:16.120
<v Speaker 1>Out? Do they have to like storting caves underneath rivers

0:04:16.120 --> 0:04:16.800
<v Speaker 1>to keep it cool?

0:04:17.000 --> 0:04:19.160
<v Speaker 2>Okay, so this is actually a really cool question because

0:04:19.160 --> 0:04:22.760
<v Speaker 2>the data centers have become somewhat like an integral part

0:04:22.800 --> 0:04:27.040
<v Speaker 2>of Formula one racing because the teams need not only

0:04:27.040 --> 0:04:29.800
<v Speaker 2>a reliable way to store, but also analyze the data

0:04:29.800 --> 0:04:32.440
<v Speaker 2>from their cars during the race. And more or less

0:04:32.480 --> 0:04:34.800
<v Speaker 2>everything has been moved to the cloud these days. So

0:04:34.839 --> 0:04:37.520
<v Speaker 2>it used to be that you would have local storages,

0:04:37.560 --> 0:04:39.520
<v Speaker 2>but now everything's in the cloud and there's some backup

0:04:39.560 --> 0:04:42.040
<v Speaker 2>in storage spaces as well, and I think it's time

0:04:42.080 --> 0:04:47.960
<v Speaker 2>for a fun fact. Great, the real time data that

0:04:48.040 --> 0:04:51.320
<v Speaker 2>we're getting right now from each race is combined with

0:04:51.440 --> 0:04:54.599
<v Speaker 2>over seventy years of a historical race data so that

0:04:54.640 --> 0:04:56.800
<v Speaker 2>they can look back and compare the data that they're

0:04:56.800 --> 0:04:59.120
<v Speaker 2>picking up at each race, and they have seventy years

0:04:59.120 --> 0:05:00.479
<v Speaker 2>of historical data look back on.

0:05:00.720 --> 0:05:03.640
<v Speaker 1>So they've re censored all the races.

0:05:03.800 --> 0:05:09.520
<v Speaker 2>So they've migrated Formula one's extensive library of seventy years

0:05:09.560 --> 0:05:13.840
<v Speaker 2>of images, audio video, and they've put all of that

0:05:13.920 --> 0:05:16.760
<v Speaker 2>into the cloud so that the data that they're capturing

0:05:16.800 --> 0:05:19.880
<v Speaker 2>today can be compared to that historical data. I cannot

0:05:19.960 --> 0:05:22.680
<v Speaker 2>imagine the amount of work that went into to taking

0:05:22.720 --> 0:05:26.320
<v Speaker 2>seventy years of footage data, all of that and putting

0:05:26.320 --> 0:05:27.720
<v Speaker 2>it into cloud, but that's something that they've done. And

0:05:27.760 --> 0:05:30.760
<v Speaker 2>apparently it's over one hundred and fifty thousand hours of content.

0:05:31.080 --> 0:05:36.000
<v Speaker 4>Just sorry, just doing my thing here crunching the numbers.

0:05:36.680 --> 0:05:39.560
<v Speaker 4>Consuming one hundred and fifty thousand hours of content would

0:05:39.600 --> 0:05:44.280
<v Speaker 4>take you about six two hundred and fifty days, or

0:05:44.480 --> 0:05:48.960
<v Speaker 4>a little over seventeen years. That's, of course, without any

0:05:49.440 --> 0:05:51.760
<v Speaker 4>stoppage time to eat, sleep.

0:05:52.160 --> 0:05:58.599
<v Speaker 1>Yeah, yeah, Jo has intervened inter intervened way over four

0:05:58.640 --> 0:05:59.599
<v Speaker 1>points seven times.

0:06:00.000 --> 0:06:03.120
<v Speaker 2>It's also another point it's actually worth mentioning. So remember

0:06:03.120 --> 0:06:06.240
<v Speaker 2>in the episode that we looked at the sponsorships and

0:06:06.279 --> 0:06:09.400
<v Speaker 2>the business of Formula one. So in addition to Formula

0:06:09.440 --> 0:06:13.440
<v Speaker 2>one having these incredible tech partners, the teams also have

0:06:13.520 --> 0:06:16.719
<v Speaker 2>these partners to help them store all of this data.

0:06:16.760 --> 0:06:21.640
<v Speaker 2>So we're talking Oracle, Aws, Salesforce, Dell. Technology is cognizant.

0:06:21.920 --> 0:06:24.240
<v Speaker 2>That's why we're in this space right now of tech

0:06:24.279 --> 0:06:27.719
<v Speaker 2>sponsors versus the non tech sponsors that we might have

0:06:27.720 --> 0:06:28.599
<v Speaker 2>had fifty years ago.

0:06:28.800 --> 0:06:33.320
<v Speaker 1>I was wondering, when you start thinking about this data

0:06:33.760 --> 0:06:36.400
<v Speaker 1>me and you if you give us data, yeah, I

0:06:36.400 --> 0:06:38.120
<v Speaker 1>don't know. I mean maybe you know more than I do,

0:06:38.200 --> 0:06:39.880
<v Speaker 1>but I don't know what to do with data. So

0:06:39.960 --> 0:06:41.880
<v Speaker 1>now I need experts to help me know what to

0:06:41.920 --> 0:06:45.039
<v Speaker 1>do with the data exactly. So that makes sense what

0:06:45.080 --> 0:06:48.040
<v Speaker 1>you're saying that you're partnering now with tech. It makes

0:06:48.040 --> 0:06:51.159
<v Speaker 1>me wonder if this is where all sports are headed.

0:06:51.720 --> 0:06:55.000
<v Speaker 1>I honestly think so you know, is one of the

0:06:55.000 --> 0:06:58.400
<v Speaker 1>managers in the baseball dugout going to be more data

0:06:58.480 --> 0:07:02.960
<v Speaker 1>driven than the guide chewing tobacco, you know, giving signals

0:07:02.960 --> 0:07:04.480
<v Speaker 1>to steal. Second is going to be a little kid

0:07:04.480 --> 0:07:07.320
<v Speaker 1>in a computer going like, well, technically, you know.

0:07:07.360 --> 0:07:10.120
<v Speaker 2>What's also going to be interesting is do we want

0:07:10.560 --> 0:07:13.560
<v Speaker 2>data helping us make sense about how decisions are taken

0:07:13.600 --> 0:07:14.120
<v Speaker 2>into sport.

0:07:14.400 --> 0:07:17.600
<v Speaker 1>I'll tell you no, yes, O froze.

0:07:18.160 --> 0:07:20.000
<v Speaker 4>Yeah, just for a second. Do you have a bunch

0:07:20.040 --> 0:07:21.160
<v Speaker 4>of tabs open? Maybe?

0:07:21.240 --> 0:07:21.480
<v Speaker 3>I do?

0:07:21.760 --> 0:07:23.040
<v Speaker 4>Sometimes it helps if you can.

0:07:22.960 --> 0:07:24.520
<v Speaker 3>Just give me half an hour and I'll close all

0:07:24.560 --> 0:07:25.000
<v Speaker 3>these tabs.

0:07:25.360 --> 0:07:27.640
<v Speaker 2>I'm hearing a lot of clicks there, Tarrek, all.

0:07:27.600 --> 0:07:29.320
<v Speaker 3>Very apropos, I assure you so.

0:07:29.400 --> 0:07:32.920
<v Speaker 2>To help us today, we've recruited two first rate F

0:07:33.000 --> 0:07:36.560
<v Speaker 2>one data notes. First up, Tarek Naslwi.

0:07:36.200 --> 0:07:37.640
<v Speaker 3>Been looking forward to this all day.

0:07:37.760 --> 0:07:40.240
<v Speaker 2>Tarek is the creator of a digital platform called Trace,

0:07:40.480 --> 0:07:44.200
<v Speaker 2>a way for fans to document their fandom through data.

0:07:44.280 --> 0:07:48.160
<v Speaker 1>Open here we go. Oh wow, that's really beautiful and cool.

0:07:48.720 --> 0:07:52.080
<v Speaker 1>Every race leaves a trace. This is hard to describe,

0:07:52.120 --> 0:07:55.720
<v Speaker 1>but it's available at trace dot. Fan traces are pieces

0:07:55.760 --> 0:07:59.080
<v Speaker 1>of art made from race data and it's like mathematical

0:07:59.320 --> 0:08:02.920
<v Speaker 1>and it almost looks like if every lap of a

0:08:02.920 --> 0:08:07.040
<v Speaker 1>Formula one race left a shadow and they were all

0:08:07.080 --> 0:08:09.920
<v Speaker 1>on top of each other. It forms this very cool,

0:08:10.240 --> 0:08:15.240
<v Speaker 1>fast looking, almost evil shape, very on brand for everyone.

0:08:15.280 --> 0:08:16.400
<v Speaker 1>This is cool, and a man.

0:08:16.320 --> 0:08:19.880
<v Speaker 2>Who's an absolute legend and an integral part of Formula one.

0:08:20.040 --> 0:08:22.960
<v Speaker 6>All the tentacles are grown way in there.

0:08:23.000 --> 0:08:26.440
<v Speaker 2>And a real, walking, talking encyclopedia of facts and stats.

0:08:26.600 --> 0:08:30.080
<v Speaker 6>Hello, folks, I'm Sean Kelly, and if you've watched a

0:08:30.080 --> 0:08:32.520
<v Speaker 6>Formula one broadcast anywhere in the world in the last

0:08:32.559 --> 0:08:35.960
<v Speaker 6>say two decades, you won't know me, but you will

0:08:35.960 --> 0:08:39.160
<v Speaker 6>know my work because I am essentially the chief statistician

0:08:39.160 --> 0:08:41.280
<v Speaker 6>to the F one Broadcaster's. All the facts and figures

0:08:41.360 --> 0:08:44.400
<v Speaker 6>you hear in a Formula one broadcast, whether they be

0:08:44.559 --> 0:08:46.800
<v Speaker 6>in the graphics, whether they be spoken by the likes

0:08:46.800 --> 0:08:49.840
<v Speaker 6>of David Croft or Martin Brundle or Alex Jakes or whomever,

0:08:50.240 --> 0:08:53.720
<v Speaker 6>I am chiefly responsible for all of that content. So,

0:08:54.120 --> 0:08:57.240
<v Speaker 6>depending on where you stand on the whole statistics spectrum,

0:08:57.280 --> 0:09:00.480
<v Speaker 6>either you're welcome or I'm sorry.

0:09:01.040 --> 0:09:04.160
<v Speaker 2>Just to give you a sense of the genius of Sean,

0:09:04.400 --> 0:09:06.360
<v Speaker 2>I'm going to have to play you this really short

0:09:06.360 --> 0:09:09.000
<v Speaker 2>clip here, and to give you a bit of context.

0:09:09.480 --> 0:09:11.760
<v Speaker 2>We were still in the small talk portion of our

0:09:11.800 --> 0:09:15.480
<v Speaker 2>interview here, just getting to know each other and sharing

0:09:15.520 --> 0:09:16.439
<v Speaker 2>how we got into the spot.

0:09:16.600 --> 0:09:18.000
<v Speaker 6>Can you remember the first race.

0:09:18.360 --> 0:09:23.000
<v Speaker 2>Yes, sper font Gauchamp, only because it was Michael Schumacher's

0:09:23.080 --> 0:09:25.440
<v Speaker 2>first Yeah, first chair.

0:09:25.480 --> 0:09:28.240
<v Speaker 6>Is nearly won it mantl how the voltage regulator go

0:09:28.280 --> 0:09:29.640
<v Speaker 6>out on his card, was in the lead, and then

0:09:29.640 --> 0:09:31.920
<v Speaker 6>the lady was leading, the engine failed and then somehow

0:09:31.920 --> 0:09:33.960
<v Speaker 6>after all that and jordanily ended up winning, and then

0:09:34.000 --> 0:09:36.000
<v Speaker 6>his engine failed and then we ended up with a

0:09:36.080 --> 0:09:38.920
<v Speaker 6>McLaren one too. Like after all this chaos, we ended

0:09:38.960 --> 0:09:41.320
<v Speaker 6>up with the most boring result possible. I went from

0:09:41.360 --> 0:09:43.600
<v Speaker 6>that race so bored that day. I was like, how

0:09:43.640 --> 0:09:45.160
<v Speaker 6>did we end up with that result?

0:09:45.960 --> 0:09:49.280
<v Speaker 2>I need our listeners to understand that Sean had no

0:09:49.400 --> 0:09:53.559
<v Speaker 2>idea that ninety one was my first race, ninety one

0:09:53.559 --> 0:09:55.520
<v Speaker 2>in spa funkle Sean, and that you were able to

0:09:55.880 --> 0:09:58.520
<v Speaker 2>just have all of these facts.

0:09:58.720 --> 0:10:00.920
<v Speaker 6>Berta had the fast slap in that race, I think,

0:10:00.920 --> 0:10:02.400
<v Speaker 6>which is the only time he ever set one in

0:10:02.400 --> 0:10:03.200
<v Speaker 6>a Formula one race.

0:10:03.280 --> 0:10:03.920
<v Speaker 1>That's insane.

0:10:04.120 --> 0:10:06.120
<v Speaker 2>Your brain is fascinating.

0:10:07.400 --> 0:10:08.200
<v Speaker 1>I live with it.

0:10:08.200 --> 0:10:10.559
<v Speaker 6>It's like it's not my constant roommate.

0:10:10.600 --> 0:10:11.520
<v Speaker 3>All this data, all.

0:10:11.520 --> 0:10:12.839
<v Speaker 1>Right, So this is a little hard for me to

0:10:12.880 --> 0:10:15.720
<v Speaker 1>wrap my hair around. Can you give me an example

0:10:16.200 --> 0:10:18.800
<v Speaker 1>of how data is used by a team to gain

0:10:18.840 --> 0:10:21.880
<v Speaker 1>an advantage? Like, okay, great, George Russell's heart rate is high,

0:10:21.920 --> 0:10:24.520
<v Speaker 1>is the blood is oxygenated? His lips are chapped? How

0:10:24.640 --> 0:10:26.120
<v Speaker 1>we got to win the fucking race? What does that

0:10:26.160 --> 0:10:26.679
<v Speaker 1>help us with?

0:10:27.240 --> 0:10:32.640
<v Speaker 2>Okay, so number one, that's more or less a fun fact.

0:10:32.640 --> 0:10:34.880
<v Speaker 2>The data is encrypted and it's sent to the teams

0:10:34.960 --> 0:10:38.800
<v Speaker 2>via radio frequencies, and the frequency is due to like

0:10:38.880 --> 0:10:41.360
<v Speaker 2>little antenna that's mounted on pointing right now, but that's

0:10:41.400 --> 0:10:43.680
<v Speaker 2>mounted on the top of a car. And what's also

0:10:43.760 --> 0:10:46.000
<v Speaker 2>crazy is this happens in like fractions of a second.

0:10:46.200 --> 0:10:49.960
<v Speaker 2>It's also interesting to see that the data transferred is

0:10:50.040 --> 0:10:52.040
<v Speaker 2>faster when the races are in Europe than when the

0:10:52.120 --> 0:10:56.000
<v Speaker 2>races are abroad, even if it's like maybe mini mediseconds.

0:10:55.440 --> 0:10:57.160
<v Speaker 1>Because it's kind of go under the ocean and down

0:10:57.200 --> 0:10:58.720
<v Speaker 1>through the cable and up to the sky and then

0:10:58.760 --> 0:10:59.520
<v Speaker 1>down to the antenna.

0:10:59.600 --> 0:10:59.920
<v Speaker 4>Whoa.

0:11:00.120 --> 0:11:02.000
<v Speaker 2>And sometimes when you're racing in the middle of a city,

0:11:02.040 --> 0:11:04.400
<v Speaker 2>like it's harder to get the frequency out it it's insane.

0:11:04.720 --> 0:11:07.720
<v Speaker 2>But to answer your question, all the data is transferred

0:11:07.800 --> 0:11:10.320
<v Speaker 2>so in real time to the pitball to the factory

0:11:10.400 --> 0:11:12.199
<v Speaker 2>and also the FA so there's a lot of people

0:11:12.240 --> 0:11:14.480
<v Speaker 2>receiving this data, and then it can be used for

0:11:14.520 --> 0:11:17.920
<v Speaker 2>things like comparing your lap time. You overlap your lap

0:11:17.960 --> 0:11:20.640
<v Speaker 2>time with other driver's lap time to see where people are,

0:11:20.679 --> 0:11:22.720
<v Speaker 2>you know, breaking breaking earlier, breaking later.

0:11:23.080 --> 0:11:25.000
<v Speaker 3>If you ever hear one of the race engineers talk

0:11:25.040 --> 0:11:27.640
<v Speaker 3>about you need to go easy on the curbs, it'll

0:11:27.679 --> 0:11:30.600
<v Speaker 3>be because they're sensing vibrations which potentially get to a dangerous

0:11:30.679 --> 0:11:34.679
<v Speaker 3>level causing resonance and potential damage with car components, the

0:11:34.720 --> 0:11:38.320
<v Speaker 3>engine itself probably has I don't know, dozens and dozens

0:11:38.360 --> 0:11:41.920
<v Speaker 3>of sensors on that and actually saw that with Lando

0:11:42.000 --> 0:11:46.080
<v Speaker 3>this weekend. His car went into some kind of safety

0:11:46.120 --> 0:11:51.320
<v Speaker 3>mode where the engine was protecting itself from damage back

0:11:51.920 --> 0:11:57.560
<v Speaker 3>you know, pressure, temperature, vibration, travel as well in the

0:11:57.800 --> 0:12:01.719
<v Speaker 3>suspension on the cars. Anything which can be sensed will

0:12:01.760 --> 0:12:02.200
<v Speaker 3>be sensed.

0:12:02.360 --> 0:12:05.199
<v Speaker 2>Basically, with all this data, the engineers and the driver

0:12:05.320 --> 0:12:08.520
<v Speaker 2>get a much better picture of where the driver is

0:12:08.559 --> 0:12:11.720
<v Speaker 2>losing time, where his opportunities to win some time, and

0:12:11.760 --> 0:12:13.880
<v Speaker 2>where he can make up that time in the race.

0:12:13.960 --> 0:12:15.600
<v Speaker 1>But I can't get my competitors data.

0:12:15.679 --> 0:12:17.959
<v Speaker 3>Can I the on track data that actually I believe

0:12:18.000 --> 0:12:21.320
<v Speaker 3>Formula one owns I think is visible to pretty much everybody.

0:12:21.360 --> 0:12:24.280
<v Speaker 3>So like on track data, like you can see what

0:12:24.320 --> 0:12:27.400
<v Speaker 3>other cars are doing and infer, for example, about your

0:12:27.480 --> 0:12:31.240
<v Speaker 3>pace for the race relative to others' pace, But for example,

0:12:31.280 --> 0:12:34.319
<v Speaker 3>you don't see what fuel loads they had in their

0:12:34.360 --> 0:12:37.280
<v Speaker 3>car or how fast they're consuming that. And that's data

0:12:37.480 --> 0:12:40.320
<v Speaker 3>is like proprietary to the team. So there's a mix

0:12:40.360 --> 0:12:42.960
<v Speaker 3>of data that I think everybody sees and then a

0:12:43.000 --> 0:12:45.760
<v Speaker 3>lot of the data that only the team sees.

0:12:46.160 --> 0:12:48.480
<v Speaker 2>But and this is the joy of a lot of

0:12:48.679 --> 0:12:51.520
<v Speaker 2>data analysts and the f one data analyst fans, is

0:12:51.600 --> 0:12:53.680
<v Speaker 2>a lot of the data is actually also open to

0:12:53.679 --> 0:12:54.080
<v Speaker 2>the public.

0:12:54.320 --> 0:12:57.000
<v Speaker 1>That's I'm going to ask, like can fans get the data?

0:12:57.120 --> 0:12:57.320
<v Speaker 2>Yes?

0:12:57.400 --> 0:12:58.360
<v Speaker 1>Can I get the data?

0:12:58.679 --> 0:12:58.959
<v Speaker 2>Yes?

0:12:59.120 --> 0:13:01.680
<v Speaker 6>Not all of it, some of it, the vast majority

0:13:01.679 --> 0:13:04.520
<v Speaker 6>of it is available to everybody on FORX, if you

0:13:04.559 --> 0:13:07.360
<v Speaker 6>go to the Forest's website, which is a subscription part

0:13:07.360 --> 0:13:11.120
<v Speaker 6>of the Autosport website, yeah, it's all there. It's a

0:13:11.160 --> 0:13:14.000
<v Speaker 6>complicated website to operate, and there's a lot of easter eggs.

0:13:14.000 --> 0:13:16.439
<v Speaker 6>You've got to keep clicking around to find the information

0:13:16.480 --> 0:13:18.280
<v Speaker 6>you want to find. But a great deal of the

0:13:18.480 --> 0:13:22.440
<v Speaker 6>raw numbers can be derived from the publicly accessible part

0:13:22.520 --> 0:13:24.960
<v Speaker 6>of forex if you subscribe to it.

0:13:25.240 --> 0:13:30.920
<v Speaker 1>You know, football turn into a bunch of like drunk

0:13:31.000 --> 0:13:34.160
<v Speaker 1>bros at the bar with their laptops open because of

0:13:34.200 --> 0:13:37.960
<v Speaker 1>Fantasy football doing the stats and the receivers and I,

0:13:38.679 --> 0:13:41.199
<v Speaker 1>you know, I grumble about that, but this is like

0:13:41.360 --> 0:13:42.160
<v Speaker 1>whole new level.

0:13:42.400 --> 0:13:45.240
<v Speaker 2>This is a whole new level and perfect for those

0:13:45.320 --> 0:13:47.880
<v Speaker 2>nerdy fans who just wants that to numbers. The other

0:13:48.080 --> 0:13:52.000
<v Speaker 2>really interesting thing is it used to be back in

0:13:52.040 --> 0:13:55.240
<v Speaker 2>the day that the teams would create their own sensors

0:13:55.280 --> 0:13:57.360
<v Speaker 2>and set up the own antennas and all of that,

0:13:57.640 --> 0:13:59.920
<v Speaker 2>and then the teams kind of realize, hey, wait a minute,

0:14:00.040 --> 0:14:03.079
<v Speaker 2>we're not in a race to create the best sensors

0:14:03.080 --> 0:14:05.440
<v Speaker 2>and the best technology. Hence why today all of that

0:14:05.480 --> 0:14:06.520
<v Speaker 2>is mandated by the FIA.

0:14:06.880 --> 0:14:11.600
<v Speaker 1>What a unique time in history for F one because

0:14:11.960 --> 0:14:16.080
<v Speaker 1>tech is at its most profound ever ever. Yeah, so

0:14:16.120 --> 0:14:17.719
<v Speaker 1>it's pretty interesting.

0:14:17.480 --> 0:14:19.880
<v Speaker 2>And it's it's at its most profound. And what's really

0:14:19.880 --> 0:14:23.080
<v Speaker 2>interesting is behind closed doors, a lot of the things

0:14:23.120 --> 0:14:25.760
<v Speaker 2>that are developed inside of the factories of the F

0:14:25.800 --> 0:14:28.880
<v Speaker 2>one teams then spill over into the rest of the world.

0:14:29.320 --> 0:14:32.040
<v Speaker 2>Glaxo Smith Klein, one of the big farmer companies in

0:14:32.080 --> 0:14:34.840
<v Speaker 2>the world, looked at how I think it was McClaren

0:14:34.920 --> 0:14:37.320
<v Speaker 2>or Williams did their pit stops, and we're just like, huh,

0:14:37.400 --> 0:14:39.880
<v Speaker 2>there's something we can learn you about how we bottle toothpaste.

0:14:40.000 --> 0:14:42.400
<v Speaker 2>And so they figured out how to bottle toothpaste faster,

0:14:42.760 --> 0:14:44.840
<v Speaker 2>which meant they could create more bottles of toothpaste and

0:14:44.880 --> 0:14:46.080
<v Speaker 2>sell more bottles of toothpaste.

0:14:46.120 --> 0:14:49.160
<v Speaker 1>And I was like, genius, is it true that Max

0:14:49.200 --> 0:14:53.120
<v Speaker 1>for Stapping keeps us coffee warm in that coffee cup?

0:14:53.520 --> 0:14:57.040
<v Speaker 1>Because I heard that that that's how the car industry

0:14:57.120 --> 0:15:00.880
<v Speaker 1>keeps our coffee worm. Now what No, But my point

0:15:01.000 --> 0:15:03.400
<v Speaker 1>is sorry for the bad joke, everybody, but the point

0:15:03.520 --> 0:15:07.120
<v Speaker 1>is much like the military was like leading the world

0:15:07.360 --> 0:15:11.720
<v Speaker 1>in research and development and velcro and all this other shit,

0:15:12.120 --> 0:15:15.520
<v Speaker 1>wender bread, all this stuff spilled over to us plebeians.

0:15:16.120 --> 0:15:17.200
<v Speaker 1>F one is doing that as.

0:15:17.080 --> 0:15:20.520
<v Speaker 2>Well, exact same. The FIA produces like this fifty or

0:15:20.600 --> 0:15:23.280
<v Speaker 2>sixty page guide at the end of every year where

0:15:23.320 --> 0:15:26.480
<v Speaker 2>it just highlights all of the callshit that's developed behind

0:15:26.480 --> 0:15:29.440
<v Speaker 2>closed doors, but then spills over whether it's taking care

0:15:29.440 --> 0:15:32.080
<v Speaker 2>of newborn babies, they've used the same system that they

0:15:32.160 --> 0:15:34.960
<v Speaker 2>used to No, but it's true. Like the thing that

0:15:35.000 --> 0:15:38.200
<v Speaker 2>the drivers are satin to keep them really protected, They've

0:15:38.200 --> 0:15:41.400
<v Speaker 2>developed the same mechanism for newborn babies that have maybe

0:15:41.560 --> 0:15:43.840
<v Speaker 2>have issues or that need to be transported by helicopter

0:15:43.960 --> 0:15:45.880
<v Speaker 2>or Apple to make sure that the babies don't move.

0:15:46.160 --> 0:15:47.480
<v Speaker 2>And I'm just like, this is genius.

0:15:47.560 --> 0:15:52.000
<v Speaker 1>That's so cool. We have to take quick break and

0:15:52.040 --> 0:15:57.280
<v Speaker 1>we'll be right back. Hey, we're back. Okay, where were.

0:15:57.080 --> 0:15:59.520
<v Speaker 2>We pulling on that thread of what the fan the

0:15:59.680 --> 0:16:01.840
<v Speaker 2>lens at which the fans go to, So you mentioned

0:16:01.880 --> 0:16:06.320
<v Speaker 2>your baseball fans. Some especially nerdy fans, will actually write

0:16:06.400 --> 0:16:09.440
<v Speaker 2>up all kinds of different software that pulls the publicly

0:16:09.520 --> 0:16:12.880
<v Speaker 2>available data from all the different relevant sources and then

0:16:12.880 --> 0:16:15.080
<v Speaker 2>it lets them play around with it on their own.

0:16:15.160 --> 0:16:17.640
<v Speaker 3>Like there are some engineers or ex engineers who are

0:16:18.080 --> 0:16:20.880
<v Speaker 3>sharing on social images of how like the new parts

0:16:21.000 --> 0:16:23.000
<v Speaker 3>change the flow of a car and what that does

0:16:23.040 --> 0:16:24.680
<v Speaker 3>to the aerodynamic forces on a car.

0:16:24.760 --> 0:16:28.720
<v Speaker 1>Okay, hold on CFD, Yeah, come on, Derek, what's CFD?

0:16:29.040 --> 0:16:33.480
<v Speaker 3>CFD Yeah. CFD is computational fluid dynamics. So if you

0:16:33.520 --> 0:16:38.040
<v Speaker 3>ever see pictures of like simulations of how a of

0:16:38.040 --> 0:16:41.440
<v Speaker 3>how an airflow will go over a surface. Those simulations

0:16:41.440 --> 0:16:43.920
<v Speaker 3>are done in a computer, which are also then leads

0:16:43.920 --> 0:16:46.880
<v Speaker 3>to what people decide to test in wind tunnels. Right,

0:16:46.960 --> 0:16:49.840
<v Speaker 3>this is basically the rocket science part of the Formula

0:16:49.840 --> 0:16:54.120
<v Speaker 3>one stuff. There are ways for fans to access that

0:16:54.240 --> 0:16:56.840
<v Speaker 3>kind of you know, storytelling and information like you go

0:16:56.960 --> 0:16:58.640
<v Speaker 3>look in the Box Box Club app and in the

0:16:58.680 --> 0:17:01.360
<v Speaker 3>Explore section there there's a whole bunch of people who

0:17:01.360 --> 0:17:04.560
<v Speaker 3>are basically taking images and overlaying things to do with

0:17:04.560 --> 0:17:06.960
<v Speaker 3>what forces are happening on the car. And you know,

0:17:07.040 --> 0:17:11.879
<v Speaker 3>I studied engineering at Cambridge for four years and even

0:17:11.920 --> 0:17:14.280
<v Speaker 3>some of that information is like pretty close to the

0:17:14.359 --> 0:17:16.879
<v Speaker 3>kinds of stuff you would study if you specialize in

0:17:16.920 --> 0:17:20.400
<v Speaker 3>fluid dynamics and mechanics and things like that. So it's

0:17:20.440 --> 0:17:24.440
<v Speaker 3>fantastic there are creators that want to expose that level

0:17:24.600 --> 0:17:28.040
<v Speaker 3>of technical understanding of what's going on in the car

0:17:28.119 --> 0:17:30.679
<v Speaker 3>as well. Of course, the number of people that want

0:17:30.720 --> 0:17:32.040
<v Speaker 3>to hang out with you and talk about it gets

0:17:32.080 --> 0:17:35.800
<v Speaker 3>smaller and smaller as you go down. But don't let

0:17:35.800 --> 0:17:37.280
<v Speaker 3>it stop for you. Don't let it stop for you

0:17:37.320 --> 0:17:39.720
<v Speaker 3>find your tribe sit in the rabbit hole where however

0:17:39.720 --> 0:17:40.480
<v Speaker 3>deep you want to go.

0:17:40.600 --> 0:17:42.960
<v Speaker 2>If you just head over, for example, to get her Michael,

0:17:43.280 --> 0:17:45.600
<v Speaker 2>and you look at the Python code for fast F

0:17:45.680 --> 0:17:47.920
<v Speaker 2>one like you will find if you know, if after

0:17:47.920 --> 0:17:50.280
<v Speaker 2>this episode you get really into the data, that's where

0:17:50.280 --> 0:17:50.760
<v Speaker 2>you should go.

0:17:51.359 --> 0:17:55.119
<v Speaker 1>In my life, no one has ever said this sentence

0:17:55.160 --> 0:17:58.000
<v Speaker 1>to me. Just head over to getthub and look for

0:17:58.040 --> 0:18:05.320
<v Speaker 1>the Python code for fast F one. Take that statistic sheets,

0:18:05.400 --> 0:18:07.720
<v Speaker 1>you know, I don't know, like men go out ice

0:18:07.760 --> 0:18:10.679
<v Speaker 1>fishing for six hours on a Sunday, you know, and

0:18:10.720 --> 0:18:12.240
<v Speaker 1>it's like how much It's like, how much do you

0:18:12.280 --> 0:18:14.560
<v Speaker 1>hate your family if you're But I'm like, well, if

0:18:14.560 --> 0:18:17.440
<v Speaker 1>you're coating for F one, you know, we all got

0:18:17.440 --> 0:18:18.679
<v Speaker 1>our stuff. Man, we did.

0:18:18.880 --> 0:18:21.919
<v Speaker 4>What they need is they need a GitHub code to

0:18:22.000 --> 0:18:22.680
<v Speaker 4>tell them.

0:18:22.560 --> 0:18:26.800
<v Speaker 1>Where the fish are. Yeah, fun fact, they don't even

0:18:26.800 --> 0:18:36.080
<v Speaker 1>care about the fish. It's just being out there.

0:18:34.320 --> 0:18:35.040
<v Speaker 2>Moving swiftly.

0:18:35.080 --> 0:18:35.159
<v Speaker 3>On.

0:18:35.440 --> 0:18:37.560
<v Speaker 1>Let me ask you this, Tony. I noticed watching the

0:18:37.640 --> 0:18:42.000
<v Speaker 1>races that drivers do a thing called track walk. Is

0:18:42.000 --> 0:18:42.640
<v Speaker 1>that what it's called?

0:18:42.840 --> 0:18:43.040
<v Speaker 2>Yeah?

0:18:43.200 --> 0:18:46.359
<v Speaker 1>Okay? And they literally just walk around the entire track.

0:18:47.240 --> 0:18:49.760
<v Speaker 1>Given this conversation we've been having, am I understanding how

0:18:49.800 --> 0:18:52.840
<v Speaker 1>the vast amount of data they have about every little detail.

0:18:53.560 --> 0:18:56.399
<v Speaker 1>What data are these drivers picking up from just walking

0:18:56.400 --> 0:18:57.000
<v Speaker 1>around the track.

0:18:57.119 --> 0:18:59.240
<v Speaker 2>They will look over if the track has changed, the layout,

0:18:59.280 --> 0:19:03.240
<v Speaker 2>huts changed, look up identifying potential issues or challenges that

0:19:03.280 --> 0:19:06.159
<v Speaker 2>the driver might have over the weekend, and more. It

0:19:06.200 --> 0:19:07.879
<v Speaker 2>depends on the driver and the race engineer and the

0:19:07.920 --> 0:19:09.520
<v Speaker 2>relationship that they have. But more often than not, it's

0:19:09.560 --> 0:19:11.640
<v Speaker 2>like a two way conversation about going back and forth

0:19:11.640 --> 0:19:15.000
<v Speaker 2>about what they're I imagine it's like a nice reset

0:19:15.040 --> 0:19:16.920
<v Speaker 2>for the team of like this is okay, now it's

0:19:17.080 --> 0:19:17.959
<v Speaker 2>race time. Let's go.

0:19:18.119 --> 0:19:20.359
<v Speaker 1>It must feel so fast when they drive it, yeah,

0:19:20.440 --> 0:19:22.600
<v Speaker 1>because they were just like last time I was walking.

0:19:22.320 --> 0:19:27.560
<v Speaker 2>This fun fact of this year, I think they banned

0:19:28.119 --> 0:19:31.120
<v Speaker 2>bicycles on tracks. These tracks are pretty long, and so

0:19:31.160 --> 0:19:32.639
<v Speaker 2>some of the drivers would be like, oh, we're just

0:19:32.640 --> 0:19:35.520
<v Speaker 2>going to cycle around the track. They banned that because

0:19:35.560 --> 0:19:38.800
<v Speaker 2>too many drivers were having like bicycle accidents.

0:19:38.920 --> 0:19:41.119
<v Speaker 1>Just can't slow it down. They can't just slow it,

0:19:41.240 --> 0:19:43.560
<v Speaker 1>just walk, use the two legs that God gave you.

0:19:43.680 --> 0:19:46.960
<v Speaker 4>Is there an element of like superstition to this, like

0:19:47.000 --> 0:19:48.240
<v Speaker 4>a kind of bit of a ritual.

0:19:49.680 --> 0:19:51.280
<v Speaker 2>There's so much superstition in sport.

0:19:51.359 --> 0:19:55.280
<v Speaker 1>I feel like the higher the stakes the more superstition.

0:19:55.359 --> 0:19:58.040
<v Speaker 1>And I would think when F one there's high stakes,

0:19:58.080 --> 0:20:00.440
<v Speaker 1>because there's life can be on the line. Do these

0:20:00.840 --> 0:20:04.240
<v Speaker 1>drivers pray? Are they're religious?

0:20:04.640 --> 0:20:08.160
<v Speaker 2>Pierre Gasley, for example, always does the sign of the Cross.

0:20:08.600 --> 0:20:13.480
<v Speaker 1>Because there's a beautiful contradictory here in data and faith,

0:20:14.280 --> 0:20:16.439
<v Speaker 1>because they don't always go hand in hand, and often

0:20:16.640 --> 0:20:21.000
<v Speaker 1>times the highest scientific scientists are not as keen to

0:20:21.840 --> 0:20:26.720
<v Speaker 1>spiritual faith. And yet also every athlete I've ever known,

0:20:26.800 --> 0:20:29.760
<v Speaker 1>especially the high levels, they there's a lot of faith there.

0:20:29.800 --> 0:20:31.560
<v Speaker 3>I can tell you what I think about this, which

0:20:31.600 --> 0:20:34.919
<v Speaker 3>is that you can be an extremely technically oriented person

0:20:35.720 --> 0:20:39.399
<v Speaker 3>and believe in science, believe in science being subscribed to

0:20:39.440 --> 0:20:42.320
<v Speaker 3>science as a way of describing how the universe works,

0:20:42.960 --> 0:20:46.160
<v Speaker 3>But answers to why things are the way they are

0:20:46.560 --> 0:20:48.760
<v Speaker 3>or how they came to be that way are not

0:20:48.920 --> 0:20:51.919
<v Speaker 3>answered by data that you can record, least of all

0:20:51.960 --> 0:20:54.080
<v Speaker 3>on the F one car. So I wouldn't fall into

0:20:54.119 --> 0:20:56.160
<v Speaker 3>the trap of thinking that if you are into data

0:20:56.240 --> 0:20:58.440
<v Speaker 3>or science, that you don't have the capacity or the

0:20:58.480 --> 0:21:02.080
<v Speaker 3>predilection for any kind of spiritual beliefs. And at least

0:21:02.080 --> 0:21:06.119
<v Speaker 3>that's my personal take on things. And yeah, don't underestimate

0:21:06.119 --> 0:21:09.520
<v Speaker 3>any capacity of any human for being able to operate

0:21:09.560 --> 0:21:10.359
<v Speaker 3>at that dimension.

0:21:16.760 --> 0:21:17.560
<v Speaker 2>How did we get here?

0:21:17.800 --> 0:21:22.120
<v Speaker 1>I don't know, but that's what's fun about podcasting. So Okay,

0:21:22.600 --> 0:21:25.000
<v Speaker 1>you know I was going to ask you this, but

0:21:25.680 --> 0:21:28.840
<v Speaker 1>I've been excited to ask you this. Okay, too much data,

0:21:29.960 --> 0:21:33.040
<v Speaker 1>at some point, they're overthinking it. There's too many data points.

0:21:33.280 --> 0:21:35.520
<v Speaker 1>If you were to analyze everything, you would never sleep.

0:21:35.560 --> 0:21:37.359
<v Speaker 1>You would just be a robot of data. And then

0:21:37.359 --> 0:21:39.600
<v Speaker 1>you couldn't even drive. Put the keys on the car.

0:21:39.600 --> 0:21:41.240
<v Speaker 1>I know these car, These cars don't have keys. But

0:21:42.040 --> 0:21:44.240
<v Speaker 1>is there such thing as too much data?

0:21:44.400 --> 0:21:46.480
<v Speaker 3>Yeah, there is such a thing as too much data?

0:21:46.640 --> 0:21:49.600
<v Speaker 3>There certainly is. I mean, you can argue, what harm

0:21:49.640 --> 0:21:51.600
<v Speaker 3>does it do if it doesn't take time or money

0:21:51.680 --> 0:21:53.399
<v Speaker 3>or to collect it or store it. But it does.

0:21:53.720 --> 0:21:56.879
<v Speaker 3>Data is only as good as the rates that you

0:21:56.880 --> 0:21:58.920
<v Speaker 3>can process it and the insights that you can glean

0:21:58.960 --> 0:22:01.640
<v Speaker 3>from it. There certainly is. I mean, I would say

0:22:01.640 --> 0:22:05.080
<v Speaker 3>most corporations suffer from the challenge of not being able

0:22:05.080 --> 0:22:07.919
<v Speaker 3>to manipulate and distill insight from the data that they

0:22:07.920 --> 0:22:10.919
<v Speaker 3>collect as a business. I know certainly that's been my experience.

0:22:11.440 --> 0:22:13.159
<v Speaker 3>So I think there is. Yeah, there is such a

0:22:13.200 --> 0:22:15.720
<v Speaker 3>thing but you know, you first have to have the

0:22:15.800 --> 0:22:17.840
<v Speaker 3>raw ingredient in order to sort of cook with it.

0:22:17.920 --> 0:22:21.000
<v Speaker 3>So I think collecting data and figuring out what to

0:22:21.040 --> 0:22:23.439
<v Speaker 3>do with that. You know, collecting it is always the

0:22:23.440 --> 0:22:26.479
<v Speaker 3>first thing, and you make an investment decision about what

0:22:26.520 --> 0:22:27.800
<v Speaker 3>you want to spend time collecting.

0:22:28.119 --> 0:22:30.359
<v Speaker 2>So yes, there is such a thing as too much data.

0:22:30.400 --> 0:22:33.080
<v Speaker 2>But also know, if there's data to collect, they're going

0:22:33.119 --> 0:22:33.679
<v Speaker 2>to collect it.

0:22:33.800 --> 0:22:37.440
<v Speaker 1>They must think it's useful. Yeah, you know, I mean

0:22:37.720 --> 0:22:40.399
<v Speaker 1>does max verst ap and collect more data?

0:22:40.600 --> 0:22:45.280
<v Speaker 3>My hypothesis would be no, I think that's really more

0:22:45.280 --> 0:22:46.879
<v Speaker 3>of a function of the car than it is it

0:22:46.920 --> 0:22:50.359
<v Speaker 3>is the driver. He might be generating less insight, but

0:22:50.560 --> 0:22:52.920
<v Speaker 3>I don't know if he's if he's generating less data.

0:22:53.119 --> 0:23:00.399
<v Speaker 3>There's a difference between data, information and insight. Right is

0:23:00.400 --> 0:23:05.320
<v Speaker 3>the raw ingredient. Right information is when somebody puts that

0:23:05.440 --> 0:23:08.919
<v Speaker 3>information on a chart or a screen, like what you

0:23:08.960 --> 0:23:12.000
<v Speaker 3>see on the pitwall. Insight is the ability to read

0:23:12.040 --> 0:23:16.280
<v Speaker 3>that and draw a new conclusion which leads you to

0:23:16.440 --> 0:23:19.639
<v Speaker 3>some kind of decision or to twist or stick with

0:23:19.680 --> 0:23:22.399
<v Speaker 3>what you're currently doing. So when we think about that,

0:23:22.520 --> 0:23:24.560
<v Speaker 3>like most people think data and they think charts, well,

0:23:24.600 --> 0:23:27.760
<v Speaker 3>I think data. I think bits and bytes, information and

0:23:27.880 --> 0:23:31.280
<v Speaker 3>insight are what data turns into. So that might be

0:23:31.320 --> 0:23:33.840
<v Speaker 3>why I might have answered your question a little bit literally.

0:23:34.640 --> 0:23:36.679
<v Speaker 1>I forget what it was. It was an NPR and

0:23:36.720 --> 0:23:38.520
<v Speaker 1>and know it's a different competitor. But they did a

0:23:38.560 --> 0:23:41.000
<v Speaker 1>story on how you can hack into someone's computer and

0:23:41.040 --> 0:23:45.040
<v Speaker 1>control their car. Now, me and you are car. So

0:23:47.040 --> 0:23:50.840
<v Speaker 1>if they have all this data, can they control the car?

0:23:50.960 --> 0:23:53.399
<v Speaker 1>Can the engineer control the car? Who's controlling the car?

0:23:53.560 --> 0:23:55.040
<v Speaker 1>Is the driver just a pretty face?

0:23:55.240 --> 0:23:58.800
<v Speaker 3>Some drivers are pretty faces. I won't necessarily reveal who

0:23:58.840 --> 0:24:02.480
<v Speaker 3>I think is pretty than others, but I mean, I

0:24:02.480 --> 0:24:04.720
<v Speaker 3>think the clear answer is no. You know, if you

0:24:04.760 --> 0:24:07.399
<v Speaker 3>sort of think about like that, the car is something

0:24:07.400 --> 0:24:14.080
<v Speaker 3>which is being configured to create the maximum opportunity for performance.

0:24:14.800 --> 0:24:19.800
<v Speaker 3>You still have to extract that performance, and you cannot

0:24:19.840 --> 0:24:23.440
<v Speaker 3>program that in a way which beats a human yet

0:24:23.720 --> 0:24:27.560
<v Speaker 3>at least right, and so the ability for a human

0:24:27.600 --> 0:24:31.000
<v Speaker 3>to interact with the physical world and to be able

0:24:31.040 --> 0:24:35.280
<v Speaker 3>to control that car with all of the parameters that

0:24:35.320 --> 0:24:38.200
<v Speaker 3>they have, which is you know, steering input, acceleration input,

0:24:38.280 --> 0:24:41.159
<v Speaker 3>break input, which basically the three basic inputs and the

0:24:41.200 --> 0:24:43.640
<v Speaker 3>perfect way at the perfect moments and the perfect combination

0:24:44.280 --> 0:24:46.679
<v Speaker 3>on a car which is basically designed to operate on

0:24:46.760 --> 0:24:49.600
<v Speaker 3>an absolute knife's edge. If you and I got in

0:24:49.600 --> 0:24:52.239
<v Speaker 3>the car, it would be a very different outcome. I mean,

0:24:52.240 --> 0:24:54.800
<v Speaker 3>actually there wouldn't be a lot of space for you

0:24:54.840 --> 0:24:56.520
<v Speaker 3>and I to get in the same car. But like

0:24:57.160 --> 0:25:00.560
<v Speaker 3>you get my point, which is, if you're a driving

0:25:00.600 --> 0:25:02.719
<v Speaker 3>by the way, I have my synric behind me, so

0:25:02.760 --> 0:25:05.000
<v Speaker 3>I do have a go at this right And I

0:25:05.040 --> 0:25:06.800
<v Speaker 3>do think that there is such a thing as good driver.

0:25:06.840 --> 0:25:10.119
<v Speaker 3>It's like there's no way around it. That's why the

0:25:10.119 --> 0:25:12.119
<v Speaker 3>competition to be one of the twenty on the grid

0:25:12.280 --> 0:25:16.800
<v Speaker 3>is just that intense. I'm a fan believer that you

0:25:17.400 --> 0:25:19.760
<v Speaker 3>can't take the driver out of the car and expect

0:25:19.840 --> 0:25:21.480
<v Speaker 3>anything special to happen.

0:25:21.800 --> 0:25:25.840
<v Speaker 1>We got to take a short break. Hey, we're back

0:25:25.960 --> 0:25:26.479
<v Speaker 1>to Michael.

0:25:26.840 --> 0:25:29.679
<v Speaker 2>Now. Is all of this data hitting you? Are you

0:25:29.760 --> 0:25:32.159
<v Speaker 2>feeling and enrich? Do you fashion yourself to be a

0:25:32.240 --> 0:25:33.560
<v Speaker 2>data fan? Where's your head up?

0:25:36.600 --> 0:25:44.000
<v Speaker 1>I'm thinking calculating. I'm thinking. My knee jerk reaction to

0:25:44.119 --> 0:25:46.200
<v Speaker 1>the word data is that it's a four letter word.

0:25:46.280 --> 0:25:48.040
<v Speaker 2>Michael doesn't like four letter words.

0:25:48.160 --> 0:25:53.159
<v Speaker 1>Yeah, and I don't enjoy how society is so data

0:25:53.400 --> 0:25:57.040
<v Speaker 1>driven right now, because I'm you're taking the feel out

0:25:57.080 --> 0:26:00.760
<v Speaker 1>of things. It's not everything in life is just a

0:26:00.840 --> 0:26:04.840
<v Speaker 1>one in a zero. But I'm more intrigued now that

0:26:04.920 --> 0:26:05.800
<v Speaker 1>we've talked about it.

0:26:05.960 --> 0:26:06.560
<v Speaker 2>I love it.

0:26:06.920 --> 0:26:10.560
<v Speaker 1>If I have multiple screens up watching Formula one, I'm

0:26:10.600 --> 0:26:15.080
<v Speaker 1>not gonna want data. I'm gonna want different driver's helmet

0:26:15.119 --> 0:26:18.040
<v Speaker 1>cams and the stadium shot. I mean, I'm gonna want

0:26:18.080 --> 0:26:18.800
<v Speaker 1>those visuals.

0:26:18.840 --> 0:26:20.800
<v Speaker 2>You want the athletes, yeah, or just.

0:26:20.760 --> 0:26:25.000
<v Speaker 1>The machine, the rocket going off, you know. But there

0:26:25.000 --> 0:26:27.800
<v Speaker 1>are these nerds that want to just check out torque

0:26:28.680 --> 0:26:31.080
<v Speaker 1>revolutions or whatever, but have it. I mean, that's cool.

0:26:31.280 --> 0:26:32.000
<v Speaker 1>I'm happy for them.

0:26:32.440 --> 0:26:37.520
<v Speaker 2>By the way, is the new name of the podcasts.

0:26:37.960 --> 0:26:41.280
<v Speaker 3>If anybody's listening to this thing that feels like they're

0:26:41.320 --> 0:26:44.439
<v Speaker 3>not a data driven fan and that this isn't for

0:26:44.520 --> 0:26:47.160
<v Speaker 3>them because they don't feel like they were never into

0:26:47.200 --> 0:26:51.160
<v Speaker 3>math when they grew up, or they're not like particularly

0:26:51.160 --> 0:26:54.719
<v Speaker 3>technical in their orientation or something like that, I guess.

0:26:54.840 --> 0:26:57.960
<v Speaker 3>I guess all I would say is like, you don't

0:26:58.040 --> 0:27:00.680
<v Speaker 3>have to label yourself a data driven fan to understand

0:27:00.680 --> 0:27:03.439
<v Speaker 3>that there's another layer of story that's going on in

0:27:03.600 --> 0:27:07.280
<v Speaker 3>mosor spot and you know, don't think of the data,

0:27:07.440 --> 0:27:09.960
<v Speaker 3>which is something which is kind of scary, which makes

0:27:09.960 --> 0:27:14.760
<v Speaker 3>this for other people, especially for technically oriented oriented males.

0:27:15.200 --> 0:27:16.880
<v Speaker 3>I think there's a lot more than meets the eye,

0:27:16.880 --> 0:27:19.000
<v Speaker 3>and you don't have to dig that deep to find it.

0:27:19.160 --> 0:27:21.760
<v Speaker 3>And I think that's to me what the beauty of

0:27:21.800 --> 0:27:24.240
<v Speaker 3>this sport and what got me hooked on it. If

0:27:24.240 --> 0:27:26.479
<v Speaker 3>you imagine I'm doing this with my hands now, right,

0:27:26.520 --> 0:27:28.800
<v Speaker 3>I'm creating this sort of picture of this kind of funnel,

0:27:29.000 --> 0:27:30.879
<v Speaker 3>right of like you know, whide at the top and

0:27:30.960 --> 0:27:34.280
<v Speaker 3>narrow at the bottom. For me, the data driven part

0:27:34.320 --> 0:27:38.199
<v Speaker 3>of fandom and the stories which really unfold during a

0:27:38.320 --> 0:27:40.960
<v Speaker 3>race or during a season are kind of in the

0:27:40.960 --> 0:27:43.159
<v Speaker 3>middle of that funnel. And if you're a person a

0:27:43.200 --> 0:27:45.879
<v Speaker 3>fan that loves to live in the rabbit hole, that

0:27:45.960 --> 0:27:49.800
<v Speaker 3>loves to understand what's going on beneath the surface, then

0:27:50.040 --> 0:27:52.760
<v Speaker 3>you can't really do that without some way of capturing

0:27:52.840 --> 0:27:56.679
<v Speaker 3>what's going on and then using that to replay and

0:27:56.680 --> 0:27:59.120
<v Speaker 3>tell a story. Because you're I mean, I'm sure, Tony,

0:27:59.160 --> 0:28:01.480
<v Speaker 3>you've spoken to a people who were like, it's just

0:28:01.520 --> 0:28:03.680
<v Speaker 3>a bunch of cars going around in circles, isn't it.

0:28:04.320 --> 0:28:06.080
<v Speaker 3>And then some of those. These are the people like

0:28:06.280 --> 0:28:08.440
<v Speaker 3>right at the top of this funnel, right then there's

0:28:08.440 --> 0:28:11.920
<v Speaker 3>the people who got into Drive to Survive and they're like, oh,

0:28:11.920 --> 0:28:14.320
<v Speaker 3>there's so much more than just cars go around a track.

0:28:14.359 --> 0:28:17.439
<v Speaker 3>There's narratives and stories and characters and drama and whatever.

0:28:18.320 --> 0:28:21.000
<v Speaker 3>And then as you get drawn into the sport, and

0:28:21.119 --> 0:28:23.480
<v Speaker 3>for me that was through gaming. Actually, like I got

0:28:23.520 --> 0:28:26.440
<v Speaker 3>I went from Drive to Survive to playing F one,

0:28:26.520 --> 0:28:30.200
<v Speaker 3>the co Masters game. Religiously, this is when I still

0:28:30.240 --> 0:28:33.960
<v Speaker 3>had time to play video games. And then I started

0:28:33.960 --> 0:28:36.359
<v Speaker 3>to understand what's going on from the seat of a

0:28:36.440 --> 0:28:39.080
<v Speaker 3>driver or of a team because you experience that, and

0:28:39.080 --> 0:28:41.760
<v Speaker 3>then when you see the race again, you're like, well,

0:28:41.760 --> 0:28:44.720
<v Speaker 3>all the story. Like the broadcast, it's such a narrow

0:28:44.760 --> 0:28:47.480
<v Speaker 3>window on all of these events that are going on,

0:28:47.760 --> 0:28:52.560
<v Speaker 3>like tire graining, pit stop times, which overtakes the happening, overcuts,

0:28:52.640 --> 0:28:56.840
<v Speaker 3>undercuts fuel consumption. You start to see way more than

0:28:56.960 --> 0:28:59.680
<v Speaker 3>is shown on the screen. And to me, that's the

0:28:59.680 --> 0:29:03.320
<v Speaker 3>real fun of it. It's almost like you're decoding a

0:29:03.360 --> 0:29:07.040
<v Speaker 3>live event as is happening, and then after the fact

0:29:07.160 --> 0:29:09.360
<v Speaker 3>you get to chew on it for that many more days,

0:29:09.360 --> 0:29:10.880
<v Speaker 3>which is a super fan, It's like, that's all you

0:29:10.920 --> 0:29:12.640
<v Speaker 3>want to do, right, is just engage more and more

0:29:12.680 --> 0:29:14.680
<v Speaker 3>deeply with the thing that you love. And without the

0:29:14.680 --> 0:29:17.720
<v Speaker 3>way to capture data and use that to replay to

0:29:17.800 --> 0:29:20.160
<v Speaker 3>tell the stories, I think it would be a less

0:29:20.920 --> 0:29:23.560
<v Speaker 3>compelling experience. From my perspective, what I'm.

0:29:23.400 --> 0:29:25.440
<v Speaker 2>Hearing from you is you like the idea that data

0:29:25.480 --> 0:29:28.080
<v Speaker 2>could make you better, but you don't want data to

0:29:28.120 --> 0:29:30.880
<v Speaker 2>be the driving force behind the athlete.

0:29:31.280 --> 0:29:34.120
<v Speaker 1>No, I don't want to be so judgmentally against data.

0:29:34.200 --> 0:29:37.200
<v Speaker 1>It's just not what tickles my fancy in sport. But

0:29:37.720 --> 0:29:43.120
<v Speaker 1>it is absolutely remarkable how this sport consumes data.

0:29:43.840 --> 0:29:47.080
<v Speaker 2>Here's another thing for you to think about. Why might

0:29:47.200 --> 0:29:51.960
<v Speaker 2>be fundamentally different or exponentially using big words here, but

0:29:52.080 --> 0:29:55.640
<v Speaker 2>exponentially more useful in a sport like Formula one because

0:29:55.720 --> 0:29:59.840
<v Speaker 2>the teams have such limited times with the cars on.

0:30:00.800 --> 0:30:03.520
<v Speaker 2>Every time you take a Formula one car, it's mandated,

0:30:03.720 --> 0:30:06.800
<v Speaker 2>it's restricted. They can't, no one can. A driver can't

0:30:06.800 --> 0:30:08.360
<v Speaker 2>just wake up one they and go I'm just gonna

0:30:08.360 --> 0:30:09.480
<v Speaker 2>go and take the car up for a run and

0:30:09.520 --> 0:30:12.520
<v Speaker 2>practice if you they can't. So because it's so limited

0:30:12.560 --> 0:30:14.840
<v Speaker 2>with how they can practice with the cars, I think

0:30:14.920 --> 0:30:17.560
<v Speaker 2>that's why every ounce of data is picked up and

0:30:17.560 --> 0:30:21.720
<v Speaker 2>collected and analyzed and useful. A baseball person makes sense,

0:30:21.760 --> 0:30:24.920
<v Speaker 2>and baseball person, a baseball athlete, a golfer can pick

0:30:25.000 --> 0:30:27.440
<v Speaker 2>up a pair of clubs and swing, you know, practice

0:30:27.440 --> 0:30:29.640
<v Speaker 2>in their own time. I actually can't think of another

0:30:29.720 --> 0:30:32.400
<v Speaker 2>sport where you can't practice at will.

0:30:34.400 --> 0:30:37.160
<v Speaker 1>I remember talking about that last season. It's very fascinating.

0:30:37.400 --> 0:30:39.000
<v Speaker 1>So I think you can hit a tennis ball for

0:30:39.040 --> 0:30:41.080
<v Speaker 1>as many hours as you're allowed to, as many hours

0:30:41.200 --> 0:30:43.200
<v Speaker 1>as you physically want to. But that can't be the case.

0:30:43.320 --> 0:30:45.520
<v Speaker 2>Yeah, And I remember Kobe talking about this with being

0:30:45.560 --> 0:30:47.760
<v Speaker 2>a basketball player. Of just like I get up five

0:30:47.800 --> 0:30:50.160
<v Speaker 2>hours before everyone else, and so I have five hours

0:30:50.160 --> 0:30:53.120
<v Speaker 2>of training on everyone else every single day. Formula one

0:30:53.200 --> 0:30:56.080
<v Speaker 2>drivers do not have that. Hence why I think that

0:30:56.200 --> 0:30:58.640
<v Speaker 2>data plays such a big role in Formula one.

0:30:58.680 --> 0:31:03.840
<v Speaker 1>Also, it's mind boggling to think that I was buying

0:31:03.920 --> 0:31:06.560
<v Speaker 1>shoes today on the internet and it was frustrating me

0:31:06.560 --> 0:31:08.160
<v Speaker 1>because I would add it to my cart and then

0:31:08.240 --> 0:31:10.120
<v Speaker 1>check out, and it would there'd be like a gap

0:31:10.400 --> 0:31:13.760
<v Speaker 1>in uh loading loading, you know, and I'd be like,

0:31:13.760 --> 0:31:15.600
<v Speaker 1>why is there a gap? It's a new computer edition

0:31:16.480 --> 0:31:18.400
<v Speaker 1>everything was fine, but it's like it's a little too strong.

0:31:18.480 --> 0:31:20.600
<v Speaker 1>And then to think that this their way they're racing

0:31:20.720 --> 0:31:24.680
<v Speaker 1>is happening in data like instantaneously yep, and it's crazy

0:31:24.720 --> 0:31:28.200
<v Speaker 1>and that probably gets into our logistic episode. That's wild

0:31:28.240 --> 0:31:29.720
<v Speaker 1>to me that that can even happen.

0:31:29.760 --> 0:31:31.600
<v Speaker 2>And they're still pushing the limits to figure out how

0:31:31.640 --> 0:31:34.720
<v Speaker 2>they can get the data uploaded to HQ faster than

0:31:34.720 --> 0:31:36.800
<v Speaker 2>what it is now when we're talking zero point zero ones,

0:31:36.840 --> 0:31:39.040
<v Speaker 2>you know, we're always pushing the limit.

0:31:39.760 --> 0:31:42.280
<v Speaker 1>Fall boots, if that's what you're asking, fall Boots. We

0:31:42.480 --> 0:31:44.360
<v Speaker 1>still get like a month left in the fall here.

0:31:45.000 --> 0:31:48.840
<v Speaker 4>So Michael, shit is that? YOHI Again, our team here

0:31:48.880 --> 0:31:53.040
<v Speaker 4>at Choosing Size HQ, we've been crunching the numbers and

0:31:53.680 --> 0:31:58.720
<v Speaker 4>unfortunately it does seem that you're going off script about

0:31:58.720 --> 0:32:01.840
<v Speaker 4>twenty five percent more than than than management would like.

0:32:02.880 --> 0:32:05.080
<v Speaker 4>So that I've got a request here. They're asking if

0:32:05.120 --> 0:32:08.360
<v Speaker 4>you can just try to be a little more vigilant.

0:32:08.920 --> 0:32:24.080
<v Speaker 7>You see. Uh, this has been Choosing Sides f one,

0:32:24.840 --> 0:32:29.040
<v Speaker 7>a production of Sports Illustrated Studios, iHeart Podcast and one

0:32:29.120 --> 0:32:30.560
<v Speaker 7>oh one Studio podcast.

0:32:32.040 --> 0:32:35.360
<v Speaker 4>The show is hosted by Michael Costa and Tony Cowan Brown.

0:32:37.000 --> 0:32:40.600
<v Speaker 4>This episode was edited, scored, and sound designed by senior

0:32:40.640 --> 0:32:46.280
<v Speaker 4>producer Johai may Thad scott Stone is the executive producer

0:32:46.600 --> 0:32:49.880
<v Speaker 4>and head of audio, and Daniel Wexman is Director of

0:32:49.960 --> 0:32:54.120
<v Speaker 4>podcast Development and production Manager at one on one Studios.

0:32:54.960 --> 0:32:58.680
<v Speaker 4>At iHeart podcast Sean ty Tone is our executive producer.

0:32:59.080 --> 0:33:02.520
<v Speaker 4>And a special thank you to Michelle Newman, David Glasser,

0:33:02.640 --> 0:33:06.640
<v Speaker 4>and David Hoodkin from One o one Studios. For more

0:33:06.680 --> 0:33:10.760
<v Speaker 4>shows from iHeart Podcasts, go visit the iHeartRadio app, Apple

0:33:10.800 --> 0:33:17.480
<v Speaker 4>Podcasts or wherever you get your podcasts, and whatever you do,

0:33:17.480 --> 0:33:21.960
<v Speaker 4>don't forget to rate us and tell your friends. It

0:33:22.040 --> 0:33:23.040
<v Speaker 4>really does mean a lot.

0:33:27.960 --> 0:33:31.160
<v Speaker 2>Michael, yess what's coming up next week?

0:33:31.680 --> 0:33:32.000
<v Speaker 1>Is it?

0:33:32.240 --> 0:33:32.480
<v Speaker 2>Yes?

0:33:32.520 --> 0:33:35.720
<v Speaker 1>It is finally, Yes.

0:33:35.680 --> 0:33:39.560
<v Speaker 2>Yes, it's the turn of the tireheads.

0:33:40.040 --> 0:33:43.720
<v Speaker 1>Yeah. I'm not sure why I'm so excited about tires,

0:33:43.760 --> 0:33:45.320
<v Speaker 1>but I am time.

0:33:45.120 --> 0:33:48.960
<v Speaker 2>For talking rubber tires, screeching, the whole shebang.

0:33:49.960 --> 0:33:53.720
<v Speaker 1>It seems very important. It seems so so so important.

0:33:53.760 --> 0:33:55.960
<v Speaker 1>The S and the M and the H and they

0:33:56.000 --> 0:33:58.440
<v Speaker 1>all get the same amount of tires or whatever. And

0:33:58.480 --> 0:34:01.320
<v Speaker 1>when I take my car into the MC, they say

0:34:01.360 --> 0:34:04.240
<v Speaker 1>the most important thing is tires and breaks next on

0:34:04.440 --> 0:34:07.760
<v Speaker 1>Torque Revolution. YOHI could you send us off with some

0:34:07.760 --> 0:34:09.280
<v Speaker 1>screeching tire noises or something

0:34:12.120 --> 0:34:12.880
<v Speaker 4>Such a cliche