WEBVTT

NOTE
Transcription provided by Deepgram

00:00:03.120 --> 00:00:06.180
<v Speaker 0>Welcome to the Geek News Central podcast, episode

00:00:06.240 --> 00:00:11.280
<v Speaker 0>number eighteen fifty one. We're got a lead

00:00:11.280 --> 00:00:14.495
<v Speaker 0>story today. It's gonna be NASA's Voyager spacecraft

00:00:14.495 --> 00:00:17.075
<v Speaker 0>on a thirty thousand to fifty thousand Kelvin

00:00:17.295 --> 00:00:19.635
<v Speaker 0>wall at the edge of our solar system.

00:00:20.735 --> 00:00:22.575
<v Speaker 0>Thanks for tuning in, folks. We got a

00:00:22.575 --> 00:00:25.710
<v Speaker 0>pretty sweet show lined up for you. Sorry

00:00:25.710 --> 00:00:27.070
<v Speaker 0>for showing up so late in the week,

00:00:27.070 --> 00:00:30.689
<v Speaker 0>but been having some audio and hardware problems

00:00:31.310 --> 00:00:33.070
<v Speaker 0>all week long. We're gonna get more into

00:00:33.070 --> 00:00:35.710
<v Speaker 0>that in a bit, but check this article

00:00:35.710 --> 00:00:38.505
<v Speaker 0>out. Little bit of context going into it.

00:00:38.665 --> 00:00:41.725
<v Speaker 0>The twin NASA probes, Voyager one and Voyager

00:00:41.785 --> 00:00:44.105
<v Speaker 0>two, launched in nineteen seventy seven and have

00:00:44.105 --> 00:00:46.345
<v Speaker 0>been exploring the outer reaches of our solar

00:00:46.345 --> 00:00:50.185
<v Speaker 0>system, including what's known as the heliosphere, the

00:00:50.185 --> 00:00:53.065
<v Speaker 0>bubble of space dominated by the sun's solar

00:00:53.065 --> 00:00:55.970
<v Speaker 0>wind, and the boundary where it meets the

00:00:55.970 --> 00:01:00.290
<v Speaker 0>interstellar medium. An article published by IFL Science

00:01:00.290 --> 00:01:03.170
<v Speaker 0>reports that the spacecraft measured a region at

00:01:03.170 --> 00:01:06.225
<v Speaker 0>the solar system's edge with apparent temperatures of

00:01:06.385 --> 00:01:10.145
<v Speaker 0>thirty thousand to fifty thousand kelvins, described as

00:01:10.145 --> 00:01:14.145
<v Speaker 0>a wall of fire. However, this description is

00:01:14.145 --> 00:01:18.485
<v Speaker 0>somewhat informal and may reflect specific plasma measurements

00:01:18.545 --> 00:01:21.125
<v Speaker 0>rather than a literal wall or solid surface.

00:01:23.440 --> 00:01:27.460
<v Speaker 0>This is a pretty cool idea, coming from,

00:01:28.320 --> 00:01:31.040
<v Speaker 0>IFL Science today. Thank you, James Felton, for

00:01:31.040 --> 00:01:35.715
<v Speaker 0>writing this article. And I I got a

00:01:35.715 --> 00:01:37.715
<v Speaker 0>couple key quotes from the article that we

00:01:37.715 --> 00:01:40.355
<v Speaker 0>can, talk about, but while not a hard

00:01:40.355 --> 00:01:42.455
<v Speaker 0>edge or a wall as it has sometimes

00:01:42.515 --> 00:01:46.275
<v Speaker 0>been called, here both spacecraft measured temperatures of

00:01:46.275 --> 00:01:48.515
<v Speaker 0>thirty thousand to fifty thousand Kelvin, which is

00:01:48.515 --> 00:01:52.659
<v Speaker 0>around fifty four thousand to ninety thousand degrees

00:01:52.880 --> 00:01:56.079
<v Speaker 0>Fahrenheit. And this kinda helps us understand the

00:01:56.079 --> 00:01:58.079
<v Speaker 0>the nuance and then it it's not a

00:01:58.079 --> 00:02:00.240
<v Speaker 0>solid wall we're really talking about. So it's

00:02:00.240 --> 00:02:02.805
<v Speaker 0>not a rigid barrier, but a region of

00:02:02.805 --> 00:02:06.565
<v Speaker 0>extreme conditions encountered at the periphery of the

00:02:06.565 --> 00:02:13.445
<v Speaker 0>heliosphere. Sorry. I'm gonna mess with the audience

00:02:13.445 --> 00:02:14.565
<v Speaker 0>a little bit. I'm getting a little bit

00:02:14.565 --> 00:02:16.745
<v Speaker 0>of weirdness coming in from here, this thingy.

00:02:17.150 --> 00:02:19.630
<v Speaker 0>But hopefully it's not too awful and we

00:02:19.630 --> 00:02:23.730
<v Speaker 0>can kinda clear that out later on. But

00:02:24.590 --> 00:02:30.205
<v Speaker 0>if we're curious, well, let's see. This kinda

00:02:30.205 --> 00:02:32.845
<v Speaker 0>highlights how these long running missions are kinda

00:02:32.845 --> 00:02:36.125
<v Speaker 0>affecting us now and research still going on.

00:02:36.125 --> 00:02:38.125
<v Speaker 0>I mean, nineteen seventy seven is a long

00:02:38.125 --> 00:02:41.265
<v Speaker 0>time to be, out there in space. So

00:02:41.485 --> 00:02:44.690
<v Speaker 0>glad to see these machines still running and

00:02:44.690 --> 00:02:47.170
<v Speaker 0>working hard for us all these years later.

00:02:47.170 --> 00:02:51.890
<v Speaker 0>That's a great investment. Right? And, like, I

00:02:51.890 --> 00:02:54.530
<v Speaker 0>guess, like, apparently, while you won't exactly feel

00:02:54.530 --> 00:02:57.685
<v Speaker 0>this wall, like, when you go there, you

00:02:57.685 --> 00:02:59.125
<v Speaker 0>can it kinda gives you a good idea

00:02:59.125 --> 00:03:01.444
<v Speaker 0>of, like, this protective bubble that's around our

00:03:01.444 --> 00:03:04.805
<v Speaker 0>solar system and how it shields us. And

00:03:04.805 --> 00:03:07.224
<v Speaker 0>exploring it helps us understand, like, the environment

00:03:07.284 --> 00:03:09.844
<v Speaker 0>and our planet. That's that's, like, part of

00:03:09.844 --> 00:03:11.970
<v Speaker 0>that system. So So it's kind of interesting

00:03:12.030 --> 00:03:15.390
<v Speaker 0>to see. And on here, there's a NASA

00:03:15.390 --> 00:03:17.470
<v Speaker 0>video. So we'll link the the article if

00:03:17.470 --> 00:03:19.790
<v Speaker 0>you guys wanna check this out. But there

00:03:19.790 --> 00:03:23.355
<v Speaker 0>is a video by NASA on here, that

00:03:23.355 --> 00:03:26.975
<v Speaker 0>kinda shows, what what exactly they're talking about.

00:03:27.435 --> 00:03:30.655
<v Speaker 0>But pretty sweet stuff from, IFL Science today.

00:03:31.515 --> 00:03:34.955
<v Speaker 0>But let's take a step back. I wanna

00:03:34.955 --> 00:03:38.480
<v Speaker 0>talk about this week for myself. It's been

00:03:38.480 --> 00:03:41.620
<v Speaker 0>a pretty rough one for me, both in

00:03:42.319 --> 00:03:46.879
<v Speaker 0>the hardware zone as well as, you know,

00:03:46.879 --> 00:03:51.040
<v Speaker 0>my personal life. Had a couple midterms come

00:03:51.040 --> 00:03:55.195
<v Speaker 0>and go, pretty tough, and glad to see

00:03:55.195 --> 00:03:58.315
<v Speaker 0>some of the results coming back. Looking like

00:03:58.315 --> 00:04:01.435
<v Speaker 0>the studying paid off, but always glad to

00:04:01.435 --> 00:04:04.235
<v Speaker 0>see those positive results. You know, it's really

00:04:04.235 --> 00:04:05.995
<v Speaker 0>a relief. I don't know how many of

00:04:05.995 --> 00:04:08.175
<v Speaker 0>you are out there taking tests still, but

00:04:08.849 --> 00:04:12.690
<v Speaker 0>Jesus. It's just so nerve wracking going into

00:04:12.690 --> 00:04:15.890
<v Speaker 0>those situations and then looking at something and

00:04:15.890 --> 00:04:19.570
<v Speaker 0>realizing, oh god, I do not know what

00:04:19.570 --> 00:04:21.729
<v Speaker 0>this is and having to calm down and

00:04:21.729 --> 00:04:24.335
<v Speaker 0>take a step back and really analyze the

00:04:24.335 --> 00:04:26.175
<v Speaker 0>problem you're looking at. So it's been really

00:04:26.175 --> 00:04:33.315
<v Speaker 0>fun. On another note, I've been so man,

00:04:33.615 --> 00:04:37.750
<v Speaker 0>I had been recording the podcast on, my

00:04:37.750 --> 00:04:44.069
<v Speaker 0>dad's Mac studio, and I finally got you

00:04:44.069 --> 00:04:45.990
<v Speaker 0>know, starting to run into issues with his

00:04:45.990 --> 00:04:47.669
<v Speaker 0>account on the on the machine. So I

00:04:47.669 --> 00:04:49.655
<v Speaker 0>was like, hey, man. I'll just give it

00:04:49.655 --> 00:04:51.574
<v Speaker 0>a little reset. I've already extracted all of

00:04:51.574 --> 00:04:53.835
<v Speaker 0>his data from it. Great. Let's move on.

00:04:54.215 --> 00:04:55.495
<v Speaker 0>So I was gonna give it a little

00:04:55.495 --> 00:04:58.955
<v Speaker 0>reset and lo and behold, despite his legacy

00:04:59.014 --> 00:05:05.150
<v Speaker 0>account being activated or whatever, that the the

00:05:05.150 --> 00:05:08.350
<v Speaker 0>devices got an activation lock on it. I'm

00:05:08.350 --> 00:05:11.070
<v Speaker 0>calling support, I'm calling support, they're they're telling

00:05:11.070 --> 00:05:13.790
<v Speaker 0>me exactly what the article says. I'm like,

00:05:13.790 --> 00:05:17.070
<v Speaker 0>great. Cool. The activation lock was supposed to

00:05:17.070 --> 00:05:19.490
<v Speaker 0>fall off when the legacy account was invoked.

00:05:20.635 --> 00:05:22.635
<v Speaker 0>But I guess there's one offs. It's always

00:05:22.635 --> 00:05:27.755
<v Speaker 0>an edge case. I'm not sure why. It's

00:05:27.755 --> 00:05:30.335
<v Speaker 0>this strict, but I did end up finding

00:05:30.395 --> 00:05:34.400
<v Speaker 0>their site. Thanks to one of the support

00:05:34.400 --> 00:05:36.400
<v Speaker 0>agents. I got to one of their sites

00:05:36.400 --> 00:05:38.400
<v Speaker 0>where I could request the activation lock be

00:05:38.400 --> 00:05:41.919
<v Speaker 0>removed. So hoping to hear back from them

00:05:41.919 --> 00:05:43.440
<v Speaker 0>in the next week or so and really

00:05:43.440 --> 00:05:46.995
<v Speaker 0>get back on that device. Just been a

00:05:46.995 --> 00:05:49.315
<v Speaker 0>little bit of a pain getting this all

00:05:49.315 --> 00:05:55.895
<v Speaker 0>set up with, my personal device. Yeah. But

00:05:56.355 --> 00:05:58.675
<v Speaker 0>on the offside, I did end up finding

00:05:58.675 --> 00:06:00.775
<v Speaker 0>something called I think it's called auto edit,

00:06:01.180 --> 00:06:02.940
<v Speaker 0>and we're gonna try to use that to

00:06:02.940 --> 00:06:05.259
<v Speaker 0>cut out all the ahs and umms and

00:06:05.259 --> 00:06:07.520
<v Speaker 0>likes out of this video today. So hopefully

00:06:08.300 --> 00:06:11.419
<v Speaker 0>we can see a little bit more smooth

00:06:11.419 --> 00:06:13.180
<v Speaker 0>transitions and just, you know, test out some

00:06:13.180 --> 00:06:16.639
<v Speaker 0>fun software. It's open source, MIT license. So

00:06:17.085 --> 00:06:18.685
<v Speaker 0>you're you're you're free to try it out

00:06:18.685 --> 00:06:19.885
<v Speaker 0>if you if you wanna go check it

00:06:19.885 --> 00:06:23.485
<v Speaker 0>out. Check it out. It's called auto auto

00:06:23.485 --> 00:06:26.285
<v Speaker 0>edit, I believe. I'm blanking right now. I'm

00:06:26.285 --> 00:06:29.505
<v Speaker 0>not sure why. Other than that, I just

00:06:30.240 --> 00:06:32.900
<v Speaker 0>last few days, just really been feeling exhausted.

00:06:33.120 --> 00:06:37.200
<v Speaker 0>So, been trying to get some good sleep

00:06:37.200 --> 00:06:42.580
<v Speaker 0>tonight and hopefully tackle tomorrow head first. But

00:06:43.495 --> 00:06:45.335
<v Speaker 0>it yeah. I think I've just been a

00:06:45.335 --> 00:06:47.355
<v Speaker 0>little bit stressed and a little bit overwhelmed,

00:06:47.415 --> 00:06:49.175
<v Speaker 0>so hoping to pull back on one of

00:06:49.175 --> 00:06:51.015
<v Speaker 0>the jobs and then put a little more

00:06:51.015 --> 00:06:55.415
<v Speaker 0>focus towards Blueberry in school, I guess Raw

00:06:55.415 --> 00:07:00.480
<v Speaker 0>Voice in school, and see where that leads.

00:07:02.140 --> 00:07:05.680
<v Speaker 0>Less about me. Let's, take a moment to

00:07:05.740 --> 00:07:10.885
<v Speaker 0>thank our lovely sponsors, GoDaddy for their incredible

00:07:10.885 --> 00:07:13.125
<v Speaker 0>support of this podcast. They make it possible

00:07:13.125 --> 00:07:14.745
<v Speaker 0>for us to keep doing what we love

00:07:14.965 --> 00:07:17.045
<v Speaker 0>and for you guys to keep enjoying what

00:07:17.045 --> 00:07:19.525
<v Speaker 0>you hear every week. New news on all

00:07:19.525 --> 00:07:23.305
<v Speaker 0>the greatest and latest tech and science news.

00:07:25.410 --> 00:07:26.930
<v Speaker 0>They make it possible for us to keep

00:07:26.930 --> 00:07:30.449
<v Speaker 0>doing it. So we're we're extremely grateful. We

00:07:30.449 --> 00:07:34.610
<v Speaker 0>wanna keep maintaining that relationship. So if you're

00:07:34.610 --> 00:07:36.370
<v Speaker 0>ready to start your own website or even

00:07:36.370 --> 00:07:40.605
<v Speaker 0>launch a podcast, GoDaddy's got you covered. At

00:07:40.605 --> 00:07:42.705
<v Speaker 0>geek new central dot com forward slash GoDaddy,

00:07:42.765 --> 00:07:44.685
<v Speaker 0>you'll find special promo codes that make it

00:07:44.685 --> 00:07:48.285
<v Speaker 0>easy and affordable to get started. Economy Hosting,

00:07:48.285 --> 00:07:50.045
<v Speaker 0>just six ninety nine a month. That's a

00:07:50.045 --> 00:07:52.205
<v Speaker 0>full year of hosting with free domain name,

00:07:52.205 --> 00:07:55.840
<v Speaker 0>professional email, and an SSL certificate. And if

00:07:55.840 --> 00:07:59.040
<v Speaker 0>you like WordPress hosting, which I have I

00:07:59.040 --> 00:08:01.600
<v Speaker 0>love I love WordPress. I've been messing with

00:08:01.600 --> 00:08:03.840
<v Speaker 0>my own set of widgets recently and trying

00:08:03.840 --> 00:08:06.020
<v Speaker 0>to get something put together for another site.

00:08:06.800 --> 00:08:12.505
<v Speaker 0>Obviously using GoDaddy, for that. And WordPress hosting

00:08:12.505 --> 00:08:14.025
<v Speaker 0>is only twelve ninety nine a month, and

00:08:14.025 --> 00:08:15.945
<v Speaker 0>you get that free domain name as well,

00:08:15.945 --> 00:08:18.665
<v Speaker 0>email, and SSL certificate. And if you only

00:08:18.665 --> 00:08:20.265
<v Speaker 0>need a domain name, something that it gets

00:08:20.265 --> 00:08:22.185
<v Speaker 0>set up now, you wanna worry about it

00:08:22.185 --> 00:08:23.945
<v Speaker 0>now and get it saved so no one

00:08:23.945 --> 00:08:25.885
<v Speaker 0>else can steal that name from you because

00:08:25.950 --> 00:08:27.890
<v Speaker 0>when someone else has it, it's it's gone.

00:08:28.190 --> 00:08:31.890
<v Speaker 0>And some of those, like, non dot com

00:08:32.030 --> 00:08:34.110
<v Speaker 0>endpoints can get a little expensive. Well, we

00:08:34.110 --> 00:08:36.110
<v Speaker 0>can take care of that. Grab one for

00:08:36.110 --> 00:08:40.375
<v Speaker 0>only eleven ninety nine with our promo codes.

00:08:40.595 --> 00:08:42.774
<v Speaker 0>And if you're not super tech savvy, GoDaddy's

00:08:42.915 --> 00:08:44.995
<v Speaker 0>website builder gives you a free thirty day

00:08:44.995 --> 00:08:47.954
<v Speaker 0>trial on personal business and business plus plans.

00:08:47.954 --> 00:08:49.735
<v Speaker 0>So you can get online in no time.

00:08:49.954 --> 00:08:52.640
<v Speaker 0>You you just describe your needs to the

00:08:52.640 --> 00:08:54.400
<v Speaker 0>GoDaddy site builder and it, and it puts

00:08:54.400 --> 00:08:58.000
<v Speaker 0>it together for you. It's very impressive. I

00:08:58.000 --> 00:09:00.880
<v Speaker 0>obviously use GoDaddy products and services my myself,

00:09:00.880 --> 00:09:02.960
<v Speaker 0>and I can tell you their reliability is

00:09:02.960 --> 00:09:07.385
<v Speaker 0>legit. Your support, GoDaddy, directly supports the show.

00:09:07.385 --> 00:09:10.445
<v Speaker 0>So please use our code, click and save,

00:09:10.505 --> 00:09:13.084
<v Speaker 0>and help keep this independent podcast going strong.

00:09:13.385 --> 00:09:15.385
<v Speaker 0>Share those links with friends and family. Every

00:09:15.385 --> 00:09:17.144
<v Speaker 0>time one is used, it's like writing a

00:09:17.144 --> 00:09:19.210
<v Speaker 0>check to the show. We truly thank you

00:09:19.210 --> 00:09:21.290
<v Speaker 0>for supporting us and a huge thanks to

00:09:21.290 --> 00:09:24.010
<v Speaker 0>GoDaddy for believing in independent creators like us

00:09:24.010 --> 00:09:27.130
<v Speaker 0>here at Geek News Central. And I don't

00:09:27.130 --> 00:09:31.085
<v Speaker 0>wanna say I didn't forget you guys. You

00:09:31.085 --> 00:09:33.245
<v Speaker 0>guys are truly the heartbeat of the show.

00:09:33.245 --> 00:09:36.845
<v Speaker 0>Kinda switching it up here today. But if

00:09:36.845 --> 00:09:39.885
<v Speaker 0>you wanna directly support the show yourself, outside

00:09:39.885 --> 00:09:41.565
<v Speaker 0>of using those GoDaddy codes, you can head

00:09:41.565 --> 00:09:43.405
<v Speaker 0>over to geek new central dot com forward

00:09:43.405 --> 00:09:47.460
<v Speaker 0>slash insider and become a GNC insider. Another

00:09:47.460 --> 00:09:48.980
<v Speaker 0>way you can support the show is by

00:09:48.980 --> 00:09:51.620
<v Speaker 0>grabbing a modern podcast apps at podcast apps

00:09:51.620 --> 00:09:54.900
<v Speaker 0>dot com. I personally have been using a

00:09:54.900 --> 00:09:59.220
<v Speaker 0>little bit of fountain. Been using, there's another

00:09:59.220 --> 00:10:00.500
<v Speaker 0>one I've been using. I don't know the

00:10:00.500 --> 00:10:02.875
<v Speaker 0>name, but I've been grabbing the, I've been

00:10:02.875 --> 00:10:05.115
<v Speaker 0>hitting that one by default. But I find

00:10:05.115 --> 00:10:06.555
<v Speaker 0>found kinda cool because they have that built

00:10:06.555 --> 00:10:10.315
<v Speaker 0>in, value system, which you can use to

00:10:10.315 --> 00:10:15.035
<v Speaker 0>boost podcasts, like this show and show your

00:10:15.035 --> 00:10:19.290
<v Speaker 0>support. Stay in the loop. Follow or subscribe

00:10:20.149 --> 00:10:22.230
<v Speaker 0>in your favorite podcast app, and don't forget

00:10:22.230 --> 00:10:24.870
<v Speaker 0>to sign up for our newsletter. I missed

00:10:24.870 --> 00:10:27.589
<v Speaker 0>the last one. I am sorry. And I

00:10:27.589 --> 00:10:29.350
<v Speaker 0>still haven't gotten Chris on the newsletter. So

00:10:29.350 --> 00:10:31.075
<v Speaker 0>I'm definitely gonna try to get on a

00:10:31.075 --> 00:10:32.995
<v Speaker 0>call with him this week. I promise you

00:10:32.995 --> 00:10:34.935
<v Speaker 0>guys we're gonna get this all figured out.

00:10:35.795 --> 00:10:37.895
<v Speaker 0>I think I just schedules have been crazy.

00:10:38.675 --> 00:10:41.235
<v Speaker 0>Trying to maintain, time and put time aside

00:10:41.235 --> 00:10:43.415
<v Speaker 0>for the show. So at twelve fifty one,

00:10:43.875 --> 00:10:45.075
<v Speaker 0>in the middle of the night for me

00:10:45.075 --> 00:10:52.660
<v Speaker 0>right now. So we're doing our best. But

00:10:52.660 --> 00:10:54.260
<v Speaker 0>you can always reach us directly at geek

00:10:54.260 --> 00:10:57.540
<v Speaker 0>news at gmail dot com. I've finally gotten

00:10:57.540 --> 00:10:59.400
<v Speaker 0>to a point with the Geek News email

00:10:59.460 --> 00:11:02.485
<v Speaker 0>that we are no longer getting weird, spammy

00:11:02.625 --> 00:11:05.765
<v Speaker 0>emails and, have now got a clean intake.

00:11:06.305 --> 00:11:09.185
<v Speaker 0>So, definitely looking forward to hearing from you

00:11:09.185 --> 00:11:12.065
<v Speaker 0>guys and seeing those emails come through. Send

00:11:12.065 --> 00:11:13.505
<v Speaker 0>an email in. Let us know what you

00:11:13.505 --> 00:11:19.410
<v Speaker 0>think. Support the show. But let's move on.

00:11:19.410 --> 00:11:22.529
<v Speaker 0>Let's talk about some articles. Some cool stuff

00:11:22.529 --> 00:11:25.250
<v Speaker 0>going on this week. Now I did miss

00:11:25.250 --> 00:11:27.089
<v Speaker 0>the launch date on this, but there's another

00:11:27.089 --> 00:11:30.095
<v Speaker 0>one coming up. PBS celebrates twenty five years

00:11:30.095 --> 00:11:34.175
<v Speaker 0>of ISS with Nova's Operation Space Station on

00:11:34.175 --> 00:11:36.175
<v Speaker 0>November fifth. So this this is gonna be

00:11:36.175 --> 00:11:39.615
<v Speaker 0>actually a two part thing. So let's give

00:11:39.615 --> 00:11:41.454
<v Speaker 0>you some context before we go into it.

00:11:41.615 --> 00:11:44.880
<v Speaker 0>Coming out, International Space Station has been continuously

00:11:45.020 --> 00:11:48.060
<v Speaker 0>inhabited since November second two thousand, and this

00:11:48.060 --> 00:11:50.160
<v Speaker 0>year marks its twenty five years of operation.

00:11:50.460 --> 00:11:52.060
<v Speaker 0>And we have kinda been talking a lot

00:11:52.060 --> 00:11:56.220
<v Speaker 0>about the twenty thirty, deorbit schedule, moving into

00:11:56.220 --> 00:12:01.154
<v Speaker 0>the commercialization of space research. So I'm super

00:12:01.154 --> 00:12:02.915
<v Speaker 0>interested to see how that goes. It's very

00:12:02.915 --> 00:12:05.634
<v Speaker 0>obvious that, SpaceX has a massive lead right

00:12:05.634 --> 00:12:10.055
<v Speaker 0>now. They've gotten majority of the contracts. So

00:12:10.194 --> 00:12:16.570
<v Speaker 0>we'll see how that goes. But this, particular

00:12:16.570 --> 00:12:19.610
<v Speaker 0>episode is produced by Nova for PBS in

00:12:19.610 --> 00:12:23.770
<v Speaker 0>collaboration with GBH and French France televisions and

00:12:23.770 --> 00:12:28.035
<v Speaker 0>uses archival footage, CGI recreations, and firsthand astronaut

00:12:28.035 --> 00:12:31.715
<v Speaker 0>slash engineer accounts. The documentary is two parts,

00:12:31.715 --> 00:12:34.675
<v Speaker 0>High Risk Build premiering November fifth, and Science

00:12:34.675 --> 00:12:37.235
<v Speaker 0>and Survival premiering November twelfth. Now I haven't

00:12:37.235 --> 00:12:38.835
<v Speaker 0>seen the first part, but I'm kinda stoked,

00:12:38.835 --> 00:12:40.435
<v Speaker 0>so I'm gonna check this out, High Risk

00:12:40.435 --> 00:12:42.710
<v Speaker 0>Build. And then, here in a few days,

00:12:42.710 --> 00:12:44.230
<v Speaker 0>the the second part is gonna be coming

00:12:44.230 --> 00:12:47.110
<v Speaker 0>out of, on November twelfth, science and survival.

00:12:47.110 --> 00:12:48.390
<v Speaker 0>So if you guys check that first part

00:12:48.390 --> 00:12:49.990
<v Speaker 0>out, you guys will be primed to watch

00:12:49.990 --> 00:12:54.565
<v Speaker 0>the second. But it's gonna be spotlighting the

00:12:54.565 --> 00:12:56.725
<v Speaker 0>wild, ambitious twenty five year journey of the

00:12:56.725 --> 00:13:00.085
<v Speaker 0>ISS from its darling construction in orbit to

00:13:00.085 --> 00:13:02.565
<v Speaker 0>the daily science and survival challenges of living

00:13:02.565 --> 00:13:05.365
<v Speaker 0>beyond Earth. The series walks you inside the

00:13:05.365 --> 00:13:08.165
<v Speaker 0>modules through spacewalks and into moment to moment

00:13:08.165 --> 00:13:10.780
<v Speaker 0>decisions that that have kept humans orbiting our

00:13:10.780 --> 00:13:14.220
<v Speaker 0>planet nonstop for a quarter century. It's a

00:13:14.220 --> 00:13:17.260
<v Speaker 0>part celebration of engineering triumph and part human

00:13:17.260 --> 00:13:21.020
<v Speaker 0>drama of life in microgravity. So pretty kinda

00:13:21.180 --> 00:13:23.905
<v Speaker 0>pretty cool. I mean, we've I'm sure you

00:13:23.905 --> 00:13:25.265
<v Speaker 0>guys know a lot about all the a

00:13:25.265 --> 00:13:28.625
<v Speaker 0>lot a lot of the challenges that, astronauts

00:13:28.625 --> 00:13:31.745
<v Speaker 0>face in space. I think I recently saw

00:13:31.745 --> 00:13:36.340
<v Speaker 0>another article about some, astronauts being stranded. I

00:13:36.340 --> 00:13:37.860
<v Speaker 0>hope that's not in here and I didn't

00:13:37.860 --> 00:13:41.620
<v Speaker 0>just spoil something. But I did see that,

00:13:41.940 --> 00:13:45.460
<v Speaker 0>some Chinese astronauts got are I think their

00:13:45.460 --> 00:13:48.740
<v Speaker 0>stay is being extended because their, return pod

00:13:48.740 --> 00:13:53.055
<v Speaker 0>was damaged. So, definitely gonna keep keep my

00:13:53.055 --> 00:13:54.255
<v Speaker 0>eye out for more news on that. But

00:13:54.255 --> 00:13:57.855
<v Speaker 0>back back to the the PBS episode, here's

00:13:57.855 --> 00:13:59.535
<v Speaker 0>a couple key quotes that we got from

00:13:59.535 --> 00:14:02.355
<v Speaker 0>the article. This is from space dot com,

00:14:02.900 --> 00:14:05.620
<v Speaker 0>written by Jeff Spry. Thank you, Jeff Spry

00:14:05.620 --> 00:14:09.940
<v Speaker 0>for the article. But over twenty five years

00:14:09.940 --> 00:14:12.340
<v Speaker 0>of continual habitation, not a single life was

00:14:12.340 --> 00:14:14.980
<v Speaker 0>lost aboard the ISS. It's a testament to

00:14:14.980 --> 00:14:17.700
<v Speaker 0>the courage and dedication of every astronaut and

00:14:17.700 --> 00:14:20.154
<v Speaker 0>engineer. And that, you know, this kinda really

00:14:20.154 --> 00:14:22.714
<v Speaker 0>underscores the safety record of the station. I

00:14:22.714 --> 00:14:25.675
<v Speaker 0>didn't realize that no one was ever lost

00:14:25.675 --> 00:14:27.695
<v Speaker 0>on there, and this is an extreme environment.

00:14:28.795 --> 00:14:33.050
<v Speaker 0>You you can see just, like, how tedious

00:14:33.110 --> 00:14:36.630
<v Speaker 0>that might have been or how prepared those

00:14:36.630 --> 00:14:39.750
<v Speaker 0>astronauts might have been or, you know, prepared

00:14:39.750 --> 00:14:42.790
<v Speaker 0>to save themselves in every opportunity. So I

00:14:42.790 --> 00:14:47.584
<v Speaker 0>think that's really impressive. Another key quote, every

00:14:47.584 --> 00:14:50.144
<v Speaker 0>step of this ambitious project unfolded against the

00:14:50.144 --> 00:14:53.584
<v Speaker 0>backdrop of a merciless vacuum, dangerous radiation, and

00:14:53.584 --> 00:14:56.464
<v Speaker 0>extreme temperatures. And this kind of reminds us

00:14:56.464 --> 00:15:00.110
<v Speaker 0>of the insane conditions that the ISS overcame

00:15:00.170 --> 00:15:01.690
<v Speaker 0>just while, like, they were in space and

00:15:01.690 --> 00:15:06.030
<v Speaker 0>being built out and how much human adaptation

00:15:06.090 --> 00:15:08.350
<v Speaker 0>was required and, you know, the constant communication

00:15:08.570 --> 00:15:11.084
<v Speaker 0>from ground to space. And even in those

00:15:11.204 --> 00:15:13.765
<v Speaker 0>I'm sure there were moments where communication were

00:15:13.765 --> 00:15:16.084
<v Speaker 0>lost too. So it's, you know, being able

00:15:16.084 --> 00:15:19.445
<v Speaker 0>to overcome those moments of silence and really

00:15:19.445 --> 00:15:22.565
<v Speaker 0>grow as a a team. I'm sure that

00:15:22.565 --> 00:15:24.990
<v Speaker 0>a lot of teamwork was required. So I'm

00:15:24.990 --> 00:15:26.910
<v Speaker 0>I'm now I really wanna watch this PBS

00:15:26.910 --> 00:15:29.870
<v Speaker 0>episode. You know? So I definitely would check

00:15:29.870 --> 00:15:33.250
<v Speaker 0>it out. So part one again is called

00:15:33.470 --> 00:15:35.310
<v Speaker 0>high risk build, and then part two is

00:15:35.310 --> 00:15:37.470
<v Speaker 0>gonna be called science of survival by PBS.

00:15:37.470 --> 00:15:41.285
<v Speaker 0>So check those out. I think that's gonna

00:15:41.285 --> 00:15:43.785
<v Speaker 0>be something really exciting to look forward to.

00:15:46.725 --> 00:15:50.805
<v Speaker 0>Next article, China solves century old problem with

00:15:50.805 --> 00:15:53.125
<v Speaker 0>new analog chip that is a thousand times

00:15:53.125 --> 00:15:56.150
<v Speaker 0>faster than high end NVIDIA GPUs. Now I

00:15:56.150 --> 00:15:58.790
<v Speaker 0>think this title's a little bit maybe, but,

00:15:59.910 --> 00:16:00.950
<v Speaker 0>let me give you guys a little bit

00:16:00.950 --> 00:16:04.230
<v Speaker 0>of context. Researchers from Peking University published a

00:16:04.230 --> 00:16:07.525
<v Speaker 0>paper on October thirteenth twenty twenty five in

00:16:07.525 --> 00:16:11.605
<v Speaker 0>journal Nature Electronics titled Precise and Scalable Analog

00:16:11.605 --> 00:16:15.925
<v Speaker 0>Matrix Equation Solving Using Irresistive Random Access Memory

00:16:15.925 --> 00:16:19.410
<v Speaker 0>Chips. So they developed an analog computing chip

00:16:19.410 --> 00:16:22.769
<v Speaker 0>based on resistive random access memory, our RAM

00:16:22.769 --> 00:16:29.170
<v Speaker 0>cells, and they reportedly achieved performance and energy

00:16:29.170 --> 00:16:33.190
<v Speaker 0>efficiently, markedly superior to current digital GPU processors.

00:16:34.465 --> 00:16:36.245
<v Speaker 0>And then one of the big things with

00:16:36.785 --> 00:16:39.265
<v Speaker 0>analog computing, it's, it's kind of been limited

00:16:39.265 --> 00:16:41.825
<v Speaker 0>by the precision and scalability issues just because

00:16:41.825 --> 00:16:43.905
<v Speaker 0>I think it was not fast enough and

00:16:43.905 --> 00:16:47.125
<v Speaker 0>needed, lots of power to do those computations.

00:16:48.300 --> 00:16:49.980
<v Speaker 0>But this new work kinda claims to have

00:16:49.980 --> 00:16:53.100
<v Speaker 0>matched the digital level precision. So they have

00:16:53.100 --> 00:16:56.940
<v Speaker 0>twenty four bit fixed fixed point precision, which

00:16:56.940 --> 00:17:00.380
<v Speaker 0>is comparable to thirty two bit floating. Thirty

00:17:00.380 --> 00:17:04.575
<v Speaker 0>two bit floating point precision. That's that is

00:17:04.575 --> 00:17:09.715
<v Speaker 0>a mouthful. While did while delivering extremely high

00:17:09.855 --> 00:17:17.070
<v Speaker 0>throughput. So these, these chips which use our

00:17:17.070 --> 00:17:20.430
<v Speaker 0>RAM arrays for a matrix inversion in large

00:17:20.430 --> 00:17:23.550
<v Speaker 0>scale signal processing tasks was up to one

00:17:23.550 --> 00:17:27.010
<v Speaker 0>thousand times the throughput and a hundred times

00:17:27.070 --> 00:17:31.015
<v Speaker 0>the energy efficiency of top digital processors. While

00:17:31.015 --> 00:17:35.495
<v Speaker 0>achieving comparable precision by moving key computations directly

00:17:35.495 --> 00:17:39.735
<v Speaker 0>into memory, compute in memory, and leveraging analog

00:17:39.735 --> 00:17:44.340
<v Speaker 0>physical operations rather than sequential digital logic. This

00:17:44.340 --> 00:17:46.740
<v Speaker 0>innovation could pave a new route for AI

00:17:46.740 --> 00:17:50.340
<v Speaker 0>training, wireless systems like six g, and other

00:17:50.340 --> 00:17:55.940
<v Speaker 0>compute heavy workloads. Kind of interesting. I think

00:17:55.940 --> 00:17:59.385
<v Speaker 0>this is kind of based around a, like

00:17:59.385 --> 00:18:04.425
<v Speaker 0>a mathematics achievement or a mathematics, because it

00:18:04.425 --> 00:18:09.305
<v Speaker 0>earlier it said, where was it? Using a

00:18:09.305 --> 00:18:13.465
<v Speaker 0>scalable analog matrix equation solving using resistive random

00:18:13.465 --> 00:18:18.400
<v Speaker 0>access memory chips. So definitely some linear algebra

00:18:18.400 --> 00:18:24.480
<v Speaker 0>here going on with, the analog chips. And

00:18:24.480 --> 00:18:26.800
<v Speaker 0>I'm I'm sure they've figured out a way

00:18:26.800 --> 00:18:34.225
<v Speaker 0>to efficiently compute within the RM instead of

00:18:34.225 --> 00:18:37.284
<v Speaker 0>having to pass that data back and forth,

00:18:38.304 --> 00:18:45.580
<v Speaker 0>from memory to the GPU. So, early when

00:18:45.580 --> 00:18:47.220
<v Speaker 0>I was reading this, I I thought it

00:18:47.220 --> 00:18:50.440
<v Speaker 0>was akin to, something like caching or memorization,

00:18:50.980 --> 00:18:54.260
<v Speaker 0>but reading more into it, it's not not

00:18:54.260 --> 00:19:00.645
<v Speaker 0>quite the same thing. But something to look

00:19:00.645 --> 00:19:03.445
<v Speaker 0>into. Definitely this article is really, really, cool.

00:19:03.445 --> 00:19:06.245
<v Speaker 0>And it's definitely a cool breakthrough. For all

00:19:06.245 --> 00:19:09.125
<v Speaker 0>you tech fans or professionals, this development suggests

00:19:09.125 --> 00:19:11.285
<v Speaker 0>a major shift could be coming in computing

00:19:11.285 --> 00:19:15.049
<v Speaker 0>architectures. Analog and hybrid compute in memory systems

00:19:15.049 --> 00:19:18.169
<v Speaker 0>might compete seriously with traditional GPUs, especially for

00:19:18.169 --> 00:19:21.690
<v Speaker 0>AI and signal processing workloads. And I'm sure

00:19:21.690 --> 00:19:25.289
<v Speaker 0>this is gonna well, if if this, you

00:19:25.289 --> 00:19:28.815
<v Speaker 0>know, spreads, and I'm sure it will because

00:19:28.815 --> 00:19:33.615
<v Speaker 0>why wouldn't, why wouldn't you use a system

00:19:33.615 --> 00:19:36.195
<v Speaker 0>that was if it if it was as

00:19:36.335 --> 00:19:40.110
<v Speaker 0>impactful as it's suggesting, a thousand times, faster

00:19:40.110 --> 00:19:42.909
<v Speaker 0>and a hundred times more efficient. No. It

00:19:42.909 --> 00:19:45.870
<v Speaker 0>was a thousand times throughput. So let's just

00:19:45.870 --> 00:19:48.590
<v Speaker 0>be clear. Thousand times of throughput and a

00:19:48.590 --> 00:19:52.495
<v Speaker 0>hundred times the energy efficiency. So and I

00:19:52.495 --> 00:19:53.934
<v Speaker 0>think it's just because you don't have to

00:19:53.934 --> 00:19:56.655
<v Speaker 0>communicate with the GPU and instead you're computing

00:19:56.655 --> 00:19:58.815
<v Speaker 0>it in memory. So then the extra step

00:19:58.815 --> 00:20:01.375
<v Speaker 0>of passing them that information to the GPU

00:20:01.375 --> 00:20:03.215
<v Speaker 0>to be calculated is being cut out of

00:20:03.215 --> 00:20:07.710
<v Speaker 0>the the equation. So that's kinda cool. But

00:20:07.710 --> 00:20:09.650
<v Speaker 0>I'm sure this is gonna result in more

00:20:09.790 --> 00:20:11.870
<v Speaker 0>energy efficient battery life if they start using

00:20:11.870 --> 00:20:14.990
<v Speaker 0>these types of CPUs or, you know, our

00:20:14.990 --> 00:20:17.390
<v Speaker 0>RAM and phones in the future. So that

00:20:17.390 --> 00:20:18.990
<v Speaker 0>could be kinda cool to to see coming

00:20:18.990 --> 00:20:23.665
<v Speaker 0>up. Let's see what we got next. Oh,

00:20:23.665 --> 00:20:25.345
<v Speaker 0>the oh, and just to be clear that,

00:20:25.585 --> 00:20:28.545
<v Speaker 0>article just now is from Live Science, by

00:20:28.545 --> 00:20:31.045
<v Speaker 0>Owen Hughes. Thank you, Owen, for the article.

00:20:33.530 --> 00:20:35.770
<v Speaker 0>We got this new this next article by

00:20:35.770 --> 00:20:42.250
<v Speaker 0>InfoQ. This one's written by Daniel Dominguez. We

00:20:42.250 --> 00:20:45.850
<v Speaker 0>have anthropic expands cloud code to web and

00:20:45.850 --> 00:20:50.385
<v Speaker 0>mobile platforms. You guys know I always talk

00:20:50.385 --> 00:20:52.065
<v Speaker 0>about AI on the show. It's a big

00:20:52.065 --> 00:20:55.825
<v Speaker 0>thing right now. Anthropic, the AI company behind

00:20:55.825 --> 00:20:58.705
<v Speaker 0>the Claude family of large language models, has

00:20:58.705 --> 00:21:01.890
<v Speaker 0>been actively expanding its tools for developers. The

00:21:01.890 --> 00:21:05.170
<v Speaker 0>Cloud Code environment was previously available primarily via

00:21:05.170 --> 00:21:08.850
<v Speaker 0>desktop or a API integrations. The recent update

00:21:08.850 --> 00:21:11.730
<v Speaker 0>opens access to web and mobile browsers, allowing

00:21:11.730 --> 00:21:15.410
<v Speaker 0>developers to use the coding assistant anywhere. What

00:21:15.410 --> 00:21:18.945
<v Speaker 0>the heck? Cloud code supports multi file coding

00:21:18.945 --> 00:21:23.825
<v Speaker 0>tasks, conversational context, inline explanations, air feedback, and

00:21:23.825 --> 00:21:27.045
<v Speaker 0>now with the web version, parallel job execution.

00:21:27.585 --> 00:21:30.705
<v Speaker 0>Wow. Enabling multiple tasks to run simultaneously in

00:21:30.705 --> 00:21:34.410
<v Speaker 0>a browser environment. This move comes amid growing

00:21:34.410 --> 00:21:37.210
<v Speaker 0>competition in AI powered coding assistance, like a

00:21:37.210 --> 00:21:40.650
<v Speaker 0>GitHub Copilot and AWS Kiro and at a

00:21:40.650 --> 00:21:44.250
<v Speaker 0>time where developer workflows are increasingly shifting towards

00:21:44.250 --> 00:21:50.304
<v Speaker 0>browser based tooling and remote cloud setups. This

00:21:50.304 --> 00:21:55.105
<v Speaker 0>is cool. I love to see, all these,

00:21:55.424 --> 00:22:01.184
<v Speaker 0>big companies compete, but it's it's cool to

00:22:01.184 --> 00:22:02.945
<v Speaker 0>see where we're going with all this. Everyone

00:22:02.945 --> 00:22:05.790
<v Speaker 0>is trying to find new ways to automate

00:22:05.790 --> 00:22:10.130
<v Speaker 0>our life. I recently, there was a conversation

00:22:10.270 --> 00:22:14.270
<v Speaker 0>recently regarding SEO and stuff, and I found

00:22:14.270 --> 00:22:18.365
<v Speaker 0>it interesting that the the SEO for or,

00:22:18.365 --> 00:22:21.645
<v Speaker 0>like, if you guys search podcast AI, you

00:22:21.645 --> 00:22:27.645
<v Speaker 0>know, in general or AI podcasting, there's just,

00:22:27.645 --> 00:22:32.940
<v Speaker 0>like, all these platforms for automating, making, like,

00:22:32.940 --> 00:22:35.980
<v Speaker 0>podcasting, like podcasts that are made by AI.

00:22:35.980 --> 00:22:38.620
<v Speaker 0>Like, the AIs are the ones talking. And

00:22:38.620 --> 00:22:42.140
<v Speaker 0>I'm maybe I just don't get it. But

00:22:42.140 --> 00:22:44.860
<v Speaker 0>why why would you wanna do this? Why

00:22:44.860 --> 00:22:49.895
<v Speaker 0>why would you wanna do that? Like, who

00:22:51.715 --> 00:22:53.155
<v Speaker 0>is it just that they read the script

00:22:53.155 --> 00:22:55.955
<v Speaker 0>that you write? I don't understand. I'm I'm

00:22:56.035 --> 00:22:59.155
<v Speaker 0>I am I was baffled. Why do people

00:22:59.155 --> 00:23:01.960
<v Speaker 0>wanna automate away the things that are enjoyable?

00:23:02.020 --> 00:23:05.160
<v Speaker 0>This is not necessarily a quote, unquote job.

00:23:05.220 --> 00:23:07.060
<v Speaker 0>You know, it's something that I'm I'm happy

00:23:07.060 --> 00:23:09.060
<v Speaker 0>to be here for. I'm happy to I

00:23:09.060 --> 00:23:10.660
<v Speaker 0>wanna be here. I wanna talk about these

00:23:10.660 --> 00:23:12.100
<v Speaker 0>things, and I wanna share it with people

00:23:12.100 --> 00:23:14.260
<v Speaker 0>because I find them interesting. But instead, it's

00:23:14.260 --> 00:23:20.664
<v Speaker 0>like a new platform to generate revenue, which

00:23:20.664 --> 00:23:24.345
<v Speaker 0>is sick if I'm being honest. But, hey,

00:23:24.345 --> 00:23:28.840
<v Speaker 0>that's just an opinion. Anthropic has rolled out

00:23:28.840 --> 00:23:31.320
<v Speaker 0>cloud code via web and mobile platforms, making

00:23:31.320 --> 00:23:34.380
<v Speaker 0>it AI powered development environment accessible beyond traditional

00:23:34.520 --> 00:23:37.559
<v Speaker 0>desktop setups. Now developers can write, edit, and

00:23:37.559 --> 00:23:40.919
<v Speaker 0>execute code across files with conversational context and

00:23:40.919 --> 00:23:43.125
<v Speaker 0>even run multiple jobs at once straight from

00:23:43.125 --> 00:23:48.245
<v Speaker 0>a browser or mobile device. Anthropic has expanded

00:23:48.245 --> 00:23:50.165
<v Speaker 0>the availability of cloud code, bringing it to

00:23:50.165 --> 00:23:52.645
<v Speaker 0>the web and mobile platform. This is really

00:23:52.645 --> 00:23:54.885
<v Speaker 0>cool. I think it's like we were just

00:23:54.885 --> 00:23:57.340
<v Speaker 0>talking about Comet. I I think it's Comet

00:23:57.340 --> 00:24:01.580
<v Speaker 0>browser, which is I don't even know how

00:24:01.580 --> 00:24:05.179
<v Speaker 0>it's doing. Is that has anyone tried it?

00:24:05.179 --> 00:24:07.919
<v Speaker 0>I still haven't. I haven't found a need.

00:24:08.299 --> 00:24:10.380
<v Speaker 0>Automate what what do I have to automate

00:24:10.380 --> 00:24:13.855
<v Speaker 0>in my life? Deleting spam emails? Jeez. I

00:24:14.315 --> 00:24:20.235
<v Speaker 0>don't have five minutes, I guess. But it's

00:24:21.755 --> 00:24:24.015
<v Speaker 0>this definitely seems like a little more lightweight

00:24:24.235 --> 00:24:27.120
<v Speaker 0>version. Something that you can just have, like,

00:24:27.120 --> 00:24:29.679
<v Speaker 0>a extension or a plug in. So it

00:24:29.679 --> 00:24:32.179
<v Speaker 0>could be interesting. I wonder how heavy it'll

00:24:32.619 --> 00:24:37.379
<v Speaker 0>make your your browser though. That's my concern.

00:24:38.965 --> 00:24:41.365
<v Speaker 0>I want my my browser already makes my

00:24:41.365 --> 00:24:43.924
<v Speaker 0>computer scream. It's got, like I've got maybe

00:24:43.924 --> 00:24:48.164
<v Speaker 0>thirty thirty, forty tabs open right now. But

00:24:48.164 --> 00:24:50.345
<v Speaker 0>you may ask why, and thank god for

00:24:51.220 --> 00:24:53.960
<v Speaker 0>the memory saving systems that they have implemented

00:24:54.019 --> 00:24:56.820
<v Speaker 0>in these tabs. So it's not as bad

00:24:56.820 --> 00:24:59.159
<v Speaker 0>as you might think, but still, you know,

00:24:59.940 --> 00:25:02.200
<v Speaker 0>I don't know if I could handle twenty

00:25:02.259 --> 00:25:05.205
<v Speaker 0>tabs with AI doing stuff in each of

00:25:05.205 --> 00:25:08.565
<v Speaker 0>them. I I might need more RAM, which

00:25:08.565 --> 00:25:10.885
<v Speaker 0>I'm just not I I I'm just I

00:25:10.885 --> 00:25:13.525
<v Speaker 0>just I don't know if now is the

00:25:13.525 --> 00:25:17.385
<v Speaker 0>time for that, so we'll see. Who knows?

00:25:17.445 --> 00:25:19.365
<v Speaker 0>I was thinking about a little computer upgrade,

00:25:19.365 --> 00:25:21.980
<v Speaker 0>but I don't know if I I really

00:25:21.980 --> 00:25:23.500
<v Speaker 0>wanna do that right now. It's a big

00:25:23.500 --> 00:25:28.059
<v Speaker 0>investment. But early developer feedback on this tool

00:25:28.059 --> 00:25:30.780
<v Speaker 0>suggests that expanded access makes Claude Code a

00:25:30.780 --> 00:25:33.500
<v Speaker 0>practical alternative without needing local setup or plug

00:25:33.500 --> 00:25:37.894
<v Speaker 0>in installations. This is a little ridiculous to

00:25:37.894 --> 00:25:39.975
<v Speaker 0>me because if for anyone that's installed Claude

00:25:39.975 --> 00:25:43.495
<v Speaker 0>code before, you know, it's just a copy

00:25:43.495 --> 00:25:46.634
<v Speaker 0>and paste from a node package manager download.

00:25:46.774 --> 00:25:48.615
<v Speaker 0>Like, if if you know the endpoint, you

00:25:48.615 --> 00:25:52.160
<v Speaker 0>can just type it in. What what what

00:25:52.160 --> 00:25:54.160
<v Speaker 0>setup? I guess now you don't have to

00:25:54.160 --> 00:25:55.760
<v Speaker 0>even look that up. You can just press

00:25:55.760 --> 00:25:59.920
<v Speaker 0>activate on your, browser extensions. So I don't

00:25:59.920 --> 00:26:03.620
<v Speaker 0>know how it's being, distributed exactly. Let's see.

00:26:04.245 --> 00:26:05.765
<v Speaker 0>Who knows? Mate, let me let let me

00:26:05.765 --> 00:26:08.565
<v Speaker 0>look in the extensions plugins right now. We'll

00:26:08.565 --> 00:26:15.385
<v Speaker 0>see if Claude codes in here. I don't

00:26:15.605 --> 00:26:20.919
<v Speaker 0>see it yet. So, I'll have to look

00:26:20.919 --> 00:26:22.440
<v Speaker 0>more into this. Maybe we'll hear more news

00:26:22.440 --> 00:26:23.559
<v Speaker 0>on it and I'll I'll get back to

00:26:23.559 --> 00:26:24.919
<v Speaker 0>you guys on this. I'll definitely look into

00:26:24.919 --> 00:26:26.679
<v Speaker 0>it a little bit more on how to

00:26:26.679 --> 00:26:33.465
<v Speaker 0>exactly get that set up. But it can't

00:26:33.465 --> 00:26:44.960
<v Speaker 0>be that hard. Let Let me just follow

00:26:44.960 --> 00:26:51.440
<v Speaker 0>this link, Claude code on the web. So

00:26:51.440 --> 00:26:55.280
<v Speaker 0>getting started. Visit claud dot com slash code

00:26:55.280 --> 00:26:58.020
<v Speaker 0>to connect your first repository and start delegating

00:26:58.080 --> 00:27:00.265
<v Speaker 0>tests. Let's just follow the link. Who knows?

00:27:01.205 --> 00:27:08.405
<v Speaker 0>Oh, it what what is this? I don't

00:27:08.485 --> 00:27:10.005
<v Speaker 0>it's okay. So it wants me to connect

00:27:10.005 --> 00:27:11.445
<v Speaker 0>to my GitHub. I don't think I wanna

00:27:11.445 --> 00:27:13.830
<v Speaker 0>do that. So we're not gonna do this,

00:27:14.870 --> 00:27:18.070
<v Speaker 0>right now. If oh, man. If they only

00:27:18.070 --> 00:27:19.350
<v Speaker 0>let me do it with my Google account,

00:27:19.350 --> 00:27:20.470
<v Speaker 0>I'd be okay with it. But I don't

00:27:20.470 --> 00:27:21.669
<v Speaker 0>really want them to do it with my

00:27:21.669 --> 00:27:25.590
<v Speaker 0>GitHub. It's because you so you I guess

00:27:25.590 --> 00:27:38.065
<v Speaker 0>you you can, basically, you it does things

00:27:38.065 --> 00:27:44.080
<v Speaker 0>through GitHub. What? I don't understand. I'll look

00:27:44.080 --> 00:27:45.680
<v Speaker 0>more into this and expand on this in

00:27:45.680 --> 00:27:48.400
<v Speaker 0>the future. I won't forget about this, guys.

00:27:48.400 --> 00:27:52.240
<v Speaker 0>I promise. But let's move on. I don't

00:27:52.240 --> 00:27:54.135
<v Speaker 0>think we wanna talk too much about Claude,

00:27:54.375 --> 00:27:57.815
<v Speaker 0>except the next article by Tom's Guide from

00:27:57.815 --> 00:28:02.135
<v Speaker 0>Alex Hughes is another Anthropic article. I use

00:28:02.135 --> 00:28:05.095
<v Speaker 0>Anthropic's AI assistant Claude to save me hours

00:28:05.095 --> 00:28:07.335
<v Speaker 0>of research, and these are my four go

00:28:07.335 --> 00:28:09.960
<v Speaker 0>to prompts. Now, I can't remember if we

00:28:09.960 --> 00:28:11.800
<v Speaker 0>already did this, but I'm just going to

00:28:11.800 --> 00:28:15.580
<v Speaker 0>give you guys the prompts straight up. And

00:28:15.880 --> 00:28:18.040
<v Speaker 0>honestly, I might just put together a prompt

00:28:18.040 --> 00:28:20.840
<v Speaker 0>page on the site so that you guys

00:28:20.840 --> 00:28:22.520
<v Speaker 0>can check these out. Cause I have quite

00:28:22.520 --> 00:28:24.860
<v Speaker 0>the list. If you actually go to the

00:28:25.275 --> 00:28:29.295
<v Speaker 0>claw documentation page, they have some good, like,

00:28:29.675 --> 00:28:33.375
<v Speaker 0>from the developers themselves, the the the actual

00:28:34.795 --> 00:28:38.540
<v Speaker 0>prompts that they suggest using to to reach

00:28:38.540 --> 00:28:41.740
<v Speaker 0>certain goals. So a couple, that they that

00:28:41.740 --> 00:28:43.980
<v Speaker 0>I have on my little power prompt list.

00:28:43.980 --> 00:28:47.040
<v Speaker 0>Okay? So you can do something like leverage

00:28:47.260 --> 00:28:52.560
<v Speaker 0>interleaved thinking, or you can, code you can

00:28:53.355 --> 00:28:59.195
<v Speaker 0>reduce hallucinations, by saying specific things. Give grounded

00:28:59.195 --> 00:29:02.155
<v Speaker 0>and hallucination free answers. Like, having making that

00:29:02.155 --> 00:29:04.795
<v Speaker 0>suggestion so it does the background check. Or

00:29:04.795 --> 00:29:07.375
<v Speaker 0>doing a markdown suppression. It does a markdown

00:29:07.675 --> 00:29:10.130
<v Speaker 0>dump for all those all those texts, you

00:29:10.130 --> 00:29:12.770
<v Speaker 0>know. But the ones that come with this,

00:29:12.770 --> 00:29:15.570
<v Speaker 0>I think this specific article, we'll give you

00:29:15.650 --> 00:29:17.169
<v Speaker 0>we'll give to you guys. And I have

00:29:17.169 --> 00:29:18.530
<v Speaker 0>the four of them here at the bottom

00:29:18.530 --> 00:29:20.850
<v Speaker 0>of my list from Tom's guide. The first

00:29:20.850 --> 00:29:24.554
<v Speaker 0>one is finding qualified sources. I am writing

00:29:24.554 --> 00:29:27.674
<v Speaker 0>a paper on insert subject using all of

00:29:27.674 --> 00:29:30.655
<v Speaker 0>the tools at your disposable, including web searches,

00:29:31.034 --> 00:29:33.835
<v Speaker 0>find sources that both support and refute this

00:29:33.835 --> 00:29:36.715
<v Speaker 0>subject. They should be categorized into sources that

00:29:36.715 --> 00:29:38.630
<v Speaker 0>have been peer reviewed and not peer reviewed

00:29:38.630 --> 00:29:42.149
<v Speaker 0>and should only come from reputable sources. And

00:29:42.149 --> 00:29:43.750
<v Speaker 0>this is a good way to get a

00:29:43.750 --> 00:29:46.630
<v Speaker 0>sorted list of credible references to start your

00:29:46.630 --> 00:29:49.750
<v Speaker 0>research. That's cool. You know, the one of

00:29:49.750 --> 00:29:56.174
<v Speaker 0>the biggest challenges of even developing, an argument

00:29:56.315 --> 00:29:59.355
<v Speaker 0>for a research topic is is literally finding

00:29:59.355 --> 00:30:01.674
<v Speaker 0>the support for your the beliefs that you

00:30:01.674 --> 00:30:03.595
<v Speaker 0>are putting out there. And they're not just

00:30:03.595 --> 00:30:07.550
<v Speaker 0>beliefs, they're freaking facts based on this article,

00:30:07.550 --> 00:30:10.190
<v Speaker 0>you know. So pretty cool. If you're doing

00:30:10.190 --> 00:30:13.870
<v Speaker 0>a research paper, don't have the divide the

00:30:13.870 --> 00:30:15.470
<v Speaker 0>AI write it for you, you write the

00:30:15.470 --> 00:30:18.350
<v Speaker 0>paper helping let it help you get some

00:30:18.350 --> 00:30:23.175
<v Speaker 0>qualified sources. How about, performing a deep dive

00:30:23.315 --> 00:30:26.115
<v Speaker 0>deep dive on a topic? I need a

00:30:26.115 --> 00:30:30.035
<v Speaker 0>comprehensive analysis of specific topic. Please search for

00:30:30.035 --> 00:30:32.915
<v Speaker 0>the most current and authoritative sources and verify

00:30:32.915 --> 00:30:35.980
<v Speaker 0>accuracy. Cover as many of the core areas

00:30:35.980 --> 00:30:39.580
<v Speaker 0>of this subject as possible. And use you

00:30:39.580 --> 00:30:41.340
<v Speaker 0>use this when you want a broad but

00:30:41.340 --> 00:30:45.180
<v Speaker 0>detailed overview of a subject. The next one

00:30:45.180 --> 00:30:48.725
<v Speaker 0>is a comparative analysis. Help me compare concept

00:30:48.865 --> 00:30:52.625
<v Speaker 0>a and concept B across multiple dimensions, search

00:30:52.625 --> 00:30:56.225
<v Speaker 0>for authoritative searches or sources on each create

00:30:56.225 --> 00:31:00.600
<v Speaker 0>a structured comparison, highlighting similarities, differences, strengths, and

00:31:00.600 --> 00:31:03.560
<v Speaker 0>weaknesses, and provide examples that illustrate the key

00:31:03.560 --> 00:31:08.440
<v Speaker 0>distinctions. Include citations for all major claims. Great

00:31:08.440 --> 00:31:10.120
<v Speaker 0>for when you need to understand how two

00:31:10.120 --> 00:31:14.485
<v Speaker 0>ideas relate, differ, and interact. So this could

00:31:14.485 --> 00:31:18.725
<v Speaker 0>go hand in hand with that, qualified sore

00:31:18.804 --> 00:31:21.205
<v Speaker 0>sources call. I feel like they're doing a

00:31:21.205 --> 00:31:25.765
<v Speaker 0>very specific type of research. Break down my

00:31:25.765 --> 00:31:30.110
<v Speaker 0>argument, devil's advocate style. My argument is insert

00:31:30.110 --> 00:31:32.429
<v Speaker 0>argument or point. I want you to be

00:31:32.429 --> 00:31:35.230
<v Speaker 0>the devil's advocate and argue against this. We

00:31:35.230 --> 00:31:37.150
<v Speaker 0>will then go back and forth making our

00:31:37.150 --> 00:31:40.110
<v Speaker 0>argument for our respective side. Only use well

00:31:40.110 --> 00:31:43.635
<v Speaker 0>informed and research backed points. This one helps

00:31:43.635 --> 00:31:46.035
<v Speaker 0>test the strength of your reasoning and uncover

00:31:46.035 --> 00:31:49.975
<v Speaker 0>weaknesses you might have missed. So kinda cool.

00:31:50.995 --> 00:31:54.355
<v Speaker 0>Definitely helps strengthen any, sort of research paper

00:31:54.355 --> 00:31:58.390
<v Speaker 0>you're doing. This kinda definitely seems, augmented towards,

00:31:58.790 --> 00:32:04.070
<v Speaker 0>research papers, but definitely a cool thing to

00:32:04.070 --> 00:32:10.595
<v Speaker 0>try out. The research that is suggested by

00:32:10.595 --> 00:32:15.635
<v Speaker 0>Claude documentation is this actually. So I'm going

00:32:15.635 --> 00:32:18.674
<v Speaker 0>to give you guys a key insight here,

00:32:18.674 --> 00:32:21.475
<v Speaker 0>a key prompt, power prompt from Claude themselves

00:32:21.475 --> 00:32:24.789
<v Speaker 0>or anthropic themselves. Search for this information in

00:32:24.789 --> 00:32:27.830
<v Speaker 0>a structured way. As you gather data, develop

00:32:27.830 --> 00:32:31.509
<v Speaker 0>several competing hypotheses. Track your confidence levels in

00:32:31.509 --> 00:32:35.110
<v Speaker 0>your progress notes to improve calibration. Regularly self

00:32:35.110 --> 00:32:38.345
<v Speaker 0>critique your approach and plan. Update a hypothesis

00:32:38.405 --> 00:32:41.545
<v Speaker 0>tree or research notes file to persist information

00:32:41.605 --> 00:32:45.285
<v Speaker 0>and provide transparency. Break down this complex research

00:32:45.285 --> 00:32:49.560
<v Speaker 0>task systematically. So, yeah, that's a little bit

00:32:49.560 --> 00:32:52.380
<v Speaker 0>of a mouthful, but you can kinda get

00:32:52.380 --> 00:32:55.260
<v Speaker 0>the idea that, that's being built here. You

00:32:55.260 --> 00:33:01.360
<v Speaker 0>can have the generative LLM create these lists

00:33:01.580 --> 00:33:05.025
<v Speaker 0>that track confidence levels and help it calibrate

00:33:05.025 --> 00:33:07.825
<v Speaker 0>itself to a, a better approach and plan.

00:33:07.825 --> 00:33:09.745
<v Speaker 0>So pretty cool stuff. I will try to

00:33:09.745 --> 00:33:11.985
<v Speaker 0>put together a little power prompt, page that

00:33:11.985 --> 00:33:13.585
<v Speaker 0>I'll put in the header that you guys

00:33:13.585 --> 00:33:16.544
<v Speaker 0>can check out where I'll include all of,

00:33:16.865 --> 00:33:18.940
<v Speaker 0>the power prompts that that I found over

00:33:18.940 --> 00:33:23.419
<v Speaker 0>time that really help with, any sort of

00:33:23.419 --> 00:33:29.440
<v Speaker 0>research, document building, even suppressing hallucinations, you know?

00:33:29.580 --> 00:33:32.895
<v Speaker 0>But definitely open to hearing some suggestions. I

00:33:32.895 --> 00:33:34.835
<v Speaker 0>wanna hear what you guys are doing for

00:33:35.695 --> 00:33:37.775
<v Speaker 0>a pruning, you know, if you guys are

00:33:37.775 --> 00:33:42.355
<v Speaker 0>using the prunters. But these are interesting machines

00:33:42.575 --> 00:33:46.310
<v Speaker 0>or or or systems that are impressive in

00:33:46.310 --> 00:33:47.750
<v Speaker 0>their own right. But we do need to

00:33:47.750 --> 00:33:49.830
<v Speaker 0>remember the last conversation we had about this

00:33:49.830 --> 00:33:53.030
<v Speaker 0>that they are simply pattern generators. You can

00:33:53.030 --> 00:33:56.790
<v Speaker 0>watch videos on how people find how people

00:33:56.790 --> 00:33:59.110
<v Speaker 0>break these, you know, by just by talking

00:33:59.110 --> 00:34:01.845
<v Speaker 0>to it or editing history in the document.

00:34:01.845 --> 00:34:04.485
<v Speaker 0>So you need to be really careful on

00:34:04.485 --> 00:34:11.285
<v Speaker 0>what you're divulging to these language models. Alright.

00:34:11.285 --> 00:34:13.845
<v Speaker 0>I did have another anthropic article lined up.

00:34:13.845 --> 00:34:16.380
<v Speaker 0>You can see where my, allegiance lies, but

00:34:16.380 --> 00:34:18.059
<v Speaker 0>let's move on. Let's let's not talk about

00:34:18.059 --> 00:34:21.020
<v Speaker 0>anthropic anymore. A paradigm shift in RAM is

00:34:21.020 --> 00:34:24.940
<v Speaker 0>about to make computing unstoppable. This is, from

00:34:24.940 --> 00:34:31.825
<v Speaker 0>Popular Mechanics by Darren Orf. But this looks

00:34:31.825 --> 00:34:43.460
<v Speaker 0>kinda cool. So scientists at Hebrew University of

00:34:43.460 --> 00:34:46.820
<v Speaker 0>Jerusalem have in reported a new mechanism by

00:34:46.820 --> 00:34:49.720
<v Speaker 0>which laser light can directly control a magnetic

00:34:49.780 --> 00:34:53.295
<v Speaker 0>state of materials. A discovery with major implications

00:34:53.615 --> 00:34:57.775
<v Speaker 0>for magna magnetoresistive RAM. So more RAM talk

00:34:57.775 --> 00:35:00.895
<v Speaker 0>today. This is MRAM and future data source

00:35:00.895 --> 00:35:04.194
<v Speaker 0>technology. MRAM is a form of non volatile

00:35:04.335 --> 00:35:08.670
<v Speaker 0>memory which retains data without power that uses

00:35:08.670 --> 00:35:11.890
<v Speaker 0>magnetic tunnel junctions rather than charge based storage.

00:35:12.190 --> 00:35:16.530
<v Speaker 0>It's already considered promising for high performance energy

00:35:16.590 --> 00:35:21.355
<v Speaker 0>efficient memory. And the breakthrough the breakthrough involves

00:35:21.355 --> 00:35:25.595
<v Speaker 0>using rapid oscillating light waves lasers to switch

00:35:25.595 --> 00:35:28.315
<v Speaker 0>magnetic states rather than relying solely on electrical

00:35:28.315 --> 00:35:31.435
<v Speaker 0>currents. And this could point towards dramatically faster,

00:35:31.435 --> 00:35:39.170
<v Speaker 0>more efficient memory devices. So that was our

00:35:39.170 --> 00:35:42.050
<v Speaker 0>little bit of context there. And then, let's

00:35:42.050 --> 00:35:43.090
<v Speaker 0>get into like a little bit of a

00:35:43.090 --> 00:35:47.090
<v Speaker 0>summary. Researchers have unveiled a laser based technique

00:35:47.090 --> 00:35:50.025
<v Speaker 0>that can control magnetic bits opening the door

00:35:50.025 --> 00:35:53.545
<v Speaker 0>to a new generation of MRAM devices that

00:35:53.545 --> 00:35:56.985
<v Speaker 0>could be much faster, more efficient, or more

00:35:56.985 --> 00:36:00.605
<v Speaker 0>energy efficient and potentially bridge towards quantum compatible

00:36:00.665 --> 00:36:03.500
<v Speaker 0>memory. While the technology is still in early

00:36:03.500 --> 00:36:07.180
<v Speaker 0>stages, the implications are broad. Magic computers where

00:36:07.180 --> 00:36:10.060
<v Speaker 0>memory switching is done by light, reducing power

00:36:10.060 --> 00:36:13.740
<v Speaker 0>consumption, increasing speed, and possibly paving the way

00:36:13.740 --> 00:36:16.480
<v Speaker 0>for memory systems that work differently from today's

00:36:17.105 --> 00:36:22.785
<v Speaker 0>DRAM, SRAM, or Flash. That is cool. I

00:36:22.785 --> 00:36:24.385
<v Speaker 0>didn't even know that there was something called

00:36:24.385 --> 00:36:28.305
<v Speaker 0>magnetic RAM or magneto hold on. There's a

00:36:28.305 --> 00:36:33.920
<v Speaker 0>specific term for it. Magneto resistive ram. Cool.

00:36:36.140 --> 00:36:39.180
<v Speaker 0>So the this particular discovery has a lot

00:36:39.180 --> 00:36:41.980
<v Speaker 0>of, far reaching implications, particularly in the domain

00:36:41.980 --> 00:36:45.020
<v Speaker 0>of, of data recording using light and nano

00:36:45.020 --> 00:36:51.565
<v Speaker 0>magnets. So this is, this could be a

00:36:51.565 --> 00:36:53.805
<v Speaker 0>little bit of a leap in how, memory

00:36:53.805 --> 00:36:56.845
<v Speaker 0>is implemented or or how it works in

00:36:56.845 --> 00:37:01.270
<v Speaker 0>our future systems. But I guess now we've

00:37:01.270 --> 00:37:04.890
<v Speaker 0>already suggested a competitive edge in our RAM

00:37:05.829 --> 00:37:09.190
<v Speaker 0>with the new analog computing technique. So it

00:37:09.190 --> 00:37:11.190
<v Speaker 0>could be kind of interesting to see how

00:37:11.190 --> 00:37:12.630
<v Speaker 0>that shapes up in the future. I mean,

00:37:12.630 --> 00:37:14.150
<v Speaker 0>they may have their own purposes, so that

00:37:14.150 --> 00:37:18.295
<v Speaker 0>might be the specific use case, scenario. But

00:37:18.295 --> 00:37:21.015
<v Speaker 0>this hints at the potential realization of ultra

00:37:21.015 --> 00:37:25.414
<v Speaker 0>fast and energy efficient optically controlled MRAM and

00:37:25.414 --> 00:37:28.295
<v Speaker 0>a seismic shift in the information storage and

00:37:28.295 --> 00:37:33.710
<v Speaker 0>processing across diverse sectors. So the use of

00:37:33.710 --> 00:37:40.910
<v Speaker 0>optically controlled in seismic shift so maybe this

00:37:40.910 --> 00:37:44.030
<v Speaker 0>might go beyond typical memory improvements. I don't

00:37:44.030 --> 00:37:46.925
<v Speaker 0>know. It's it's seismic shift. That's that must

00:37:46.925 --> 00:37:48.765
<v Speaker 0>be a big breakthrough. Maybe, maybe it's a

00:37:48.765 --> 00:37:50.785
<v Speaker 0>little bit of an exaggeration, but who knows?

00:37:51.405 --> 00:37:55.025
<v Speaker 0>It could potentially reshape architecture or system design

00:37:55.085 --> 00:38:02.030
<v Speaker 0>based on this, development. And then here's one

00:38:02.030 --> 00:38:04.830
<v Speaker 0>last key quote from the article. We've arrived

00:38:04.830 --> 00:38:08.290
<v Speaker 0>at a very elementary equation describing this interaction.

00:38:08.430 --> 00:38:12.130
<v Speaker 0>It lets us completely reconsider optical magnetic recording

00:38:12.270 --> 00:38:15.125
<v Speaker 0>and navigate our way to a dense energy

00:38:15.585 --> 00:38:19.185
<v Speaker 0>efficient, cost efficient optical magnetic storage device that

00:38:19.185 --> 00:38:27.980
<v Speaker 0>doesn't even exist yet. So that's cool. Who

00:38:27.980 --> 00:38:29.820
<v Speaker 0>knows? Tech may be on the verge of

00:38:29.820 --> 00:38:32.140
<v Speaker 0>a paradigm shift, not even like, not just

00:38:32.140 --> 00:38:35.020
<v Speaker 0>higher capacity or faster shifts, but fundamentally different

00:38:35.020 --> 00:38:38.700
<v Speaker 0>mechanisms. You know? Maybe we've started to reach

00:38:38.700 --> 00:38:41.635
<v Speaker 0>a break breakthrough in areas that we didn't

00:38:41.635 --> 00:38:44.935
<v Speaker 0>really express or expect using light and magnetism

00:38:45.155 --> 00:38:49.075
<v Speaker 0>is crazy. Lasers to control a chip. I

00:38:49.075 --> 00:38:50.675
<v Speaker 0>I I don't know. I didn't really think

00:38:50.675 --> 00:38:52.994
<v Speaker 0>that, you know, it's it's hard to think

00:38:52.994 --> 00:38:55.170
<v Speaker 0>of it as just light. Right? We think

00:38:55.170 --> 00:38:59.030
<v Speaker 0>of lasers like a like a beam almost.

00:38:59.650 --> 00:39:01.490
<v Speaker 0>I guess it's a beam of light, but

00:39:01.490 --> 00:39:03.170
<v Speaker 0>I don't know. I've never really thought that

00:39:03.170 --> 00:39:07.275
<v Speaker 0>hard about it, I feel like. But I

00:39:07.275 --> 00:39:09.194
<v Speaker 0>guess it's, this article kinda suggests that we

00:39:09.194 --> 00:39:12.395
<v Speaker 0>could redefine memory speed, efficiency, and perhaps perhaps

00:39:12.395 --> 00:39:15.194
<v Speaker 0>open up new architectures in memory computing or

00:39:15.194 --> 00:39:19.275
<v Speaker 0>quantum adjacent memory. I don't think we'll see

00:39:19.275 --> 00:39:21.950
<v Speaker 0>this in our everyday laptop yet just yet,

00:39:21.950 --> 00:39:23.630
<v Speaker 0>but it's like a cool sign that future

00:39:23.630 --> 00:39:27.630
<v Speaker 0>devices may become faster, more energy efficient, and

00:39:27.630 --> 00:39:31.310
<v Speaker 0>even more always ready. Less wait time, less

00:39:31.310 --> 00:39:34.665
<v Speaker 0>power wasted. But I think that's kind of

00:39:34.665 --> 00:39:36.905
<v Speaker 0>expected. You, you would expect that things to

00:39:36.905 --> 00:39:40.905
<v Speaker 0>be improving always or you'd hope, right? Or

00:39:40.905 --> 00:39:42.985
<v Speaker 0>what else are we doing when we go

00:39:42.985 --> 00:39:46.825
<v Speaker 0>to work every day? Can just slog away

00:39:46.825 --> 00:39:52.200
<v Speaker 0>at the machine. But I got another article

00:39:52.200 --> 00:39:55.320
<v Speaker 0>for you folks. AMD bundles four Steam games

00:39:55.320 --> 00:39:58.760
<v Speaker 0>with only Lenovo Legion Go two. So this

00:39:58.760 --> 00:40:01.160
<v Speaker 0>is a Costco special for those of you

00:40:01.160 --> 00:40:03.000
<v Speaker 0>that are looking for a new gaming device,

00:40:03.000 --> 00:40:05.474
<v Speaker 0>the Legion Go two is coming out with

00:40:05.474 --> 00:40:09.174
<v Speaker 0>Starfield, Lies of P, Space Marine and Awakening.

00:40:11.714 --> 00:40:22.240
<v Speaker 0>Interesting. Wow. Well, this device is going for

00:40:22.240 --> 00:40:27.440
<v Speaker 0>ten ninety nine. Ten ninety nine and I

00:40:27.440 --> 00:40:31.040
<v Speaker 0>mean one thousand big ones with ninety nine

00:40:31.040 --> 00:40:34.945
<v Speaker 0>more on top. But Lenovo has launched the

00:40:34.945 --> 00:40:38.305
<v Speaker 0>Legion Go two, a handheld gaming PC powered

00:40:38.305 --> 00:40:41.825
<v Speaker 0>by AMD's z two series chip, the Ryzen

00:40:41.825 --> 00:40:44.245
<v Speaker 0>z two, which were designed for high performance

00:40:44.305 --> 00:40:49.050
<v Speaker 0>portable systems. The promotion is exclusive to Costco

00:40:49.050 --> 00:40:50.970
<v Speaker 0>and bundles four Steam Games with the purchase

00:40:50.970 --> 00:40:52.809
<v Speaker 0>of Legion Go two as part of the

00:40:52.809 --> 00:40:56.170
<v Speaker 0>collaboration between AMD and Costco. The heck? I

00:40:56.170 --> 00:41:00.109
<v Speaker 0>didn't know Costco and AMD had a partnership.

00:41:00.250 --> 00:41:04.065
<v Speaker 0>That's interesting to find out. Maybe I'm just

00:41:04.065 --> 00:41:05.345
<v Speaker 0>out of the loop. I need to get

00:41:05.345 --> 00:41:07.345
<v Speaker 0>in the loop. I guess I'm not I

00:41:07.345 --> 00:41:08.785
<v Speaker 0>don't I don't know. I'm not really looking

00:41:08.785 --> 00:41:12.225
<v Speaker 0>at partnerships though. But keep this context in

00:41:12.225 --> 00:41:14.145
<v Speaker 0>mind for the future, I guess. The games

00:41:14.145 --> 00:41:16.065
<v Speaker 0>in the bundle per the listing including some

00:41:16.065 --> 00:41:18.359
<v Speaker 0>high profile titles such such as Starfield, Lyza

00:41:18.359 --> 00:41:21.500
<v Speaker 0>P, Unknown Nine, Awakening, and and Hammer Warhammer

00:41:21.960 --> 00:41:25.240
<v Speaker 0>forty thousand Space Marines two. Now these games

00:41:25.240 --> 00:41:28.599
<v Speaker 0>have been out for a while. So, honestly,

00:41:28.599 --> 00:41:31.000
<v Speaker 0>it's a little bit disappointing to see it

00:41:31.000 --> 00:41:34.375
<v Speaker 0>come out with that. But it comes out

00:41:34.535 --> 00:41:37.414
<v Speaker 0>this so the campaign's already started and it

00:41:37.414 --> 00:41:40.694
<v Speaker 0>runs while coupon codes last. It's offered at

00:41:40.694 --> 00:41:43.575
<v Speaker 0>participating Costco warehouses and at costco dot com

00:41:43.575 --> 00:41:47.240
<v Speaker 0>in the US and Canada. And you can

00:41:47.940 --> 00:41:51.460
<v Speaker 0>attempt to redeem by May second twenty twenty

00:41:51.460 --> 00:41:54.180
<v Speaker 0>six if you're looking for this device. Pretty

00:41:54.180 --> 00:41:57.800
<v Speaker 0>cool to see. It's it's a literal gaming

00:41:58.215 --> 00:42:01.095
<v Speaker 0>PC but a handheld device. So I guess

00:42:01.095 --> 00:42:04.135
<v Speaker 0>that explains the big the big the big

00:42:04.135 --> 00:42:09.655
<v Speaker 0>price point there. But, who knows? If you're

00:42:09.655 --> 00:42:11.735
<v Speaker 0>looking for a device that you can just

00:42:11.735 --> 00:42:15.390
<v Speaker 0>play games on which, you know, could be

00:42:15.390 --> 00:42:18.210
<v Speaker 0>kinda interesting. Who knows? Gotta check that out.

00:42:19.790 --> 00:42:21.869
<v Speaker 0>But if you yeah. So if you're in

00:42:21.869 --> 00:42:24.270
<v Speaker 0>the market with portable PC gaming setup, this

00:42:24.270 --> 00:42:27.470
<v Speaker 0>this bundle might be what's calling out your

00:42:27.470 --> 00:42:29.615
<v Speaker 0>name, you know, to to pro it's supposed

00:42:29.615 --> 00:42:30.734
<v Speaker 0>to be like it's supposed to be a

00:42:30.734 --> 00:42:34.655
<v Speaker 0>Costco bargain. Let's move on. We got a

00:42:34.655 --> 00:42:38.494
<v Speaker 0>couple more key ones and wow. Look at

00:42:38.494 --> 00:42:41.775
<v Speaker 0>them freaking bend. Look at them bend. This

00:42:41.775 --> 00:42:46.079
<v Speaker 0>one's from Forbes by Davey Winder. They have

00:42:46.079 --> 00:42:48.720
<v Speaker 0>they have bent the knee to the the

00:42:48.720 --> 00:42:53.140
<v Speaker 0>upset people. Microsoft confirms free Windows ten security

00:42:53.200 --> 00:43:02.085
<v Speaker 0>updates and how to get them. I I'd

00:43:02.085 --> 00:43:03.845
<v Speaker 0>love to use a lot of colorful language

00:43:03.845 --> 00:43:07.065
<v Speaker 0>for this, you know. For those of you

00:43:07.525 --> 00:43:09.605
<v Speaker 0>upgrading to win or that were forced to

00:43:09.605 --> 00:43:13.900
<v Speaker 0>upgrade to Windows eleven, I hope you love

00:43:13.900 --> 00:43:15.500
<v Speaker 0>it. I really do. And I hope your

00:43:15.500 --> 00:43:18.880
<v Speaker 0>device can run it. We've had two devices

00:43:19.020 --> 00:43:22.700
<v Speaker 0>on Windows eleven crash at work because of

00:43:22.700 --> 00:43:25.434
<v Speaker 0>the bloatware that comes with it. So if

00:43:25.434 --> 00:43:28.555
<v Speaker 0>you wanna remove some Microsoft bloatware, definitely look

00:43:28.555 --> 00:43:36.015
<v Speaker 0>into Chris Titus', wind debloater. I love that

00:43:36.234 --> 00:43:43.930
<v Speaker 0>tool. But, yeah, it's it's ridiculous. They they

00:43:43.930 --> 00:43:46.170
<v Speaker 0>kinda played us there. But they kind of

00:43:46.170 --> 00:43:48.089
<v Speaker 0>announced that they were not gonna do any

00:43:48.089 --> 00:43:50.809
<v Speaker 0>more security support on Windows ten, as of

00:43:50.809 --> 00:43:54.615
<v Speaker 0>October fourteenth. And now they have introduced a

00:43:54.615 --> 00:43:56.955
<v Speaker 0>free option for Windows ten users to receive

00:43:57.015 --> 00:44:00.055
<v Speaker 0>one additional year of extended security updates through

00:44:00.055 --> 00:44:02.775
<v Speaker 0>October thirteen twenty twenty six. Oh, so you

00:44:02.775 --> 00:44:06.620
<v Speaker 0>only got one one year. Okay. The free

00:44:06.620 --> 00:44:09.740
<v Speaker 0>ESU comes with conditions. So if the free

00:44:09.740 --> 00:44:15.280
<v Speaker 0>extended security updates, so you have to enable

00:44:15.500 --> 00:44:19.180
<v Speaker 0>certain Windows backup or cloud sync features. What

00:44:19.180 --> 00:44:23.635
<v Speaker 0>a bunch of whoo. They are they wow.

00:44:23.855 --> 00:44:29.215
<v Speaker 0>Cool. I'm just we'll see if this the

00:44:29.215 --> 00:44:31.555
<v Speaker 0>the my work laptop can run Windows eleven.

00:44:32.495 --> 00:44:35.135
<v Speaker 0>Because it it she screams at me already.

00:44:35.135 --> 00:44:37.210
<v Speaker 0>That's all I can say. And I have

00:44:37.210 --> 00:44:40.650
<v Speaker 0>been avoiding the Windows eleven update, which I

00:44:40.650 --> 00:44:42.730
<v Speaker 0>really need to get on. That might be

00:44:42.730 --> 00:44:47.050
<v Speaker 0>a concern. But hey, if you are looking

00:44:47.050 --> 00:44:50.775
<v Speaker 0>for continued Windows ten, support Oh, actually, I

00:44:50.775 --> 00:44:53.494
<v Speaker 0>don't even think my laptop can update to

00:44:53.494 --> 00:44:56.214
<v Speaker 0>Windows eleven. So I might have to ask

00:44:56.214 --> 00:44:59.174
<v Speaker 0>them about that. I don't think it's a

00:44:59.174 --> 00:45:03.990
<v Speaker 0>problem right now, but who knows? Microsoft obviously

00:45:03.990 --> 00:45:05.670
<v Speaker 0>really wants people to stop using Windows ten

00:45:05.670 --> 00:45:08.710
<v Speaker 0>though. It's called twenty twenty five the year

00:45:08.710 --> 00:45:11.350
<v Speaker 0>of the Windows eleven PC refresh. Yeah. More

00:45:11.350 --> 00:45:14.710
<v Speaker 0>like the, move to Linux refresh. I just

00:45:14.710 --> 00:45:18.575
<v Speaker 0>read an article today about, people hosting a

00:45:18.575 --> 00:45:21.214
<v Speaker 0>Linux install party where they help everyday people

00:45:21.214 --> 00:45:23.454
<v Speaker 0>just get Linux installed in their devices. Pretty

00:45:23.454 --> 00:45:27.694
<v Speaker 0>cool stuff. Oh, you know, I thought I

00:45:27.694 --> 00:45:29.135
<v Speaker 0>had a couple more articles for you, but

00:45:29.135 --> 00:45:30.575
<v Speaker 0>I think that's actually the end of the

00:45:30.575 --> 00:45:35.430
<v Speaker 0>line. Thanks for hanging out with me this

00:45:35.430 --> 00:45:40.710
<v Speaker 0>afternoon. Again, sorry for the late late, post

00:45:40.710 --> 00:45:42.870
<v Speaker 0>into the week. I will try to get

00:45:42.870 --> 00:45:47.645
<v Speaker 0>the newsletter out hopefully tomorrow. But things have

00:45:47.645 --> 00:45:49.484
<v Speaker 0>just been a little bit rough rate lately,

00:45:49.484 --> 00:45:53.805
<v Speaker 0>so hoping to keep, keep my head on

00:45:53.805 --> 00:45:56.845
<v Speaker 0>straight and keep delivering great drills for you

00:45:56.845 --> 00:46:00.045
<v Speaker 0>folks. Please, send me some feedback via geek

00:46:00.045 --> 00:46:03.000
<v Speaker 0>news at g mail dot com. And I

00:46:03.000 --> 00:46:07.800
<v Speaker 0>hope you guys have a phenomenal week. Until

00:46:07.800 --> 00:46:09.240
<v Speaker 0>I talk to you guys next time, have