WEBVTT - Are the weather apps getting worse?

0:00:00.200 --> 0:00:01.680
<v Speaker 1>I'm Manny, I'm Noah.

0:00:01.720 --> 0:00:03.520
<v Speaker 2>This is Steven and this is no such thing.

0:00:03.720 --> 0:00:06.320
<v Speaker 3>The show where we settle our dumb arguments and yours

0:00:06.519 --> 0:00:09.880
<v Speaker 3>by actually doing the research. On today's episode, are the

0:00:10.000 --> 0:00:15.360
<v Speaker 3>weather apps actually getting worse? And how random is Spotify's

0:00:15.360 --> 0:00:16.120
<v Speaker 3>shuffle feature?

0:00:16.480 --> 0:00:16.840
<v Speaker 2>Really?

0:00:19.360 --> 0:00:22.920
<v Speaker 1>I no, there's no no such thing, no such thing,

0:00:24.280 --> 0:00:26.040
<v Speaker 1>no such thing.

0:00:28.040 --> 0:00:31.520
<v Speaker 4>Such those such.

0:00:38.880 --> 0:00:41.559
<v Speaker 3>So as the weather seems to be getting more and

0:00:41.720 --> 0:00:46.400
<v Speaker 3>more unpredictable. With flash flooding overtaking our subways in New

0:00:46.479 --> 0:00:47.319
<v Speaker 3>York City, you.

0:00:47.240 --> 0:00:50.760
<v Speaker 5>Can see water spouting out of the walls, people walking

0:00:50.760 --> 0:00:53.800
<v Speaker 5>across flooded platforms, and that rather dirty water.

0:00:54.120 --> 0:00:57.319
<v Speaker 3>To the tragic, deadly floods in central Texas, we.

0:00:57.320 --> 0:00:59.960
<v Speaker 5>Confirm that at least one hundred and thirty five people

0:01:00.360 --> 0:01:02.880
<v Speaker 5>have been killed. This is in addition to the more

0:01:02.920 --> 0:01:06.880
<v Speaker 5>than one hundred people who remain missing across several counties.

0:01:07.280 --> 0:01:10.200
<v Speaker 3>This week, we are turning our attention to our weather

0:01:10.240 --> 0:01:13.880
<v Speaker 3>apps and then nottedly. Many people in our lives have

0:01:13.959 --> 0:01:17.880
<v Speaker 3>been complaining that the weather apps are just not accurate anymore.

0:01:18.959 --> 0:01:20.600
<v Speaker 3>So we're going to get to the bottom of that

0:01:21.480 --> 0:01:25.560
<v Speaker 3>and answer all your other questions about weather apps, including

0:01:25.560 --> 0:01:26.880
<v Speaker 3>this one from my friend.

0:01:26.600 --> 0:01:30.400
<v Speaker 6>Alek Okay, So I want to know why we as

0:01:30.440 --> 0:01:34.279
<v Speaker 6>society can't come together and use feels like temperatures instead

0:01:34.319 --> 0:01:38.000
<v Speaker 6>of actual temperatures as the default, because right now, when

0:01:38.000 --> 0:01:40.000
<v Speaker 6>they tell me it's going to be sixty five degrees,

0:01:40.520 --> 0:01:42.880
<v Speaker 6>I then have to go and do other homework on

0:01:43.120 --> 0:01:45.240
<v Speaker 6>like how wendy is it going to be that day?

0:01:45.400 --> 0:01:47.600
<v Speaker 6>And is it going to be really humid? And it

0:01:47.760 --> 0:01:50.400
<v Speaker 6>seems like they have come up with one number that

0:01:50.520 --> 0:01:52.919
<v Speaker 6>can give me the answer that I'm really looking for here,

0:01:53.280 --> 0:01:55.400
<v Speaker 6>which is do I need a jacket that day?

0:01:55.720 --> 0:01:58.160
<v Speaker 1>That's a great question, and it reminds me of when

0:01:58.200 --> 0:02:00.880
<v Speaker 1>you guys used to make fun of me for saying

0:02:00.920 --> 0:02:05.200
<v Speaker 1>that it feels quote unquote good outside like it feels good,

0:02:05.680 --> 0:02:10.360
<v Speaker 1>and I maintain that many people say that maybe not

0:02:10.440 --> 0:02:14.920
<v Speaker 1>from you know, Connecticut or Long Island, but I just

0:02:14.960 --> 0:02:16.760
<v Speaker 1>wanted to get that off my chest.

0:02:17.000 --> 0:02:17.200
<v Speaker 4>Yeah.

0:02:17.440 --> 0:02:19.960
<v Speaker 2>I love the idea of like a Manny weather app that.

0:02:21.760 --> 0:02:26.800
<v Speaker 3>It just says feels good.

0:02:27.520 --> 0:02:29.680
<v Speaker 1>That's all I need to know. But just to be

0:02:29.760 --> 0:02:33.120
<v Speaker 1>clear that the feels like it's a part of the app,

0:02:33.160 --> 0:02:34.880
<v Speaker 1>I actually don't see it that often. It's a part

0:02:35.040 --> 0:02:36.560
<v Speaker 1>is on the weather? Which app is.

0:02:36.520 --> 0:02:38.560
<v Speaker 3>This all the apps kind of have it now, so

0:02:38.560 --> 0:02:41.280
<v Speaker 3>there's usually app okay.

0:02:40.960 --> 0:02:42.400
<v Speaker 7>And they don't really have much.

0:02:42.960 --> 0:02:44.040
<v Speaker 2>So like, let's pull it up now.

0:02:44.080 --> 0:02:48.160
<v Speaker 3>It's usually you know, the air temp which is up top,

0:02:50.000 --> 0:02:53.400
<v Speaker 3>and then feels like it's usually below that or very deeper.

0:02:53.840 --> 0:02:56.200
<v Speaker 3>So like this, this is the default Apple one. You

0:02:56.280 --> 0:02:58.920
<v Speaker 3>really got to scroll here. So it's eighty seven right

0:02:58.960 --> 0:03:01.760
<v Speaker 3>now from Brooklyn, and then we scroll all the way down,

0:03:01.880 --> 0:03:03.519
<v Speaker 3>feels like ninety one.

0:03:04.080 --> 0:03:07.560
<v Speaker 1>Okay, that is helpful. It's helpful, but I guess I

0:03:07.600 --> 0:03:10.920
<v Speaker 1>do also want to know the real temperature. That's my

0:03:11.080 --> 0:03:13.240
<v Speaker 1>guess is that y'all do you want to know the

0:03:13.240 --> 0:03:13.800
<v Speaker 1>real temp?

0:03:14.040 --> 0:03:16.520
<v Speaker 3>I don't care about the real temperature. It doesn't matter.

0:03:16.960 --> 0:03:19.400
<v Speaker 3>This was especially true remember when we had those really

0:03:19.480 --> 0:03:20.440
<v Speaker 3>really windy days.

0:03:21.000 --> 0:03:24.079
<v Speaker 7>Oh yeah, it's it's yeah, it's in the hot weather.

0:03:24.160 --> 0:03:26.200
<v Speaker 7>It's less of a thing I feel for us anymore.

0:03:26.240 --> 0:03:28.320
<v Speaker 2>I mean, well, no, still thing, because.

0:03:28.080 --> 0:03:29.600
<v Speaker 7>It can be in the cold. I feel like that

0:03:30.160 --> 0:03:32.760
<v Speaker 7>the wind can change it so dramatic.

0:03:32.880 --> 0:03:35.000
<v Speaker 3>They'll be like it's forty degrees out. I'm like, oh,

0:03:35.040 --> 0:03:36.840
<v Speaker 3>this is kind of warm for winter. And then it

0:03:36.960 --> 0:03:38.720
<v Speaker 3>was like the wind is making it feel like it's

0:03:38.720 --> 0:03:39.840
<v Speaker 3>fifteen exactly.

0:03:40.080 --> 0:03:43.320
<v Speaker 7>But it's like I don't hear what the still cold day? Okay,

0:03:43.360 --> 0:03:45.880
<v Speaker 7>I can live in this versus like I'm about to

0:03:45.920 --> 0:03:46.160
<v Speaker 7>die in.

0:03:46.160 --> 0:03:49.520
<v Speaker 3>Free because why are we checking the weather? You're checking

0:03:49.520 --> 0:03:51.480
<v Speaker 3>them whether to see what I gotta wear.

0:03:52.680 --> 0:03:54.680
<v Speaker 1>Yeah, it's true for me, it's.

0:03:56.280 --> 0:03:59.800
<v Speaker 3>We're not you know, like that's what most people checking

0:04:00.040 --> 0:04:01.240
<v Speaker 3>other while they're checking the letter.

0:04:01.680 --> 0:04:04.520
<v Speaker 1>I might wear something different in sixty five degree weather

0:04:04.560 --> 0:04:06.760
<v Speaker 1>than you might. Yeah, I mean you still need to

0:04:06.800 --> 0:04:08.680
<v Speaker 1>know what to wear for you. That's why I want

0:04:08.680 --> 0:04:10.840
<v Speaker 1>to know the real temperature. Yeah, the real temperature is

0:04:10.840 --> 0:04:13.560
<v Speaker 1>the real temperature, no matter who well look.

0:04:13.480 --> 0:04:14.560
<v Speaker 2>At no, no, but no.

0:04:14.600 --> 0:04:17.000
<v Speaker 7>But if it's all right it's sixty degrees but feels

0:04:17.000 --> 0:04:20.600
<v Speaker 7>like ninety, yes, you you want to dress for ninety yes, yeah, but.

0:04:20.560 --> 0:04:22.560
<v Speaker 3>It feels like it's actually better for you because you

0:04:22.600 --> 0:04:24.480
<v Speaker 3>want to know what it's going to feel like, so

0:04:24.520 --> 0:04:25.640
<v Speaker 3>you should know what to wear.

0:04:26.680 --> 0:04:27.960
<v Speaker 2>The actual temperature doesn't know what.

0:04:28.040 --> 0:04:29.800
<v Speaker 7>It actually make a difference if it's actually if it's

0:04:29.880 --> 0:04:31.160
<v Speaker 7>actually sixty.

0:04:30.880 --> 0:04:33.880
<v Speaker 1>Yeah, because I want to know if we've breaken up

0:04:33.880 --> 0:04:35.479
<v Speaker 1>broken any records today.

0:04:35.360 --> 0:04:39.479
<v Speaker 3>Okay, okay, that's different, that's what you're wearing, breaking records is.

0:04:42.560 --> 0:04:43.000
<v Speaker 7>Over here.

0:04:45.240 --> 0:04:48.800
<v Speaker 3>I have a map the historical data. I want to

0:04:48.800 --> 0:04:49.919
<v Speaker 3>make sure that you can assume we.

0:04:49.920 --> 0:04:57.400
<v Speaker 7>Are breaking a record every day.

0:04:58.640 --> 0:05:03.800
<v Speaker 3>So I talked to meteorologists at the Weather Company, okay,

0:05:03.839 --> 0:05:06.520
<v Speaker 3>which you may know for the Weather Channel brand.

0:05:07.000 --> 0:05:10.640
<v Speaker 4>So my name is doctor Loriana Gaudett. I am a

0:05:10.680 --> 0:05:15.000
<v Speaker 4>staff applied meteorological scientist at the Weather Company. I've worked

0:05:15.040 --> 0:05:19.599
<v Speaker 4>primarily within our forecast sciences team, so I'm not operationally

0:05:19.640 --> 0:05:23.039
<v Speaker 4>forecasting the weather, but i am working on the science

0:05:23.120 --> 0:05:25.920
<v Speaker 4>behind the scenes per se to improve our forecasts.

0:05:26.080 --> 0:05:27.919
<v Speaker 3>All right, So one of the first questions that we

0:05:28.040 --> 0:05:33.839
<v Speaker 3>got on weather is this idea of real feel. Right,

0:05:33.880 --> 0:05:36.640
<v Speaker 3>you get our actual temperature and then we get the

0:05:36.680 --> 0:05:38.600
<v Speaker 3>real field tamp. So can we start by just having

0:05:38.640 --> 0:05:40.880
<v Speaker 3>you break down what is the real field tamp? How

0:05:40.920 --> 0:05:41.720
<v Speaker 3>is that calculated?

0:05:42.240 --> 0:05:45.719
<v Speaker 4>So the real field temperature is more so known as

0:05:45.839 --> 0:05:50.240
<v Speaker 4>the feels like temperature, and what it's composed of is

0:05:50.360 --> 0:05:53.960
<v Speaker 4>a combination of the heat index and the windshiel temperature.

0:05:54.800 --> 0:05:59.440
<v Speaker 4>The heat index itself is a combination of the temperature

0:05:59.640 --> 0:06:04.400
<v Speaker 4>and the relative humidity and how those two interchangeably play

0:06:04.480 --> 0:06:08.560
<v Speaker 4>together to affect how we feel when we're outside. And

0:06:08.600 --> 0:06:11.840
<v Speaker 4>so if it's really humid outside, less of that sweat

0:06:11.960 --> 0:06:15.240
<v Speaker 4>is able to evaporate off of our bodies, and we

0:06:15.320 --> 0:06:18.799
<v Speaker 4>are less effectively cooling ourselves down, which makes it feel

0:06:18.920 --> 0:06:22.839
<v Speaker 4>much warmer. As an example, if it's ninety degrees fahrenheit

0:06:22.920 --> 0:06:26.960
<v Speaker 4>outside with a relative humidity of seventy percent, the heat

0:06:27.000 --> 0:06:30.240
<v Speaker 4>index or the feels like temperature in those conditions is

0:06:30.240 --> 0:06:33.640
<v Speaker 4>around one hundred and five degrees fahrenheit, which is very

0:06:33.680 --> 0:06:37.280
<v Speaker 4>warm and it can become dangerous with heat stress impacts.

0:06:37.600 --> 0:06:40.159
<v Speaker 4>And then on the other side of the temperature spectrum,

0:06:40.279 --> 0:06:43.080
<v Speaker 4>the feels like kind of points to the wind chill temperature.

0:06:43.560 --> 0:06:46.880
<v Speaker 4>So this time we're considering the effect of wind speed

0:06:47.120 --> 0:06:50.719
<v Speaker 4>on temperature, and the reason that that's important is because

0:06:50.760 --> 0:06:55.080
<v Speaker 4>the wind is effectively transporting the heat away from our body,

0:06:55.400 --> 0:06:58.640
<v Speaker 4>which is cooling down our body or our skin temperature,

0:06:58.680 --> 0:07:02.280
<v Speaker 4>and then over time core body temperature, which can also

0:07:02.360 --> 0:07:06.800
<v Speaker 4>come dangerous in its own way through frostbite or through

0:07:06.839 --> 0:07:10.960
<v Speaker 4>hypothermia effects. So another example here is that if you

0:07:10.960 --> 0:07:13.480
<v Speaker 4>have a temperature of thirty degrees fahrenheit and a wind

0:07:13.560 --> 0:07:16.600
<v Speaker 4>speed of fifteen miles an hour, your wind chill or

0:07:16.640 --> 0:07:20.760
<v Speaker 4>feels like temperature would be nineteen degrees fahrenheit, give or take.

0:07:30.080 --> 0:07:33.960
<v Speaker 1>Interesting. So basically like seventy degrees with no humidity feels

0:07:33.960 --> 0:07:36.920
<v Speaker 1>a lot different than seventy degrees with humidity, and some

0:07:37.160 --> 0:07:39.440
<v Speaker 1>you know, X amount of miles per hour.

0:07:39.280 --> 0:07:42.880
<v Speaker 3>Wind exactly to take away I got from talking to her,

0:07:42.920 --> 0:07:46.280
<v Speaker 3>it was like, the feels like takes into account how

0:07:46.400 --> 0:07:50.840
<v Speaker 3>the temperature affects our body, and it's not just all right,

0:07:50.880 --> 0:07:52.280
<v Speaker 3>here's the air temp.

0:07:52.560 --> 0:07:54.720
<v Speaker 7>Yeah, it's not so abstract. I guess it's like kind

0:07:54.720 --> 0:07:57.520
<v Speaker 7>of an algorithm basically. Yeah, and yeah, it's about how

0:07:58.240 --> 0:08:00.280
<v Speaker 7>you know your sweat's going to be a vap rated

0:08:00.360 --> 0:08:04.760
<v Speaker 7>or not or whatever. That's it's more thorough than I thought.

0:08:04.840 --> 0:08:06.800
<v Speaker 1>Yeah, I kind of thought. A scientist and a lab

0:08:06.840 --> 0:08:08.080
<v Speaker 1>coat walked outside, I was.

0:08:08.080 --> 0:08:12.840
<v Speaker 7>Like, okay, sixty five, Yeah, we wan'll make them feel

0:08:12.880 --> 0:08:13.280
<v Speaker 7>good today.

0:08:14.800 --> 0:08:17.760
<v Speaker 3>But something is interesting about feels like, which we talked

0:08:17.760 --> 0:08:20.280
<v Speaker 3>about a little bit already, is that someone like manny,

0:08:21.360 --> 0:08:27.000
<v Speaker 3>if it's seventy tract Yeah, if it's seventy seven degrees outside,

0:08:27.080 --> 0:08:28.240
<v Speaker 3>man's complaining as hot?

0:08:29.560 --> 0:08:32.880
<v Speaker 1>Yeah, well, not that it's hot, it's too It's like,

0:08:33.160 --> 0:08:34.520
<v Speaker 1>does it's warmer than I prefer?

0:08:34.559 --> 0:08:35.160
<v Speaker 7>It feels bad?

0:08:35.160 --> 0:08:39.840
<v Speaker 3>It feels bad, bad, whereas with us that's seventy seven

0:08:39.880 --> 0:08:41.320
<v Speaker 3>temperature bad, not bad.

0:08:41.440 --> 0:08:43.280
<v Speaker 7>So well, I.

0:08:43.200 --> 0:08:44.559
<v Speaker 2>Don't know, Okay, don't put that on that.

0:08:44.600 --> 0:08:46.440
<v Speaker 3>Okay, what do you what's what seventy seven.

0:08:46.200 --> 0:08:48.079
<v Speaker 7>Of you that could get pretty hot?

0:08:48.160 --> 0:08:48.400
<v Speaker 2>Okay?

0:08:48.720 --> 0:08:51.760
<v Speaker 7>Seventy three is comfy, okay, And I want a little

0:08:51.800 --> 0:08:52.640
<v Speaker 7>bit of clouds.

0:08:53.800 --> 0:08:57.400
<v Speaker 3>And speaking of shade versus sun, when they take the

0:08:57.480 --> 0:08:59.959
<v Speaker 3>temperature outside, did you know that they're taking into shade?

0:09:00.400 --> 0:09:03.040
<v Speaker 1>Whoa, oh, why is that?

0:09:03.200 --> 0:09:03.720
<v Speaker 7>I did not know.

0:09:04.040 --> 0:09:05.240
<v Speaker 2>Well, we're gonna find out.

0:09:06.400 --> 0:09:09.760
<v Speaker 4>So temperature and heat index are recorded in the shade,

0:09:10.320 --> 0:09:15.280
<v Speaker 4>and so if oh, yeah, what I know, Yes, it's

0:09:15.320 --> 0:09:18.480
<v Speaker 4>it's super surprising. But the reason is we don't want

0:09:18.520 --> 0:09:21.960
<v Speaker 4>the thermometer that's measuring the temperature to heat up and

0:09:22.040 --> 0:09:25.520
<v Speaker 4>not be able to actually tell us what the air

0:09:25.600 --> 0:09:28.880
<v Speaker 4>temperature is. We want that not the temperature with the thermometer.

0:09:29.559 --> 0:09:34.439
<v Speaker 4>So when you were outside doing whatever activity in the sun,

0:09:34.720 --> 0:09:37.360
<v Speaker 4>it's going to feel warmer than the reported air temperature

0:09:37.440 --> 0:09:39.760
<v Speaker 4>and even the heat index. So that's important to keep

0:09:39.800 --> 0:09:43.839
<v Speaker 4>in mind. And then the other component is that scientists

0:09:43.880 --> 0:09:48.000
<v Speaker 4>when they were deriving these heat indices and the wind chill,

0:09:48.400 --> 0:09:52.880
<v Speaker 4>they had to make certain approximations and assumptions. So some

0:09:52.960 --> 0:09:55.880
<v Speaker 4>of those involve like how tall are you, how much

0:09:55.920 --> 0:09:58.280
<v Speaker 4>do you weigh, how much do you sweat, what kind

0:09:58.280 --> 0:10:00.360
<v Speaker 4>of clothes are you're wearing, so on and so forth,

0:10:00.440 --> 0:10:04.280
<v Speaker 4>and that obviously can't account for each of our unique

0:10:04.760 --> 0:10:10.760
<v Speaker 4>body compositions and circumstances, but it's our best general approximation

0:10:11.280 --> 0:10:14.720
<v Speaker 4>for what you might experience when you walk out the door.

0:10:15.400 --> 0:10:18.280
<v Speaker 3>The shade thing really blew my mind because I'm every

0:10:18.280 --> 0:10:20.360
<v Speaker 3>time I go outside and I'm in the shade, I'm like, oh,

0:10:20.400 --> 0:10:23.520
<v Speaker 3>this is cooler than what's the app because I'm in

0:10:23.520 --> 0:10:27.800
<v Speaker 3>the shade. But that's the best case scenario. You're only

0:10:27.800 --> 0:10:32.560
<v Speaker 3>going to get hotter if it's ninety degrees. That means

0:10:32.600 --> 0:10:33.960
<v Speaker 3>if you're in the sun, it's hotter than that.

0:10:34.520 --> 0:10:38.079
<v Speaker 7>Yeah. Yeah, if you're walking around, you're gonna be sucked

0:10:38.080 --> 0:10:39.000
<v Speaker 7>there sometimes.

0:10:39.160 --> 0:10:39.880
<v Speaker 3>Yeah.

0:10:40.360 --> 0:10:42.800
<v Speaker 1>There's so many variables, which is why I just try

0:10:42.840 --> 0:10:46.040
<v Speaker 1>to distill them all into good or bad. Yeah.

0:10:46.040 --> 0:10:46.160
<v Speaker 3>I know.

0:10:46.320 --> 0:10:48.640
<v Speaker 7>Now I'm kind of like many systems well because it's like, well,

0:10:48.679 --> 0:10:55.679
<v Speaker 7>this makes me want them to have shade, Yeah, because

0:10:55.679 --> 0:10:56.240
<v Speaker 7>I need to know.

0:10:56.559 --> 0:10:58.440
<v Speaker 1>You open the weather app. It's just like an Excel

0:10:58.520 --> 0:10:59.120
<v Speaker 1>sph Yeah.

0:10:59.600 --> 0:11:02.200
<v Speaker 7>Ever dial in and then you dial in your outfit yeah,

0:11:02.280 --> 0:11:06.080
<v Speaker 7>and your skin tone calculator.

0:11:06.280 --> 0:11:06.640
<v Speaker 8>I mean.

0:11:09.000 --> 0:11:10.240
<v Speaker 7>Imagine you have an or a ring.

0:11:10.600 --> 0:11:13.080
<v Speaker 2>Yeah, that's that's a lot of data.

0:11:13.320 --> 0:11:13.920
<v Speaker 8>Yeah.

0:11:14.200 --> 0:11:16.600
<v Speaker 7>And then you didn't tell weather you take a selfie

0:11:17.040 --> 0:11:17.840
<v Speaker 7>it skins your clothes.

0:11:17.840 --> 0:11:19.600
<v Speaker 3>You don't even need to take a selfie, yeah, right,

0:11:19.679 --> 0:11:20.040
<v Speaker 3>your phone.

0:11:20.760 --> 0:11:23.840
<v Speaker 1>Yeah, and and you just exists and Peter Tiel buys

0:11:23.880 --> 0:11:25.800
<v Speaker 1>all of this data. Yeah, exactly, and then he but

0:11:25.840 --> 0:11:28.400
<v Speaker 1>he tells you it's going to be only seventy two today,

0:11:28.480 --> 0:11:30.040
<v Speaker 1>or it's only going to feel like seventy.

0:11:29.720 --> 0:11:32.040
<v Speaker 3>Two when we look at the weather app. Besides many

0:11:32.080 --> 0:11:35.000
<v Speaker 3>lying and saying he wants to look at historical data,

0:11:35.440 --> 0:11:37.520
<v Speaker 3>we're looking at it to see what we should wear

0:11:37.600 --> 0:11:39.760
<v Speaker 3>to go outside. Do I need to bring an umbrella?

0:11:39.840 --> 0:11:41.920
<v Speaker 3>Why don't we have this as the default? If I

0:11:41.960 --> 0:11:43.800
<v Speaker 3>open up the app, I want to see feels like

0:11:43.880 --> 0:11:45.400
<v Speaker 3>and then if I want to search for the actual

0:11:45.400 --> 0:11:47.480
<v Speaker 3>air temp, I could find that lower down.

0:11:47.480 --> 0:11:48.560
<v Speaker 2>Why are we doing the reverse?

0:11:52.800 --> 0:11:55.960
<v Speaker 4>We take a certain approach within our Weather Channel app,

0:11:56.520 --> 0:12:00.600
<v Speaker 4>and we've supply both temperatures, so not just the temperature,

0:12:00.679 --> 0:12:03.280
<v Speaker 4>but also the fields like temperature, so that you can

0:12:03.320 --> 0:12:06.600
<v Speaker 4>have both data points and use those to make decisions

0:12:06.640 --> 0:12:09.160
<v Speaker 4>about how you want to plan your day or go

0:12:09.200 --> 0:12:12.360
<v Speaker 4>about your day. But yeah, it's a really good question

0:12:12.559 --> 0:12:14.400
<v Speaker 4>because it gets down to the core of like the

0:12:14.480 --> 0:12:21.880
<v Speaker 4>human experience of course, but there's other impacts and implications

0:12:22.040 --> 0:12:26.079
<v Speaker 4>of the temperature that also don't relate to humans. So

0:12:26.320 --> 0:12:29.280
<v Speaker 4>some of those might be like if a farmer, for example,

0:12:29.440 --> 0:12:32.400
<v Speaker 4>is trying to figure out when to plant their crop

0:12:32.520 --> 0:12:35.720
<v Speaker 4>or protect their crop, they are looking at the actual temperature.

0:12:36.040 --> 0:12:39.480
<v Speaker 4>So that's what our weather forecast models are actually outputting,

0:12:39.600 --> 0:12:43.120
<v Speaker 4>is the real air temperature, and that's what we are

0:12:43.400 --> 0:12:47.440
<v Speaker 4>measuring and looking at when we are monitoring the climate,

0:12:47.480 --> 0:12:52.400
<v Speaker 4>for example, and it allows us to compare the observations

0:12:52.400 --> 0:12:58.079
<v Speaker 4>of temperature across the country, across the world, and over time. Whereas,

0:12:58.120 --> 0:13:00.800
<v Speaker 4>like with everything that we talked about with the feels

0:13:00.840 --> 0:13:04.520
<v Speaker 4>like temperature, there's a lot of approximations that are being used,

0:13:04.520 --> 0:13:09.880
<v Speaker 4>and so some weather services given the same environmental setup

0:13:10.160 --> 0:13:12.640
<v Speaker 4>might come up with different values. That makes it really

0:13:12.679 --> 0:13:17.520
<v Speaker 4>difficult for that inter comparison component. But if you yourself,

0:13:17.559 --> 0:13:21.040
<v Speaker 4>as the user of a weather app find that the

0:13:21.640 --> 0:13:24.120
<v Speaker 4>feels like temperature gives you everything that you need to

0:13:24.160 --> 0:13:27.559
<v Speaker 4>know you can set that as your own to fault temperature.

0:13:27.640 --> 0:13:29.800
<v Speaker 4>But we just don't want to make that assumption for

0:13:29.880 --> 0:13:30.880
<v Speaker 4>all of our users.

0:13:32.200 --> 0:13:35.840
<v Speaker 2>So they're just very considerate of me at this point.

0:13:36.600 --> 0:13:40.880
<v Speaker 3>The thing that impacts most of us would be it

0:13:40.880 --> 0:13:44.560
<v Speaker 3>feels like temperature that should be to default. Make everybody

0:13:44.559 --> 0:13:45.600
<v Speaker 3>else look for the other stuff.

0:13:45.640 --> 0:13:46.840
<v Speaker 1>Please contact your company.

0:13:47.160 --> 0:13:50.360
<v Speaker 3>I guess do you feel I understand all everything that

0:13:50.400 --> 0:13:53.080
<v Speaker 3>she said. When I'm looking at my app, I'm not

0:13:53.200 --> 0:13:57.040
<v Speaker 3>looking for climate. You know, over the last ten years,

0:13:57.080 --> 0:13:59.320
<v Speaker 3>I don't have any crops. I guess I can do

0:13:59.360 --> 0:14:01.199
<v Speaker 3>it within my own but I feel like as a

0:14:01.240 --> 0:14:04.839
<v Speaker 3>country we need to we neither do real feel I'm

0:14:04.840 --> 0:14:06.800
<v Speaker 3>not saying get rid of the real number. I'm just

0:14:06.800 --> 0:14:07.920
<v Speaker 3>saying put that lower.

0:14:08.360 --> 0:14:09.880
<v Speaker 7>See why I can't?

0:14:10.200 --> 0:14:11.480
<v Speaker 1>Why not just side by side?

0:14:11.679 --> 0:14:17.439
<v Speaker 7>Oh slash yeah, pretty much? Okay, big one, I mean,

0:14:17.640 --> 0:14:21.200
<v Speaker 7>pick whichever one you want, big one then basically an

0:14:21.320 --> 0:14:24.200
<v Speaker 7>arrow or slash, Yeah, basically, and you just know that

0:14:24.720 --> 0:14:27.480
<v Speaker 7>you just know, okay, this is you know, you know

0:14:27.640 --> 0:14:29.280
<v Speaker 7>the real thing. And here's the thing. It wouldn't take

0:14:29.320 --> 0:14:31.600
<v Speaker 7>up that much space. They're digits and like the numbers

0:14:31.600 --> 0:14:35.640
<v Speaker 7>are hopefully not Yeah, yeah, hopefully four digits. You're look

0:14:35.640 --> 0:14:36.120
<v Speaker 7>at that total.

0:14:36.360 --> 0:14:38.600
<v Speaker 1>I'm fine with the normal one. I'm fine with the

0:14:38.640 --> 0:14:39.480
<v Speaker 1>regular Yeah.

0:14:39.520 --> 0:14:42.520
<v Speaker 7>My main concern with these things is doing an umbrella

0:14:42.640 --> 0:14:44.280
<v Speaker 7>or not, which I forget to look for most of

0:14:44.320 --> 0:14:44.520
<v Speaker 7>the time.

0:14:44.560 --> 0:14:49.000
<v Speaker 3>Anymore, Speaking of rain, Manny, do you want to explain

0:14:49.080 --> 0:14:51.120
<v Speaker 3>this Twitter argument that people have been having.

0:14:54.920 --> 0:14:57.160
<v Speaker 1>When it's raining or when it might looks like it

0:14:57.240 --> 0:14:59.920
<v Speaker 1>might rain. You go on the app and says, let's say,

0:15:00.040 --> 0:15:05.000
<v Speaker 1>for example, thirty five percent. Doesn't say what the thirty

0:15:05.040 --> 0:15:07.040
<v Speaker 1>five percent is. So some people think that it's thirty

0:15:07.040 --> 0:15:09.680
<v Speaker 1>five percent chance it's going to rain where you're standing.

0:15:10.480 --> 0:15:14.480
<v Speaker 1>Other people think it's in a rain on thirty five

0:15:14.600 --> 0:15:19.080
<v Speaker 1>percent of the area around you, yes, and a third

0:15:19.080 --> 0:15:21.600
<v Speaker 1>group of people think that's effectively the same thing.

0:15:23.840 --> 0:15:25.640
<v Speaker 7>Well, well what do you what do you guys think?

0:15:26.280 --> 0:15:29.720
<v Speaker 3>Before I did this interview, Yeah, my thought was it's

0:15:29.720 --> 0:15:32.160
<v Speaker 3>a thirty five percent chance it's going to rain.

0:15:32.280 --> 0:15:34.400
<v Speaker 7>That's not that's my thought too, because the area doesn't

0:15:34.400 --> 0:15:36.200
<v Speaker 7>make because it's like, well, what's what area?

0:15:36.320 --> 0:15:38.640
<v Speaker 1>A lot of people, a lot of people online, these

0:15:38.640 --> 0:15:40.800
<v Speaker 1>are not experts, but they were like, no, that is

0:15:40.840 --> 0:15:42.800
<v Speaker 1>what they're telling you. Well, what did you think I

0:15:42.920 --> 0:15:44.520
<v Speaker 1>was thought, thirty five percent chance is going to rain.

0:15:44.560 --> 0:15:47.800
<v Speaker 7>Chance, Yeah, where you are? I agree, That's what I'm

0:15:47.800 --> 0:15:49.880
<v Speaker 7>looking at, and that's how I feel like my lived

0:15:49.920 --> 0:15:51.040
<v Speaker 7>experience is.

0:15:51.240 --> 0:15:53.800
<v Speaker 1>You know, it's like, well, that's where it gets tricky.

0:15:53.880 --> 0:15:55.840
<v Speaker 1>It's it's never right to me.

0:15:56.200 --> 0:15:58.920
<v Speaker 7>But yeah, I always assumed it's basically there is a

0:15:58.960 --> 0:16:04.520
<v Speaker 7>percentage of chance that it will rain. Not whatever area

0:16:04.720 --> 0:16:07.280
<v Speaker 7>I'm taking in, it's going to cover sixty percent of this.

0:16:07.480 --> 0:16:08.360
<v Speaker 3>Yeah, yeah, that.

0:16:08.280 --> 0:16:10.840
<v Speaker 7>Doesn't really that would never cross our behind me that much.

0:16:12.920 --> 0:16:16.840
<v Speaker 4>So this is a common area of confusion for users,

0:16:16.880 --> 0:16:20.360
<v Speaker 4>and even in our own field of meteorology, it can

0:16:20.400 --> 0:16:24.320
<v Speaker 4>be really hard to pinpoint what we are actually communicating

0:16:24.400 --> 0:16:29.360
<v Speaker 4>with probability of precipitation or pop In my experience and

0:16:29.440 --> 0:16:33.560
<v Speaker 4>knowledge base, I think both of those interpretations are true

0:16:33.720 --> 0:16:37.120
<v Speaker 4>in their own right, which of course makes it even

0:16:37.240 --> 0:16:40.920
<v Speaker 4>more confusing. But I can I can share from the

0:16:40.960 --> 0:16:45.320
<v Speaker 4>Weather Channel app perspective, the way that we're communicating it

0:16:45.360 --> 0:16:50.000
<v Speaker 4>is really in your surrounding area. What is the likelihood

0:16:50.240 --> 0:16:55.360
<v Speaker 4>of precipitation or of rain impacting you within whatever time

0:16:55.440 --> 0:16:59.400
<v Speaker 4>frame you're interested in, So, whether it's today, the next hour,

0:17:00.120 --> 0:17:05.440
<v Speaker 4>fifteen minutes, and less so the amount of area that

0:17:05.640 --> 0:17:08.920
<v Speaker 4>is going to be impacted. A couple misconceptions that also

0:17:08.920 --> 0:17:13.879
<v Speaker 4>come up to are about the intensity of precipitation from pop.

0:17:14.119 --> 0:17:17.320
<v Speaker 4>So sometimes people will see like, oh, there's a ninety

0:17:17.320 --> 0:17:20.320
<v Speaker 4>percent chance of rain, it's going to be a downpour.

0:17:21.000 --> 0:17:26.280
<v Speaker 4>We are indicating the likelihood of rain, of measurable rain,

0:17:26.520 --> 0:17:29.679
<v Speaker 4>any rain, and so generally it has nothing to do

0:17:29.760 --> 0:17:32.520
<v Speaker 4>with the intensity of that precipitation, which is important to

0:17:32.600 --> 0:17:35.880
<v Speaker 4>keep in mind. And then the other component two is

0:17:36.200 --> 0:17:39.639
<v Speaker 4>you know, sometimes people think, Okay, there's a fifty percent

0:17:39.720 --> 0:17:42.080
<v Speaker 4>chance of pop in New York City, so only half

0:17:42.119 --> 0:17:45.080
<v Speaker 4>of the day will be wet, And again you could

0:17:45.080 --> 0:17:47.639
<v Speaker 4>have that fifty percent chance, there might only be a

0:17:47.640 --> 0:17:49.800
<v Speaker 4>couple hours that are impacted, and then you have a

0:17:49.840 --> 0:17:53.320
<v Speaker 4>beautiful remainder of the day. I think that it really

0:17:53.400 --> 0:17:58.120
<v Speaker 4>lays on us meteorologists to make sure that we're communicating

0:17:58.680 --> 0:18:03.240
<v Speaker 4>what that likely hood and probability means, especially if it

0:18:03.280 --> 0:18:06.800
<v Speaker 4>does vary, you know, from a news broadcaster or a

0:18:06.840 --> 0:18:09.920
<v Speaker 4>meteorologist who's on TV trying to communicate the likelihood of rain,

0:18:10.040 --> 0:18:12.800
<v Speaker 4>to a push alert from your weather app telling you

0:18:12.840 --> 0:18:15.600
<v Speaker 4>that there's rain coming within the next thirty minutes.

0:18:17.600 --> 0:18:21.800
<v Speaker 1>That is really funny because the idea that the percent

0:18:21.920 --> 0:18:26.639
<v Speaker 1>chance is the total coverage is such a like, actually,

0:18:26.800 --> 0:18:29.600
<v Speaker 1>I'm smart, and this is what they're really saying, fools

0:18:29.600 --> 0:18:32.000
<v Speaker 1>in conversation. I've heard it so many times and it's

0:18:32.040 --> 0:18:32.520
<v Speaker 1>just wrong.

0:18:32.720 --> 0:18:35.480
<v Speaker 7>And then I mean it's kind of fascinating, like people

0:18:35.520 --> 0:18:37.840
<v Speaker 7>are just taking this and twisting it in any direction

0:18:37.880 --> 0:18:40.359
<v Speaker 7>where it's like, okay, ten percent, that's ten percent of

0:18:40.400 --> 0:18:44.480
<v Speaker 7>the day. Yeah, so yeah, okay, so whatever ten percent

0:18:44.520 --> 0:18:47.240
<v Speaker 7>of twenty four hours is. It's like, yeah, thinking of

0:18:47.280 --> 0:18:49.280
<v Speaker 7>all the different ways to map it out, it's kind

0:18:49.320 --> 0:18:51.639
<v Speaker 7>of that's actually like a SAT question or something.

0:18:51.720 --> 0:18:53.480
<v Speaker 1>Yeah, I heard the rain is only coming from ten

0:18:53.520 --> 0:18:54.400
<v Speaker 1>percent of the clouds.

0:18:54.520 --> 0:18:57.520
<v Speaker 2>Yeah, exactly. Yeah, but there.

0:18:57.840 --> 0:18:59.719
<v Speaker 3>I thought it was interesting that they're kind of they

0:18:59.720 --> 0:19:02.080
<v Speaker 3>could both be right depending on your weather.

0:19:02.280 --> 0:19:03.480
<v Speaker 7>You need explanation.

0:19:03.840 --> 0:19:05.520
<v Speaker 2>I mean, I think that you know, the apps that

0:19:05.560 --> 0:19:06.639
<v Speaker 2>we're looking at or telling us, I.

0:19:07.600 --> 0:19:13.440
<v Speaker 7>Would hope so frankly, I think that you know, maybe

0:19:13.480 --> 0:19:15.439
<v Speaker 7>they could do a better job than of getting the

0:19:15.440 --> 0:19:17.600
<v Speaker 7>word out there hopefully. You know, we're going to do

0:19:17.600 --> 0:19:21.080
<v Speaker 7>our part today with our you know, hundreds of thousands

0:19:21.080 --> 0:19:21.680
<v Speaker 7>of listeners.

0:19:22.800 --> 0:19:28.200
<v Speaker 3>Some would say millions, So yeah, you could argue that millions.

0:19:28.240 --> 0:19:32.040
<v Speaker 3>Maybe all right, we are going to take a quick

0:19:32.160 --> 0:19:34.520
<v Speaker 3>break and when we get back, we are going to

0:19:34.600 --> 0:19:39.560
<v Speaker 3>find out are the weather apps actually getting worse? And

0:19:40.119 --> 0:19:51.360
<v Speaker 3>it's Trump to blame. So in last week's mail bag,

0:19:51.359 --> 0:19:54.000
<v Speaker 3>we were debating who gets the right of way between

0:19:54.119 --> 0:19:56.720
<v Speaker 3>a school bus with the stop sign out, an ambulance

0:19:56.800 --> 0:20:00.399
<v Speaker 3>with the siren on, and a funeral procession, and from

0:20:00.400 --> 0:20:02.359
<v Speaker 3>North Carolina called in with this insight.

0:20:02.640 --> 0:20:06.919
<v Speaker 9>I am a state wide law enforcement officer here in

0:20:06.920 --> 0:20:12.480
<v Speaker 9>North Carolina. If I am running lights and sirens, I

0:20:12.560 --> 0:20:13.960
<v Speaker 9>am allowed.

0:20:13.400 --> 0:20:15.119
<v Speaker 10>To go through a soft sign.

0:20:15.760 --> 0:20:19.879
<v Speaker 9>People legally have to yield to me. But if I

0:20:19.960 --> 0:20:23.040
<v Speaker 9>run a soft sign and hit someone, it is still

0:20:23.119 --> 0:20:26.640
<v Speaker 9>my fault, and I, as a driver, would.

0:20:26.520 --> 0:20:30.600
<v Speaker 10>Not only be responsible to my agency, but I could

0:20:30.680 --> 0:20:37.720
<v Speaker 10>also be personally legally financially responsible funeral processions.

0:20:37.760 --> 0:20:39.560
<v Speaker 9>You guys are correct, that is a courtesy.

0:20:39.600 --> 0:20:41.280
<v Speaker 10>It's not a legal thing, and but it is it

0:20:41.359 --> 0:20:41.760
<v Speaker 10>drive me.

0:20:41.720 --> 0:20:44.120
<v Speaker 9>Grace to get down here in the South, they love

0:20:44.160 --> 0:20:45.440
<v Speaker 9>them at funeral profession.

0:20:45.840 --> 0:20:48.520
<v Speaker 3>So we're going to try to include more listener responses

0:20:48.840 --> 0:20:51.879
<v Speaker 3>to our episodes like this in the future, So you

0:20:51.880 --> 0:20:55.760
<v Speaker 3>can email us at Manny Noladevin at gmail dot com

0:20:56.080 --> 0:20:58.359
<v Speaker 3>or leave us a voicemail at the number in our

0:20:58.400 --> 0:21:00.560
<v Speaker 3>show notes and hey, you may includes you in a

0:21:00.560 --> 0:21:03.960
<v Speaker 3>future episode. All right, let's get back to the show.

0:21:08.520 --> 0:21:13.520
<v Speaker 3>We do have one final weather question from Mia.

0:21:15.040 --> 0:21:18.159
<v Speaker 11>I have a question, and this is just bugging me

0:21:18.320 --> 0:21:24.960
<v Speaker 11>so much, especially this summer, our weather apps getting less

0:21:25.119 --> 0:21:31.440
<v Speaker 11>accurate because I feel like they are like these days,

0:21:32.280 --> 0:21:34.359
<v Speaker 11>I just don't feel like I can trust the weather

0:21:34.400 --> 0:21:37.720
<v Speaker 11>app to tell me exactly what's going to happen, specifically

0:21:37.760 --> 0:21:40.880
<v Speaker 11>if it's going to rain, like over this the course

0:21:40.880 --> 0:21:43.040
<v Speaker 11>of the summer, It's been a rainy summer in New York,

0:21:43.640 --> 0:21:45.840
<v Speaker 11>and now I feel like I'm becoming this kind of

0:21:45.880 --> 0:21:48.800
<v Speaker 11>like medieval farmer where I'm sort of gauging what's happening

0:21:48.800 --> 0:21:51.560
<v Speaker 11>in the sky, and I feel like I am becoming

0:21:51.600 --> 0:21:54.679
<v Speaker 11>a much better predictor of what's actually going to happen

0:21:55.040 --> 0:21:57.560
<v Speaker 11>than what my phone is telling me. I'm just starting

0:21:57.600 --> 0:22:02.720
<v Speaker 11>to be like, what's big weather even there? So if

0:22:02.720 --> 0:22:06.040
<v Speaker 11>you could answer for me, is it getting less accurate?

0:22:06.320 --> 0:22:08.960
<v Speaker 11>What's the reason should I trust this app anymore?

0:22:09.520 --> 0:22:10.560
<v Speaker 4>That would be great. Thank you.

0:22:14.119 --> 0:22:16.960
<v Speaker 2>I put this question to our meteorologists from the weather.

0:22:17.280 --> 0:22:18.560
<v Speaker 7>She was sweam bullets at this one.

0:22:19.880 --> 0:22:22.479
<v Speaker 3>Is the weather more unpredictable or is this on in

0:22:22.480 --> 0:22:25.320
<v Speaker 3>our heads? And you know, has nothing really changed.

0:22:26.600 --> 0:22:31.280
<v Speaker 4>So that's a super intriguing question. No, as a short answer,

0:22:31.640 --> 0:22:34.879
<v Speaker 4>the aps are not getting worse at predicting rain. I

0:22:34.880 --> 0:22:37.200
<v Speaker 4>think there's a there's a few different things at play here,

0:22:37.440 --> 0:22:41.800
<v Speaker 4>one of which you pointed at. It's psychological, so we're

0:22:41.880 --> 0:22:45.680
<v Speaker 4>more likely to remember when the weather apps get it wrong,

0:22:45.960 --> 0:22:49.119
<v Speaker 4>versus that when we are seeing a prediction of, oh,

0:22:49.160 --> 0:22:51.040
<v Speaker 4>it's going to rain in ten minutes, let me make

0:22:51.040 --> 0:22:53.160
<v Speaker 4>sure I grab my rain jacket before I go out,

0:22:53.520 --> 0:22:56.080
<v Speaker 4>and it ends up being correct, and so you're prepared.

0:22:56.280 --> 0:22:58.879
<v Speaker 4>It becomes a non event and you forget about it.

0:22:59.320 --> 0:23:03.360
<v Speaker 4>But let's say that if someone is outside it starts pouring,

0:23:03.440 --> 0:23:06.280
<v Speaker 4>there's absolutely no warning. Of course, you're going to be

0:23:06.280 --> 0:23:09.760
<v Speaker 4>annoyed that you had no notice that that was going

0:23:09.800 --> 0:23:14.440
<v Speaker 4>to happen. And there's a few reasons that those specific

0:23:14.520 --> 0:23:20.440
<v Speaker 4>circumstances can crop up. This example of stepping outside and

0:23:21.119 --> 0:23:26.880
<v Speaker 4>being met with an unexpected downpour of rain can largely

0:23:26.960 --> 0:23:30.280
<v Speaker 4>happen because even if the radar is able to pick

0:23:30.359 --> 0:23:32.679
<v Speaker 4>up on a storm let's say it just started raining

0:23:32.680 --> 0:23:35.760
<v Speaker 4>within the past few minutes. The weather radar just got

0:23:35.760 --> 0:23:38.679
<v Speaker 4>that data. So for example, that data needs to be

0:23:39.320 --> 0:23:42.920
<v Speaker 4>ingested into our back end systems or any other weather

0:23:43.000 --> 0:23:46.639
<v Speaker 4>app systems to process that data, figure out where that

0:23:46.720 --> 0:23:51.800
<v Speaker 4>storm is using proprietary software and algorithms, predict where that

0:23:51.840 --> 0:23:55.879
<v Speaker 4>storm is headed and if it will intensify or again dissipate,

0:23:56.520 --> 0:24:01.280
<v Speaker 4>get that forecast to our technology system downstream, and then

0:24:01.400 --> 0:24:04.639
<v Speaker 4>those then deliver that information to your app. So that

0:24:04.760 --> 0:24:08.040
<v Speaker 4>takes a bit of wall clock time for all of

0:24:08.040 --> 0:24:12.080
<v Speaker 4>that process to happen. So unfortunately, there are those situations

0:24:12.160 --> 0:24:16.359
<v Speaker 4>where rain can impact you within that window of time

0:24:16.400 --> 0:24:18.800
<v Speaker 4>that we're trying to get that information to you as

0:24:18.840 --> 0:24:23.800
<v Speaker 4>fast as possible, but perhaps missed that window of opportunity.

0:24:24.160 --> 0:24:27.000
<v Speaker 1>I've never thought about a situation where the weather app

0:24:27.119 --> 0:24:30.200
<v Speaker 1>was wrong, because it just was like trying to catch

0:24:30.280 --> 0:24:32.960
<v Speaker 1>up to the real time m hm. You would think.

0:24:34.359 --> 0:24:37.640
<v Speaker 3>You're supposed to be predicting.

0:24:37.960 --> 0:24:41.040
<v Speaker 7>It's like, don't blame me, I'm not the weather company.

0:24:41.119 --> 0:24:41.399
<v Speaker 3>Hello.

0:24:41.960 --> 0:24:45.000
<v Speaker 1>And now that I remember what Mia was complaining about,

0:24:45.000 --> 0:24:48.280
<v Speaker 1>I think her concern is that the apps are more

0:24:49.080 --> 0:24:53.120
<v Speaker 1>frequently incorrect, not that they're ever incorrect, but that it's

0:24:53.160 --> 0:24:54.200
<v Speaker 1>happening more often.

0:24:55.280 --> 0:24:58.359
<v Speaker 3>Yes, yeah, she thinks it's getting the apps are getting worse.

0:24:58.640 --> 0:25:04.080
<v Speaker 3>So the Weather Company said, no, that's you know, the

0:25:04.160 --> 0:25:06.879
<v Speaker 3>apps aren't getting worse, but they work at the Weather Company.

0:25:06.960 --> 0:25:10.720
<v Speaker 3>So I wanted to call up someone who can maybe

0:25:10.720 --> 0:25:13.280
<v Speaker 3>speak a bit more freely about whether or not these

0:25:13.320 --> 0:25:16.000
<v Speaker 3>apps are getting worse and do we need to worry,

0:25:16.080 --> 0:25:18.199
<v Speaker 3>especially with these Doge cuts, about them being worse in

0:25:18.240 --> 0:25:18.679
<v Speaker 3>the future.

0:25:18.720 --> 0:25:20.440
<v Speaker 2>So I called the Mary Glacken.

0:25:21.480 --> 0:25:27.040
<v Speaker 12>I'm the former deputy undersecretary for NOAH for operations there

0:25:27.080 --> 0:25:29.320
<v Speaker 12>and I had worked for Noah for just about thirty

0:25:29.320 --> 0:25:34.320
<v Speaker 12>five years. I also am on an AI board and

0:25:34.359 --> 0:25:38.280
<v Speaker 12>things like that, so today these days I'm mainly in

0:25:38.320 --> 0:25:39.800
<v Speaker 12>an advisory capacity.

0:25:40.240 --> 0:25:43.160
<v Speaker 2>She also worked at the Weather Company back in the day.

0:25:43.560 --> 0:25:45.320
<v Speaker 3>All right, great.

0:25:45.160 --> 0:25:46.400
<v Speaker 7>Job finding, Mary.

0:25:46.920 --> 0:25:49.680
<v Speaker 1>I always have stuff to say about my former employees.

0:25:50.440 --> 0:25:51.240
<v Speaker 1>It should be good to take.

0:25:52.280 --> 0:25:54.800
<v Speaker 3>So, you know, the big thing that we were concerned

0:25:54.800 --> 0:25:58.080
<v Speaker 3>about and seeing the headlines is that with the Doge cuts,

0:25:59.160 --> 0:26:02.800
<v Speaker 3>that there's just less people working, which is why the

0:26:02.840 --> 0:26:05.200
<v Speaker 3>apps are getting worse. So I asked Mary, like, where

0:26:05.200 --> 0:26:06.520
<v Speaker 3>do we currently stand.

0:26:06.960 --> 0:26:09.800
<v Speaker 12>So let me talk about it in terms of personnel first,

0:26:10.560 --> 0:26:14.240
<v Speaker 12>because one of the major things that happened was the exodus.

0:26:14.280 --> 0:26:15.720
<v Speaker 12>You know, there was the Fork in the.

0:26:15.720 --> 0:26:20.760
<v Speaker 13>Road, another unprecedented action from the Trump administration, offering more

0:26:20.800 --> 0:26:24.199
<v Speaker 13>than two million federal workers a buyout. The workers receiving

0:26:24.240 --> 0:26:26.520
<v Speaker 13>an email with the subject line fork in the Road,

0:26:26.640 --> 0:26:29.679
<v Speaker 13>giving them a choice resign and be paid through September

0:26:30.080 --> 0:26:31.240
<v Speaker 13>or risk being fired.

0:26:31.680 --> 0:26:35.240
<v Speaker 12>So the National Weather Service and all of Noah are

0:26:35.359 --> 0:26:40.520
<v Speaker 12>down significantly in terms of people, something approaching as much

0:26:40.520 --> 0:26:44.720
<v Speaker 12>as twenty percent in some locations. So the National Weather

0:26:44.840 --> 0:26:48.639
<v Speaker 12>Service did lose a lot of senior people. In terms

0:26:48.640 --> 0:26:52.639
<v Speaker 12>of funding, they had actually been funded by Congress last

0:26:52.720 --> 0:26:56.679
<v Speaker 12>year for a full year at a reasonable level, but

0:26:56.880 --> 0:27:01.119
<v Speaker 12>the Trump administration has delayed spending of those funds, so

0:27:01.240 --> 0:27:04.679
<v Speaker 12>they've really been slow rolling contracts to go out for

0:27:04.840 --> 0:27:08.400
<v Speaker 12>various things. I don't have any figures here, but it's

0:27:08.400 --> 0:27:10.840
<v Speaker 12>safe to assume there's a fair amount of money still

0:27:10.880 --> 0:27:14.360
<v Speaker 12>on the table. But the direction that we saw this

0:27:14.440 --> 0:27:17.639
<v Speaker 12>week was a spend plan for the rest of this

0:27:17.760 --> 0:27:21.360
<v Speaker 12>fiscal year is clawing back that money. It's saying you're

0:27:21.400 --> 0:27:25.560
<v Speaker 12>not allowed to spend that anymore. So that's that's kind

0:27:25.600 --> 0:27:29.399
<v Speaker 12>of where we are. We've seen some news about them hiring.

0:27:29.359 --> 0:27:32.520
<v Speaker 5>So earlier this year, President Trump's Doze Office cut more

0:27:32.560 --> 0:27:36.480
<v Speaker 5>than five hundred Weather employees. Well now WS says they're

0:27:36.480 --> 0:27:39.520
<v Speaker 5>going to hire four hundred and fifty meteorologists, hydrologists, and

0:27:39.680 --> 0:27:40.720
<v Speaker 5>radar technicians.

0:27:41.040 --> 0:27:45.119
<v Speaker 12>They're all entry level positions, So you know you're not

0:27:45.200 --> 0:27:49.760
<v Speaker 12>going to hire back the expertise that's been lost that

0:27:50.480 --> 0:27:53.840
<v Speaker 12>one of the senior officials that Noah career official had quoted,

0:27:53.880 --> 0:27:57.399
<v Speaker 12>that was twenty seven thousand years of expertise that walked

0:27:57.400 --> 0:28:00.720
<v Speaker 12>out the door between February in April.

0:28:02.920 --> 0:28:04.439
<v Speaker 3>It's just going to be a lot of people, a

0:28:04.440 --> 0:28:07.919
<v Speaker 3>lot of college who don't have the expertise, and now

0:28:07.960 --> 0:28:10.600
<v Speaker 3>they also don't have the leadership to mentor those people.

0:28:10.960 --> 0:28:14.200
<v Speaker 1>They just went from an NFL team to like JV

0:28:14.359 --> 0:28:18.000
<v Speaker 1>high school team.

0:28:18.320 --> 0:28:20.520
<v Speaker 3>So I wanted Mary to answer the question because I

0:28:20.520 --> 0:28:22.880
<v Speaker 3>couldn't take the Weather Company's word for it.

0:28:22.960 --> 0:28:24.600
<v Speaker 2>Are the apps getting worse?

0:28:24.720 --> 0:28:27.879
<v Speaker 12>The apps haven't degraded at all. I think the worries

0:28:27.960 --> 0:28:32.400
<v Speaker 12>that we have with the Trump administration is if they

0:28:32.440 --> 0:28:35.680
<v Speaker 12>move forward with their plans. Literally one of the plans

0:28:35.760 --> 0:28:41.200
<v Speaker 12>is to eliminate all of Noah's research arm So and

0:28:41.240 --> 0:28:44.360
<v Speaker 12>that's all our future. You know, how do we do

0:28:44.400 --> 0:28:48.800
<v Speaker 12>a better job in forecasting that whole section would be eliminated?

0:28:49.280 --> 0:28:53.520
<v Speaker 12>Which is crazy, but that's the plan. I do want

0:28:53.520 --> 0:28:57.240
<v Speaker 12>to kind of remind folks that Congress has a say

0:28:57.240 --> 0:29:00.040
<v Speaker 12>in this whole thing. Both the House and Senate that

0:29:00.680 --> 0:29:03.720
<v Speaker 12>have given their plan on how Noah would be funded.

0:29:04.200 --> 0:29:06.880
<v Speaker 12>The Senate does a really pretty good job and keeping

0:29:06.920 --> 0:29:12.040
<v Speaker 12>Noah funded. The House has some significant cuts in it,

0:29:12.080 --> 0:29:15.560
<v Speaker 12>but nothing as draconian as the administration is asking for.

0:29:16.360 --> 0:29:19.240
<v Speaker 12>I think the problem is that Congress won't be able

0:29:19.360 --> 0:29:24.160
<v Speaker 12>to agree on the overall spending, which will really basically

0:29:24.160 --> 0:29:27.320
<v Speaker 12>allow the Trump administration to continue to do what it

0:29:27.360 --> 0:29:28.040
<v Speaker 12>wants to do.

0:29:29.000 --> 0:29:32.160
<v Speaker 3>I was curious if we've kind of hit the point

0:29:32.200 --> 0:29:36.400
<v Speaker 3>of no return, you know, see if President Biden runs

0:29:36.440 --> 0:29:37.280
<v Speaker 3>again and.

0:29:37.280 --> 0:29:45.800
<v Speaker 2>Wins, yeah, you know which, we're in eight can we

0:29:46.040 --> 0:29:47.320
<v Speaker 2>get back to where we were?

0:29:52.240 --> 0:29:54.400
<v Speaker 12>One of the things I'd like to make clear with

0:29:54.560 --> 0:29:56.840
<v Speaker 12>you know, all of my experience with Noah, both in

0:29:56.960 --> 0:30:00.560
<v Speaker 12>Noah and then working with Noah outside is I would

0:30:00.560 --> 0:30:03.400
<v Speaker 12>not be the one arguing for status quo. You know,

0:30:03.600 --> 0:30:06.040
<v Speaker 12>I'm not here saying oh, it was a perfect world

0:30:06.080 --> 0:30:08.520
<v Speaker 12>and now this has happened. I think it will be

0:30:08.680 --> 0:30:11.600
<v Speaker 12>possible to get us back if we can keep people

0:30:11.720 --> 0:30:14.840
<v Speaker 12>in the field and interested in our problems. You know,

0:30:14.880 --> 0:30:19.080
<v Speaker 12>you have the whole advent of AI, and AI is

0:30:19.160 --> 0:30:22.240
<v Speaker 12>impacting our value chain all the way from taking an

0:30:22.240 --> 0:30:27.680
<v Speaker 12>observation to helping somebody make a decision on what to

0:30:27.760 --> 0:30:31.800
<v Speaker 12>do that day. So when I look at AI, it's

0:30:31.800 --> 0:30:35.400
<v Speaker 12>pretty clear to me and many is the private sector

0:30:35.480 --> 0:30:38.280
<v Speaker 12>is ahead of where Noah is with AI, and that's

0:30:38.320 --> 0:30:40.800
<v Speaker 12>no great chock. You know, the private sector can pay

0:30:40.840 --> 0:30:43.560
<v Speaker 12>somebody a half a million a year because they're a

0:30:43.600 --> 0:30:46.440
<v Speaker 12>genius in AI. You know, if you go to nowhere,

0:30:46.440 --> 0:30:49.400
<v Speaker 12>you're going to be making ninety thousand. So that says

0:30:49.440 --> 0:30:52.360
<v Speaker 12>to me that we need to find a way to

0:30:52.400 --> 0:30:57.680
<v Speaker 12>work with the private sector that meets public good. You know,

0:30:57.800 --> 0:31:00.920
<v Speaker 12>how do we ensure that everybody gets warning that they

0:31:00.960 --> 0:31:04.920
<v Speaker 12>need and how do we ensure people get the basic information.

0:31:05.400 --> 0:31:05.959
<v Speaker 3>To do that?

0:31:06.280 --> 0:31:10.000
<v Speaker 12>So I do think we need to think more creatively

0:31:10.080 --> 0:31:13.800
<v Speaker 12>about public private partnerships. You know, right now, there's not

0:31:13.880 --> 0:31:16.840
<v Speaker 12>a lot of mechanisms for the private sector to work

0:31:16.880 --> 0:31:20.640
<v Speaker 12>with the government sector. And I think if we you know,

0:31:20.680 --> 0:31:24.320
<v Speaker 12>if we started rebuilding tomorrow I think that's what we

0:31:24.360 --> 0:31:27.360
<v Speaker 12>would be thinking about, Well, what really makes sense here

0:31:27.840 --> 0:31:29.400
<v Speaker 12>to do in the future.

0:31:32.480 --> 0:31:35.160
<v Speaker 1>Yeah, I'm like, I'm like your run of the mill

0:31:35.360 --> 0:31:38.360
<v Speaker 1>kind of lefty, right, who has some skepticism about what

0:31:38.400 --> 0:31:40.760
<v Speaker 1>the private sector can do, like for the good of

0:31:40.800 --> 0:31:44.040
<v Speaker 1>the people, quote unquote. But it's interesting how this situation

0:31:44.160 --> 0:31:45.960
<v Speaker 1>is so die or that, like we do just kind

0:31:45.960 --> 0:31:46.760
<v Speaker 1>of have to look at it.

0:31:47.400 --> 0:31:47.480
<v Speaker 10>All.

0:31:47.600 --> 0:31:49.760
<v Speaker 3>Right, So we've been, you know, trying to make sense

0:31:49.760 --> 0:31:52.880
<v Speaker 3>of the world through weather. We're going to take a

0:31:52.920 --> 0:31:54.640
<v Speaker 3>little break. I'm going to leave you guys, and then

0:31:54.640 --> 0:31:56.280
<v Speaker 3>we're going to try to make sense of the world

0:31:56.760 --> 0:32:13.680
<v Speaker 3>through Spotify's shuffle feature. This is Devin, Welcome back to

0:32:13.760 --> 0:32:17.560
<v Speaker 3>no such thing. A few weeks ago, actually, we got

0:32:17.600 --> 0:32:22.280
<v Speaker 3>an email from this listener named Austin. He wrote, after

0:32:22.400 --> 0:32:25.240
<v Speaker 3>listening to your latest mail Bag episode, it got me

0:32:25.280 --> 0:32:27.680
<v Speaker 3>thinking about an issue I've run into over the years.

0:32:28.160 --> 0:32:31.240
<v Speaker 3>Whenever I hit shuffle play for a music playlist on Spotify,

0:32:31.600 --> 0:32:36.440
<v Speaker 3>the shuffle feature never seems to be truly random. I

0:32:36.480 --> 0:32:39.000
<v Speaker 3>want to know how does shuffle work for music apps

0:32:39.200 --> 0:32:45.120
<v Speaker 3>and is it truly random.

0:32:45.360 --> 0:32:51.760
<v Speaker 8>I'm Heather mccoldon and I'm a writer, artist, and sometimes

0:32:51.800 --> 0:32:52.840
<v Speaker 8>a tarot reader.

0:32:53.400 --> 0:32:55.840
<v Speaker 3>All right, So I reached out because we got a

0:32:55.960 --> 0:33:00.640
<v Speaker 3>question from a listener who wanted to know if we

0:33:00.640 --> 0:33:04.880
<v Speaker 3>could figure out how Spotify's shuffle feature works. And I

0:33:04.920 --> 0:33:08.040
<v Speaker 3>came across your article in the Financial Times cool in

0:33:08.080 --> 0:33:12.280
<v Speaker 3>which you dive into this. Would you mind, I guess

0:33:12.360 --> 0:33:16.720
<v Speaker 3>kind of setting the scene for me on what happened

0:33:16.760 --> 0:33:20.200
<v Speaker 3>on December fifteenth, let's say, twenty twenty three.

0:33:20.520 --> 0:33:23.240
<v Speaker 2>Yeah, when all these random acts started coming together.

0:33:26.720 --> 0:33:29.440
<v Speaker 8>Yeah, basically, you know, it's like one of those things.

0:33:29.560 --> 0:33:36.360
<v Speaker 8>It's like holiday time, Brooklyn, like the aras chilled. Everyone's

0:33:36.440 --> 0:33:38.920
<v Speaker 8>excited and happy for like the end of the year

0:33:39.080 --> 0:33:42.080
<v Speaker 8>beginning of the new year. I was visiting some friends

0:33:42.120 --> 0:33:47.000
<v Speaker 8>at a dinner party in Williamsburg and you know, too

0:33:47.120 --> 0:33:51.880
<v Speaker 8>much wine, too much festivities, like everyone leaves on masks

0:33:51.920 --> 0:33:55.360
<v Speaker 8>to go home, and yeah, I was feeling like kind

0:33:55.400 --> 0:33:59.760
<v Speaker 8>of nostalgic, like I had a partner in that neighborhood, like,

0:34:00.320 --> 0:34:04.200
<v Speaker 8>and you know, it's just brought back memories and you know,

0:34:04.320 --> 0:34:06.640
<v Speaker 8>my friends were like, oh, like we opened the door

0:34:06.680 --> 0:34:08.960
<v Speaker 8>from the building, there's a cab right there. And I

0:34:09.040 --> 0:34:12.279
<v Speaker 8>was like great, Like the universe is working out for me.

0:34:12.600 --> 0:34:15.600
<v Speaker 8>So yeah, like I get in and I'm just like, oh,

0:34:15.719 --> 0:34:18.719
<v Speaker 8>like went into my liked songs on Spotify and just

0:34:18.800 --> 0:34:25.319
<v Speaker 8>hit shuffle and the song Maps by the yayaya As

0:34:25.400 --> 0:34:29.480
<v Speaker 8>comes on, which is, you know, like this epic contemporary

0:34:29.880 --> 0:34:36.279
<v Speaker 8>love song and basically like the taxi just like decides to,

0:34:36.640 --> 0:34:38.960
<v Speaker 8>you know, go a certain way and we literally like

0:34:39.080 --> 0:34:44.480
<v Speaker 8>pass my ex's building as like this song is about like,

0:34:45.120 --> 0:34:47.080
<v Speaker 8>you know, saying like you know, they don't love you

0:34:47.200 --> 0:34:47.560
<v Speaker 8>like I.

0:34:47.480 --> 0:34:48.080
<v Speaker 4>Love you.

0:34:50.120 --> 0:34:56.480
<v Speaker 8>Then, and I just had this moment of like, what

0:34:56.520 --> 0:35:00.839
<v Speaker 8>the fuck is happening, not just like in my life

0:35:00.840 --> 0:35:04.839
<v Speaker 8>in the universe, but like what is this app even? So, yeah,

0:35:04.880 --> 0:35:08.960
<v Speaker 8>that led me to investigate those Spotify shuffle works in

0:35:08.960 --> 0:35:11.879
<v Speaker 8>a very randabout way. But you know, like I think

0:35:11.960 --> 0:35:16.600
<v Speaker 8>that's like what's kind of cool about existing now like

0:35:16.640 --> 0:35:20.800
<v Speaker 8>in this era where it's like, how are these technologies

0:35:20.920 --> 0:35:26.120
<v Speaker 8>and their glitches affecting our emotions in our personal lives?

0:35:26.239 --> 0:35:30.120
<v Speaker 8>And you know, is it random? Is it all random?

0:35:30.280 --> 0:35:30.760
<v Speaker 2>Et cetera.

0:35:31.719 --> 0:35:34.560
<v Speaker 3>Can you talk me through I guess starting with the

0:35:34.600 --> 0:35:39.000
<v Speaker 3>first iteration of like what Spotify shuffle used to do.

0:35:43.239 --> 0:35:51.759
<v Speaker 8>So basically there's like a very simple, elegant, mathematical description

0:35:52.880 --> 0:35:57.760
<v Speaker 8>of randomness. That's called the fisher Yates algorithm, and essentially

0:35:57.840 --> 0:36:02.720
<v Speaker 8>this is like from Spotify's insight option. Until somewhere between

0:36:02.760 --> 0:36:06.400
<v Speaker 8>twenty twelve and twenty fourteen, it was using fisher Yates

0:36:06.760 --> 0:36:12.560
<v Speaker 8>from my understanding from what's available fisher Yates basically, it's

0:36:12.600 --> 0:36:14.520
<v Speaker 8>an algorithm that will take an.

0:36:14.440 --> 0:36:15.480
<v Speaker 4>Array of values.

0:36:15.760 --> 0:36:19.520
<v Speaker 8>Let's say, like you have numbers one through ten, it

0:36:19.560 --> 0:36:24.040
<v Speaker 8>removes five, and five becomes the first track of the

0:36:24.080 --> 0:36:28.080
<v Speaker 8>shuffle list, and then it just keeps kind of you know,

0:36:29.040 --> 0:36:34.240
<v Speaker 8>randomly selecting the other values to like create a new list, Sasha,

0:36:35.280 --> 0:36:38.600
<v Speaker 8>So every number in that list has an equal chance

0:36:38.800 --> 0:36:43.760
<v Speaker 8>of appearing in the first position or the consequential one.

0:36:43.880 --> 0:36:48.040
<v Speaker 8>It's great because technically that's completely random.

0:36:48.840 --> 0:36:49.120
<v Speaker 4>Right.

0:36:49.320 --> 0:36:54.279
<v Speaker 8>So Spotify engineers were like, this is awesome. You can

0:36:54.320 --> 0:36:57.719
<v Speaker 8>do this in between like two or three lines of code,

0:36:58.239 --> 0:37:00.839
<v Speaker 8>Like it was so simple. They're like, yeah, we sold this,

0:37:01.200 --> 0:37:05.279
<v Speaker 8>and like kind of instantly the user complaints came in

0:37:05.480 --> 0:37:09.320
<v Speaker 8>of like my shuffle is broken. How is it possible

0:37:09.360 --> 0:37:11.440
<v Speaker 8>that you could screw this up? It's so simple?

0:37:11.960 --> 0:37:13.719
<v Speaker 3>And the complaints were at the time because I remember

0:37:13.760 --> 0:37:16.279
<v Speaker 3>seeing them on social right would be like, how's you

0:37:16.280 --> 0:37:20.200
<v Speaker 3>know Spotify Shuffle Ranmouth. They're playing four Taylor Swift songs.

0:37:19.960 --> 0:37:23.399
<v Speaker 8>In a row one hundred percent. But you can see,

0:37:23.520 --> 0:37:26.040
<v Speaker 8>like based on how I described how it works, Ye,

0:37:26.680 --> 0:37:31.640
<v Speaker 8>randomness does create clusters. So it creates like, you know,

0:37:32.200 --> 0:37:36.560
<v Speaker 8>clusters of songs from one album or clusters of songs

0:37:36.560 --> 0:37:39.399
<v Speaker 8>by the same artist, Like each of those songs has

0:37:39.440 --> 0:37:44.240
<v Speaker 8>the exact same chance of like emerging, right, there's nothing

0:37:44.400 --> 0:37:50.160
<v Speaker 8>preventing that. So what the engineers finally determined was users

0:37:50.200 --> 0:37:58.120
<v Speaker 8>were falling for what's called the Monte Carlo fallacy. So

0:37:58.560 --> 0:38:03.000
<v Speaker 8>this is basically a human perception of randomness that is

0:38:03.040 --> 0:38:06.760
<v Speaker 8>not correct, and it's named after this very specific event

0:38:06.840 --> 0:38:11.560
<v Speaker 8>that occurred August eighteenth, nineteen thirteen, at the famous Monte

0:38:11.560 --> 0:38:18.000
<v Speaker 8>Carlo casino. We're essentially at the roulette table. The ball

0:38:18.120 --> 0:38:21.440
<v Speaker 8>kept falling on black. It starts to create this weird

0:38:22.320 --> 0:38:25.600
<v Speaker 8>chaos and like sensation in the casino because people are

0:38:25.640 --> 0:38:29.879
<v Speaker 8>thinking like this isn't possible, right, like you know, two

0:38:29.960 --> 0:38:33.160
<v Speaker 8>or three times sure, then you get into like five

0:38:33.239 --> 0:38:38.239
<v Speaker 8>to ten times, you know, like whirl, like this is unusual.

0:38:39.280 --> 0:38:43.040
<v Speaker 8>So yeah, something's up, and people kind of come down

0:38:43.239 --> 0:38:47.000
<v Speaker 8>with this fever of just expecting like on the next

0:38:47.239 --> 0:38:50.840
<v Speaker 8>turn of the wheel, red, Red is going to happen.

0:38:50.920 --> 0:38:53.359
<v Speaker 8>Red is going to happen because Black has happened all

0:38:53.440 --> 0:39:00.680
<v Speaker 8>these times of beforehand, and that night all fell on

0:39:00.760 --> 0:39:04.080
<v Speaker 8>Black twenty six times in a row, which is just

0:39:04.400 --> 0:39:09.840
<v Speaker 8>like it's like an astronomical this happened, and yeah, it

0:39:10.080 --> 0:39:13.759
<v Speaker 8>just this whole situation pointed out that like it's also

0:39:13.840 --> 0:39:18.120
<v Speaker 8>called the gambler's fallacy. It's where you think previous events

0:39:18.160 --> 0:39:23.760
<v Speaker 8>somehow affect the current event unfolding. So that's why people

0:39:23.800 --> 0:39:29.240
<v Speaker 8>get angry at like the clusters of you know, Addison

0:39:29.320 --> 0:39:29.960
<v Speaker 8>Ray or whatever.

0:39:30.239 --> 0:39:32.759
<v Speaker 3>Yeah, it's like, okay, you're already played in Addison Ray song.

0:39:33.360 --> 0:39:36.799
<v Speaker 3>Therefore their Monte Carlo Felas is like, yeah, it has

0:39:36.840 --> 0:39:38.799
<v Speaker 3>to be something different now because we've done Black so

0:39:38.840 --> 0:39:40.719
<v Speaker 3>many times in a row. We played the Addison and

0:39:40.800 --> 0:39:44.200
<v Speaker 3>Ray song, so therefore an X song cannot possibly be

0:39:44.400 --> 0:39:45.440
<v Speaker 3>diet pepsi, you.

0:39:45.400 --> 0:39:48.520
<v Speaker 8>Know, right, and then like what the fuck it's diet pepsi?

0:39:48.719 --> 0:39:52.760
<v Speaker 8>Like are you kidding me? Right now? The engineers were like, oh, okay,

0:39:52.840 --> 0:39:56.319
<v Speaker 8>people are having like this weird issue, like they don't

0:39:56.320 --> 0:40:02.600
<v Speaker 8>realize what randomness actually is. So then they created essentially,

0:40:02.920 --> 0:40:08.000
<v Speaker 8>like it's not like a hybrid algorithm, but they created

0:40:08.040 --> 0:40:13.560
<v Speaker 8>a different one that mimics or attempts to mimic, the

0:40:13.680 --> 0:40:17.440
<v Speaker 8>human perception of randomness. So it does this way. It

0:40:17.440 --> 0:40:22.399
<v Speaker 8>takes your playlist and it's like, oh, like, I don't know,

0:40:22.560 --> 0:40:25.760
<v Speaker 8>You've got a lot of like Justin Bieber in here,

0:40:26.520 --> 0:40:30.120
<v Speaker 8>So it's spreading Justin Bieber and then with being Justin Bieber,

0:40:30.320 --> 0:40:32.120
<v Speaker 8>it's spreading out the albums.

0:40:32.600 --> 0:40:34.000
<v Speaker 2>Yeah yeah, yeah, yeah.

0:40:33.800 --> 0:40:35.720
<v Speaker 8>So it's called cluster breaking.

0:40:36.000 --> 0:40:38.400
<v Speaker 3>Yeah, you're not going to get to Justin Bieber songs

0:40:38.400 --> 0:40:42.840
<v Speaker 3>within a ten track shuffle from Swag. We're going to

0:40:42.880 --> 0:40:44.640
<v Speaker 3>make sure if you get to Justin Bieber songs, you're

0:40:44.640 --> 0:40:45.840
<v Speaker 3>from completely different albums.

0:40:45.960 --> 0:40:46.640
<v Speaker 4>One hundred percent.

0:40:46.960 --> 0:40:51.080
<v Speaker 8>Yes. So that was their solution. And keep in mind,

0:40:51.239 --> 0:40:53.880
<v Speaker 8>like what I've just described with the cluster breaks, like

0:40:53.920 --> 0:40:57.760
<v Speaker 8>that's from twenty fourteen, so like we there's been nothing

0:40:58.440 --> 0:41:02.439
<v Speaker 8>really that they put out since then that describes what's

0:41:02.480 --> 0:41:06.359
<v Speaker 8>going on. People are now in this weird position where

0:41:06.400 --> 0:41:10.839
<v Speaker 8>they're like they want, like the Fisheryates algorithm to come

0:41:10.880 --> 0:41:15.040
<v Speaker 8>back as like an additional like like if shuffle could

0:41:15.120 --> 0:41:19.040
<v Speaker 8>have yet exactly, and they're like yeah, like I know

0:41:19.080 --> 0:41:23.279
<v Speaker 8>it's bad, but like it would just be preferable to

0:41:23.440 --> 0:41:30.160
<v Speaker 8>like whatever this weird thing is. Our human minds are

0:41:30.200 --> 0:41:35.080
<v Speaker 8>so small that, you know, we're only able to comprehend

0:41:35.200 --> 0:41:37.400
<v Speaker 8>like a very like tiny wedge.

0:41:37.520 --> 0:41:39.480
<v Speaker 4>Of how the world functions.

0:41:39.600 --> 0:41:43.200
<v Speaker 8>Right, So it could be that like we're seeing all

0:41:43.280 --> 0:41:47.799
<v Speaker 8>these things as random, but really it's like, oh, if

0:41:47.800 --> 0:41:51.279
<v Speaker 8>we could actually take a step back and like have

0:41:51.360 --> 0:41:54.239
<v Speaker 8>more of a bird's eye view, potentially these things could

0:41:54.239 --> 0:41:57.959
<v Speaker 8>be connected. And they just operate at a pace that's

0:41:58.000 --> 0:42:00.800
<v Speaker 8>so slow that like over the core of one human

0:42:00.880 --> 0:42:05.040
<v Speaker 8>lifetime it appears random, but over the course of like

0:42:05.200 --> 0:42:09.000
<v Speaker 8>five hundred human lifetimes, it's actually like one slow process

0:42:09.000 --> 0:42:11.560
<v Speaker 8>that makes perfect sense, but we're just not able to

0:42:11.640 --> 0:42:17.840
<v Speaker 8>comprehend it, right, So you know it just randomness is

0:42:17.840 --> 0:42:22.120
<v Speaker 8>so interesting because in a sense, it's undefinable. Yeah, right,

0:42:24.360 --> 0:42:27.600
<v Speaker 8>So that's why it's so interesting when you have something

0:42:27.719 --> 0:42:31.759
<v Speaker 8>that's essentially like a math problem where it's like, come on,

0:42:31.880 --> 0:42:35.360
<v Speaker 8>like I have like I don't know, thirty five hundred songs.

0:42:35.840 --> 0:42:39.520
<v Speaker 8>It can't like how how complicated could it possibly be?

0:42:41.040 --> 0:42:43.000
<v Speaker 8>And it turns out it's really complicated.

0:42:47.239 --> 0:42:50.960
<v Speaker 2>HEATHERN. Mccalldon is the author of the Observable Universe. We're

0:42:50.960 --> 0:42:52.680
<v Speaker 2>going to put a link to it in our show.

0:42:52.520 --> 0:43:01.920
<v Speaker 3>Notess Hews Hews her howss. No Such Thing is a

0:43:01.920 --> 0:43:06.520
<v Speaker 3>production of Kaleidoscope Content. Our executive producers are Kate Osborne

0:43:06.560 --> 0:43:09.840
<v Speaker 3>in Mangesh Hadi Cardur. The show was created by Many Fidel,

0:43:09.920 --> 0:43:13.480
<v Speaker 3>Noah Friedman and Me Devin Joseph. Our theme in credit

0:43:13.560 --> 0:43:17.600
<v Speaker 3>song or by Manny, mixing by Steve Bone. Additional music

0:43:17.680 --> 0:43:20.879
<v Speaker 3>for this episode by certain Self. Our guests this week

0:43:20.880 --> 0:43:24.560
<v Speaker 3>we're doctor Loriana Gaudette from the Weather Company, Mary Glacken

0:43:24.880 --> 0:43:28.880
<v Speaker 3>and Heather mccauden. Thanks to Alec Mia and Austin for

0:43:28.960 --> 0:43:31.840
<v Speaker 3>the questions. If you have something you want us to

0:43:31.840 --> 0:43:33.799
<v Speaker 3>get at the bottom of you can email us at

0:43:33.840 --> 0:43:37.400
<v Speaker 3>Manny Noah Devin at gmail dot com. Sign up for

0:43:37.440 --> 0:43:40.839
<v Speaker 3>our newsletter No Such Thing that shows We'll

0:43:40.840 --> 0:43:45.120
<v Speaker 1>See you guys, those by those such things