TRANSCRIPT 🔗
WEBVTT
00:00:00.239 --> 00:00:07.200
Probably my boldest prediction is that people will stop treating these models as unintelligent.
00:00:07.200 --> 00:00:16.800
All these different features that we are adding on to LLMs, first it was reg retrieval augmentation, then it was memories.
00:00:16.800 --> 00:00:18.960
You know, that's what they're kind of currently working on.
00:00:18.960 --> 00:00:25.920
On top of that is like context compression, which you could argue is a form of synthesizing information.
00:00:25.920 --> 00:00:31.120
You're just describing the process of like designing intelligence.
00:00:31.120 --> 00:00:35.119
Just because a plane doesn't fly like a bird doesn't mean it can't fly.
00:00:35.280 --> 00:00:35.600
Yeah.
00:00:35.759 --> 00:00:37.840
We are building intelligence systems.
00:00:37.840 --> 00:00:43.200
We have put intelligence in a bottle and we are adding intelligence features to these models.
00:00:43.200 --> 00:00:49.039
We should have had a global holiday for passing the Turing tests, and and it's it's just, yeah.
00:00:49.039 --> 00:00:57.119
Anyways, as my wife tells me, I have like radical views on all these topics, and the most people, you know, she says she tells me that I'm my views are outside the Overton window.
00:00:57.119 --> 00:01:14.400
And welcome to ADSP the podcast, episode 270, recorded on January 13th, 2026.
00:01:14.400 --> 00:01:15.280
My name is Connor.
00:01:15.280 --> 00:01:22.239
Today with my co-host Bryce, we make our 2026 predictions, talk about the future, AI, books, and more.
00:01:22.239 --> 00:01:28.959
2025, it's in the rear, view, mirror.
00:01:28.959 --> 00:01:30.560
2026 is here.
00:01:30.560 --> 00:01:33.200
It is January 13th as we record this.
00:01:33.200 --> 00:01:34.400
What do we want to say?
00:01:34.400 --> 00:01:49.599
I mean, one of my favorite episodes of all time, I believe, is episode 111, I think it is, and it was the Star Wars intro episode where I used the Star Wars theme.
00:01:49.599 --> 00:01:51.760
I believe, was it episode 111?
00:01:51.760 --> 00:01:52.239
Yes.
00:01:52.239 --> 00:01:56.719
C 23 Ranges, 2022 Retro, and Star Wars.
00:01:56.719 --> 00:02:11.120
So it was, I guess, it was three years ago when we were doing the 2022 retro, and you started talking about how 2023 was gonna be the year that the Empire strikes back.
00:02:11.120 --> 00:02:13.599
So do you have any more great analogies?
00:02:13.599 --> 00:02:15.120
They can be Star Wars themed again.
00:02:15.120 --> 00:02:20.639
I mean, Andor came out, obviously, everyone agrees it's one of the best shows of all time.
00:02:20.639 --> 00:02:22.639
What's in store for 2026?
00:02:22.639 --> 00:02:25.680
Is it the AI bubble popping?
00:02:25.680 --> 00:02:27.759
Which obviously it's not gonna pop, folks.
00:02:27.759 --> 00:02:28.800
It was just a wobble.
00:02:28.960 --> 00:02:38.960
It was just You know, we've been I've been listening to the acquired podcast a lot, and they in in more recent episodes, they've started at the start by saying this is not investment advice.
00:02:38.960 --> 00:02:42.240
They put a little disclaimer at the start of their podcast.
00:02:42.240 --> 00:02:43.680
Maybe we need that.
00:02:43.680 --> 00:02:45.120
Uh I'm gonna speculate.
00:02:45.120 --> 00:02:46.400
I'm gonna speculate.
00:02:46.400 --> 00:02:53.280
I'm gonna make some very specific speculations about some specific people and what they may do.
00:02:53.680 --> 00:02:55.039
Are we gonna name these people?
00:02:55.439 --> 00:02:56.960
Yeah, of course I'm gonna name these people.
00:02:56.960 --> 00:03:10.960
So, first of all, first of all, I will speculate that sometime either this year or next year, that you, Connor, are gonna get nerd-sniped into like ML kernel design.
00:03:10.960 --> 00:03:24.000
And I think at some point, my what I've hinted at on past episodes, that at some point we're gonna be like, all right, we should go train, train our own language model and figure out how that how to do that.
00:03:24.000 --> 00:03:27.280
At some point the next two years, I think that'll happen.
00:03:27.280 --> 00:03:53.759
Because I think at some point you're gonna you're gonna get nerd-styped by this, and uh, and and and I say that having somewhat been nerd-styped by this now myself, and there's all sorts of cool algorithms underneath these these ML models, and it's like a place where you can really spend a lot of time and effort finding the the perfect algorithm, and there is a a great value and return on investment for that.
00:03:53.759 --> 00:03:55.360
So I I think that'll happen to you.
00:03:55.680 --> 00:03:58.560
Well, I have the power to make you wrong, but anyways.
00:03:59.599 --> 00:04:02.719
In this case, I don't I don't think so.
00:04:02.719 --> 00:04:03.520
I don't think so.
00:04:03.840 --> 00:04:04.400
Time will tell.
00:04:04.639 --> 00:04:14.960
My second my second prediction is that I think we will have Sean Baxter back on this podcast sometime in the next year or two.
00:04:15.360 --> 00:04:21.360
All right, so you started off with one where you gave me the power to, you know, have have you be wrong.
00:04:21.360 --> 00:04:26.720
And technically you've done the same thing again, but also you have more ability to make that one come true.
00:04:26.720 --> 00:04:29.759
But I could just be like, that's it, we're not having Sean on.
00:04:29.759 --> 00:04:31.120
Playing with fire here.
00:04:32.399 --> 00:04:33.439
There's reason.
00:04:33.439 --> 00:04:43.040
I mean, you're you're not even exploring the interesting part of that, which is like, why would Bryce want to have Sean back on the podcast?
00:04:43.040 --> 00:04:43.839
I mean, obviously, Sean.
00:04:43.839 --> 00:04:44.800
What do you mean why?
00:04:44.800 --> 00:04:45.600
It's obvious why.
00:04:46.240 --> 00:04:49.600
Some of his conversations we had with him were like our best episodes ever.
00:04:49.600 --> 00:04:54.399
That one that was like circle versus C versus
Load full transcript
Rust versus whatever.
00:04:54.720 --> 00:05:02.319
Yes, but but is that but you should ask yourself, why is it that Bryce thinks that we're gonna have Sean back on this podcast?
00:05:02.639 --> 00:05:04.240
I mean, I we work for the same company.
00:05:04.240 --> 00:05:05.360
I know why.
00:05:05.600 --> 00:05:11.279
I don't think you do, because the thing, the thing is is very, very recent.
00:05:11.279 --> 00:05:12.560
It's very, very recent.
00:05:12.560 --> 00:05:13.920
Okay, maybe I don't know.
00:05:13.920 --> 00:05:14.720
Maybe I don't know.
00:05:14.720 --> 00:05:15.360
Yes.
00:05:15.360 --> 00:05:18.560
I think Sean is working on some very exciting things.
00:05:18.560 --> 00:05:27.199
And as soon as they are things that he can talk about, I'm gonna say Sean should come back onto the podcast.
00:05:27.199 --> 00:05:29.759
So those are my two predictions.
00:05:29.759 --> 00:05:33.360
Bigger, like macro world predictions.
00:05:33.360 --> 00:05:47.439
I think we'll see a lot more AI in the workplace the next year, like companies trying to produce the sort of results with AI that that we've seen for for coding.
00:05:47.439 --> 00:05:54.319
They'll try to take that to other, you know, white-collar jobs, and we'll see more like tools and frameworks built out around around that.
00:05:54.319 --> 00:05:56.079
We'll see a lot more adoption of that.
00:05:56.079 --> 00:06:08.959
And I think that there will be a lot more talk about edge AI and robots and automation and and AI in our various devices.
00:06:08.959 --> 00:06:10.560
I think we'll see a lot of that.
00:06:10.560 --> 00:06:21.040
And I think it's a it's a it's a great time to be a a staff software engineer, and it is an awful time to be anybody more junior than that.
00:06:21.040 --> 00:06:42.160
I think there's there's an increase somebody somebody just asked me today about their their programming and like Java and some other languages, and they were asking like, what, what what recommendations would you have for for me if I want to get into lower level languages, C ⁇ , etc., if I want to get more systems software.
00:06:42.160 --> 00:06:48.720
And what I told him is, and he asked, oh, should I learn like modern best practices and like the APIs and like good design philosophy?
00:06:48.720 --> 00:06:50.800
And I was like, no, don't do any of that.
00:06:50.800 --> 00:07:02.720
Learn learn performance analysis and optimization, how to benchmark things, and how to reason about hardware and performance, debugging, etc.
00:07:02.720 --> 00:07:17.360
I think those are skills that are still very valuable in an era where we can where we can have AI automate a lot of the laborious sort of authoring of the code.
00:07:17.360 --> 00:07:21.600
Obviously, being able to design the system is still an important skill.
00:07:21.600 --> 00:07:25.600
But I think that there's a lot of people who have those design skills.
00:07:25.600 --> 00:07:36.639
I think a far more in demand skill is being able to reason about performance and optimize codes and then also debug codes.
00:07:36.639 --> 00:07:41.439
So I think those will be increasingly important skills.
00:07:42.160 --> 00:07:44.240
Everything lower than staff engineer, though?
00:07:44.240 --> 00:07:44.560
Really?
00:07:44.560 --> 00:07:45.600
That's the threshold?
00:07:46.720 --> 00:07:48.079
Yeah, I think so.
00:07:48.079 --> 00:07:57.199
I think it I think that uh companies that are hiring are only hiring, you know, the very top, very senior people.
00:07:57.199 --> 00:08:31.680
Or people who are you know, I I I imagine there'll be like more product managery sort of roles in the future because it's a lot easier for people uh it's a lot easier for like a person to be like a one a one-stop shop for a whole like product or feature, because they can be the person who like meets with the customers, figures out what the product should be, goes and builds the product using AI, and and then you know, brings it to market, does the outreach, does the you know, the marketing, etc.
00:08:31.680 --> 00:08:44.240
I think we'll see a lot more sort of integration of multiple different parts of software development and software publication into a couple uh into fewer people.
00:08:44.240 --> 00:08:54.879
I think like people's roles will get more general because there will be less of a demand for people whose specialty is just outputting code manually themselves.
00:08:54.879 --> 00:08:59.600
So people who have diverse skill sets are gonna benefit.
00:08:59.600 --> 00:09:16.960
Or people who have very, very deep skill sets, but in a very specific way, like people who are, you know, leaders in their fields of like mathematics or, you know, performance optimization or something like more domain specific.
00:09:16.960 --> 00:09:22.639
But uh but just you know, being a junior software engineer right now, I think it's bad time for that.
00:09:23.039 --> 00:09:27.279
Do you think that's gonna change at any point, or is this the way it is?
00:09:27.279 --> 00:09:29.039
It's a new paradigm shift.
00:09:29.039 --> 00:09:32.320
There's a paradigm shift, and this is just the world we live in now.
00:09:32.799 --> 00:09:51.519
I think that yes, I think it will change because if you if you believe that we're in the midst of an industrial revolution, then in the future there will be a lot more things that are like powered under the hood by software.
00:09:51.519 --> 00:09:58.720
And so eventually the AI revolution will mean that there is a lot more demand for software in general.
00:09:58.720 --> 00:10:10.159
And so, like, every every time there's been increases in efficiency and like worker efficiency, we've seen like demand increase too, because the cost of the thing goes down.
00:10:10.159 --> 00:10:12.960
So I I think we'll see that happen here too.
00:10:12.960 --> 00:10:24.159
Yeah, the the amount of output that one engineer can do will go up, but that does not mean that the that does not mean that we'll have
less engineers.
00:10:24.159 --> 00:10:31.360
It just means that eventually the number of in the amount of work out there will grow.
00:10:31.360 --> 00:10:33.919
But there are like gonna be growing pains.
00:10:33.919 --> 00:10:51.519
And I think we also have the problem that a lot of people have gone and pursued degrees and in careers in computer science because it's been a very lucrative field for a long time, and there may be a glut, there may be an oversupply right now.
00:10:51.519 --> 00:10:52.960
It it's kind of hard to say.
00:10:52.960 --> 00:11:08.639
I mean, hiring's hiring's very tight at a lot of tech tech companies, and for a period it seemed like that was because of the, you know, there was, was it 2021 or 2022, where there was just a really bad year for tech.
00:11:08.639 --> 00:11:10.480
Market contracted a bit.
00:11:10.480 --> 00:11:17.919
There was a lot of like uncertainty because of world events, and like COVID was kind of weird for the hiring market in general.
00:11:17.919 --> 00:11:28.000
But after 2023, 2024, 2025, it's hard to argue that like big tech is in a bad place, right?
00:11:28.000 --> 00:11:35.120
Like big tech companies, tech companies in general, not just big tech, but tech companies in general, seem to be doing, seem to be having a pretty good time.
00:11:35.120 --> 00:11:39.919
So why is there less demand for for engineers?
00:11:39.919 --> 00:11:55.039
Is it still really just the case that despite the good times that tech companies feel like there's a lot of uncertainty and so they don't want to, you know, hire a lot of people and and expand their their you know, how much they're paying out every two weeks in salary?
00:11:55.039 --> 00:11:55.759
Maybe.
00:11:55.759 --> 00:12:02.399
Is it that they're seeing a lot of you know returns from using AI tools internally?
00:12:02.399 --> 00:12:03.279
Maybe.
00:12:03.279 --> 00:12:17.519
It could also just be that a lot of the thing that's driving the good times in tech right now, a lot of the things that are driving AI revolutions, the AI revolution, is powered by a s relatively small number of people.
00:12:17.519 --> 00:12:18.879
And that that may be the case.
00:12:18.879 --> 00:12:34.399
I mean, you see like these crazy, these crazy deals where supposedly Meta is paying ludicrous sums of money to hire people, and you know, why are tech companies paying so much for people who are experts in ML?
00:12:34.399 --> 00:12:53.759
And it it seems to be because they're getting very good results out of these relatively small teams who have this very rare knowledge of how to build these AI models, and they don't need, you know, 10 or 20,000 engineers to go, you know, churn out a whole pile of code.
00:12:53.759 --> 00:12:59.679
They need a small team of people who can go, you know, train and design a model.
00:12:59.679 --> 00:13:07.039
And that that maybe just doesn't require the same type of software engineer that is on the market right now.
00:13:07.039 --> 00:13:09.200
Anyway, so those were a lot of words.
00:13:09.600 --> 00:13:12.080
Well, let me describe this for the listener.
00:13:12.080 --> 00:13:15.679
I was interested while you were talking about that.
00:13:15.679 --> 00:13:23.279
I mean, there's the the website trueup.io slash layoffs, which tracks layoffs.
00:13:23.279 --> 00:13:27.759
And admittedly, December, and I know we're only halfway through January, but it's quite low.
00:13:27.759 --> 00:13:34.159
But I had never noticed that there's all this other information slash stats.
00:13:34.159 --> 00:13:39.919
And the one that was relevant to what I guess we're talking about right now is kind of hiring and outlook.
00:13:39.919 --> 00:13:57.840
And if you can look at big tech employees, it shows two graphs actually, and goes back to 2014, and you see this little black line that by 2016 has disappeared off the top of the chart, and that's Amazon, because they have 1.6 roughly million employees at this point.
00:13:57.840 --> 00:14:10.960
And you can notice that, yeah, since 2022, December 31st, so I guess the beginning of 23, it's kind of been flat, if not down, on average.
00:14:10.960 --> 00:14:20.960
Like definitely, Amazon peaked back at the end of 2021, and then their employee count has dropped and not recovered to that point.
00:14:20.960 --> 00:14:34.399
And then definitely, I'm sure you've heard the the reporting that's been done of Amazon talking about how they're, you know, gonna be employing, quote unquote employing or using robots more and have less need to.
00:14:35.279 --> 00:14:44.559
Yeah, but the the interesting thing here, you know, some people have the theory that, oh, this is happening because AI is replacing the software engineering jobs.
00:14:44.559 --> 00:14:49.840
And I think that it's very unlikely that that's true because go back to that graph for a second.
00:14:49.840 --> 00:14:52.080
When actually go back to what you just had.
00:14:52.080 --> 00:14:52.720
When what was it?
00:14:52.720 --> 00:14:54.000
It just had a list of important dates.
00:14:54.320 --> 00:14:54.559
Yeah, yeah.
00:14:54.559 --> 00:14:55.919
Well, there's a there's a ton of stuff.
00:14:55.919 --> 00:15:00.159
I mean, just to skip around to all this different stuff, I'll I'll link this website in the show notes.
00:15:00.559 --> 00:15:01.840
But go back and what was it?
00:15:01.840 --> 00:15:04.480
It had the date for when ChatGPT launched.
00:15:05.120 --> 00:15:07.120
3.1 years ago on November 30th.
00:15:07.360 --> 00:15:08.159
Yeah, 2022.
00:15:08.159 --> 00:15:09.679
Go back to that chart.
00:15:09.679 --> 00:15:14.000
The the hiring sort of like peaked in 2022.
00:15:14.000 --> 00:15:19.279
Because I think was it 2021 was the bad the bad year for tech, or maybe it was 2022.
00:15:19.279 --> 00:15:20.639
It's one of those two years.
00:15:20.639 --> 00:15:33.360
I I think it's hard to believe that in 2022 that across the board tech company leadership said, oh hey, this AI thing is
here.
00:15:33.360 --> 00:15:43.279
That means that we should stop hiring because you know, our software engineers are gonna be so much more efficient because of this.
00:15:43.279 --> 00:15:48.639
Like 2022, I don't think everybody had drank the Kool-Aid yet, right?
00:15:48.639 --> 00:15:56.639
Like maybe some people did, but like even you and I, you know, we were not on the AI hype train in 2022.
00:15:56.639 --> 00:16:00.240
So I think that I think that there's some other explanation going on.
00:16:00.240 --> 00:16:12.559
I don't think that Amazon or Microsoft are hiring more people or doing layoffs because they decided in 2022 that AI could make their software engineering workforce more efficient.
00:16:12.559 --> 00:16:13.600
I don't buy that.
00:16:13.600 --> 00:16:16.080
I think it's some combination of other factors.
00:16:16.080 --> 00:16:28.000
And I think like that maybe part of it is a lot of these companies have to deploy their capital now to make these huge investments in hardware to train these AI models.
00:16:28.000 --> 00:16:32.080
And so maybe that's where they're investing their money instead of in personnel.
00:16:32.080 --> 00:16:36.639
Maybe it's because you know they don't need as big teams to build these models.
00:16:36.639 --> 00:16:38.159
I don't know.
00:16:38.559 --> 00:16:53.600
I mean, yes, I've I've I switched over to artificial analysis, which funnily enough, only goes back to March of 2023, which is four months after November of 2022, which is when ChatGPT launched.
00:16:53.600 --> 00:17:03.919
And I recall really being like what is the word AI pilled when Claude 3.5 was out.
00:17:03.919 --> 00:17:07.519
So that was like middle to late 2024.
00:17:07.519 --> 00:17:12.480
So I've been using Cursor every sin ever since early 2025.
00:17:12.480 --> 00:17:32.640
I think I bought my first subscription in January and then realized within a month that NVIDIA was paying for our subscription, so I only paid for a month, but I had been using like the online, you know, Chat GPT and friends for helping out with coding.
00:17:32.640 --> 00:17:41.920
And so yeah, it wasn't until 2024, so it took a full year and a half until I started like using these tools.
00:17:41.920 --> 00:17:48.559
And I I didn't have my mind blown until I don't know, the CLOD 3.7, which was in April, March.
00:17:48.559 --> 00:17:51.200
Simil similar similar for me.
00:17:51.359 --> 00:18:07.039
So I think it's hard to believe that that this that AI that the increase in worker efficiency in the software field due to AI is the sole reason for tech hiring falling off.
00:18:07.039 --> 00:18:11.599
And I think it's more likely that it's like a combination of multiple different factors.
00:18:11.599 --> 00:18:27.119
Well, and do you have any theories for the kind of what I illustrated that that why are all the like everybody who's doing well in tech right now pretty much is doing well because of AI in some way, shape, or form.
00:18:27.119 --> 00:18:34.319
All the big all the big tech players who are doing well are doing well because they have some part in the AI economy.
00:18:34.319 --> 00:18:46.720
And I think that you don't need you need a different sort of workforce to be an AI tech company than you needed before.
00:18:46.720 --> 00:18:48.960
I think that's what it is.
00:18:48.960 --> 00:18:54.640
That look at look at like Microsoft or Google, like what's important for for them right now?
00:18:54.640 --> 00:19:04.319
It's building out like their AI, their their their hyperscaler cloud and and training you know the world's best models.
00:19:04.319 --> 00:19:11.440
Do you need is hiring 10,000 junior engineers gonna help make Gemini better?
00:19:11.440 --> 00:19:27.680
No, probably the thing that's gonna help make Gemini better is going and hiring, you know, the five, you know, key experts who know the thing that you need for this particular part of this particular niche area of AI where you've got a problem right now.
00:19:27.680 --> 00:19:35.039
That I don't I don't think it's these companies need like rare expertise, right?
00:19:35.039 --> 00:19:49.839
Right, where rare expertise is driving the tech economy right now, not you know these large workforces of not not like just solely person power, you know, not just code monkeys spitting out code.
00:19:49.839 --> 00:20:15.440
And I I think that I think that also because these companies are deploying so much money to build out data centers, to build out compute hardware, they uh they of course naturally are all you can't grow your workforce by 10,000 employees and also you know go build you know billions and billions of dollars of data centers.
00:20:15.440 --> 00:20:18.400
Like do you you do have a limited amount of money.
00:20:18.400 --> 00:20:24.240
And so I think that's they're they're choosing to invest in in in the compute resources.
00:20:24.240 --> 00:20:26.319
And I think there's other factors.
00:20:26.319 --> 00:20:30.720
I do think that there's a lot of uncertainty in the economy.
00:20:30.720 --> 00:20:41.119
There's uncertainty about whether there's an AI bubble, there's uncertainty because of you know the politics of the world right now, and and and so I think that's part of it too.
00:20:41.119 --> 00:20:46.400
But that that that last argument I I find less compelling now than I did in 2023.
00:20:47.200 --> 00:20:47.759
Interesting.
00:20:48.000 --> 00:20:48.559
What do you think?
00:20:48.559 --> 00:20:50.240
What's what's your theories here?
00:20:51.119 --> 00:21:05.680
I mean, on the topic of tech hiring and corporate capital allocation towards, you know, infrastructure build or compute spend versus employee spend.
00:21:05.680 --> 00:21:10.000
I don't think I have a ton of I don't really spend a lot of time thinking about that.
00:21:10.000 --> 00:21:30.720
I will say to echo what you know you just talked about, I I have had the evolving view, or not evolving view, but I I had a kind of moments where I
realized that experts really are required to use these tools correctly.
00:21:30.720 --> 00:21:42.319
And as an expert in a domain, you don't really realize it because you're just asking these tools to know to do what you want it to do, because you know that's the thing you want.
00:21:42.319 --> 00:21:51.039
But when you go to a vertical that you are not an expert in and you do care about code quality, you know, vibe coding, if you don't care, it doesn't matter.
00:21:51.039 --> 00:21:59.759
But if you are trying to get like the idiomatic solution in some language, whether it's Python or Rust, and you're not an expert and you don't know the surface.
00:21:59.759 --> 00:22:18.559
Area of the libraries and the algorithms in the libraries or the APIs and the methods in the APIs, and then you post that as a PR somewhere, you are going to realize very quickly when experts take a look at it that it's not necessarily doing like the best practice idiomatic thing.
00:22:18.559 --> 00:22:25.119
And I had that experience when working with Rust recently.
00:22:25.119 --> 00:22:26.559
And so there's a difference.
00:22:26.559 --> 00:22:33.279
When you don't care about the code quality, vibe code away.
00:22:33.279 --> 00:22:42.880
But when you do care, expertise is like not only necessary, I would say essential, depending on the complexity of the task that you're trying to do.
00:22:42.880 --> 00:22:59.359
And I think as like someone that operates typically in a domain of expertise, or like my expertise, you don't really notice how much you're because anytime it does something that you know is not what you wanted, you just tell it, no, no, no, no, please use this thing from this library.
00:22:59.359 --> 00:23:18.319
And anyway, so that kind of echoes what you're saying, is that yeah, I don't know if it's a staff level engineer that is all that people need, but definitely I think expertise, even though that these models are really, really good still, that a lot of the times it goes down the wrong path and you need to be able to correct that.
00:23:18.319 --> 00:23:25.680
And if you don't know that you've gone down a wrong path, which is probably going to be the case for a lot of junior folks, that's gonna be a problem.
00:23:26.079 --> 00:23:35.039
But I I don't I don't even think that that's necessarily the problem because I think we're still very early in the adoption of AI even within the software engineering.
00:23:35.039 --> 00:23:49.039
I I don't know what percentage of I don't know whether there's public data on what percentage of employees at uh big or small tech companies are using AI, but I I bet you, I bet you it's a lot less than you think.
00:23:49.039 --> 00:24:02.079
Because, as I always like to say, inertia is king in the software industry, and switching to new tools and to new ways of working is scary and and it takes a long time for people to uh to actually go and do that.
00:24:02.079 --> 00:24:14.400
So if if you told me that that only 25% of employees at big tech companies were using like 25% of software engineers at big tech companies were using AI, I wouldn't be surprised.
00:24:14.880 --> 00:24:16.880
I think it's it's probably company dependent.
00:24:16.880 --> 00:24:21.920
I think there's probably some companies where it's like 80, 90%, if not all.
00:24:21.920 --> 00:24:24.480
And then there's other companies where it's really, really low.
00:24:24.640 --> 00:24:39.680
And I don't I don't think that there's any I don't think that any of the big companies are anywhere near that high because I don't think that like a company like Google scale or even like at NVIDIA scale, I don't think that you can get to those numbers that quickly.
00:24:39.680 --> 00:24:54.559
I think, yeah, maybe a smaller company, yeah, but these really large tech companies, they don't have like there's a lot of like localized practice and culture, and it takes a long time for stuff to trickle down throughout the entire company.
00:24:54.720 --> 00:24:55.519
Aaron Powell Yeah, that's true.
00:24:55.519 --> 00:25:07.279
I mean it's way way easier for a startup with, you know, a handful of folks to all be leveraging these tools, aka 100% of them, versus some company with tens of thousands of employees.
00:25:07.680 --> 00:25:16.160
And just just think what just think what it's gonna be like once once, you know, give it give it five years, and then we'll start seeing saturation in this industry, I think.
00:25:16.559 --> 00:25:19.279
No, it's not I don't think it's gonna take five years.
00:25:19.599 --> 00:25:23.759
I think to to get to 80 to 90 percent.
00:25:23.759 --> 00:25:26.720
Like at some point, it's let me put it this way.
00:25:26.720 --> 00:25:31.920
At some point there were there was like a time before version control in the software industry, right?
00:25:31.920 --> 00:25:35.519
And now it's it's unthinkable to not use version control.
00:25:35.519 --> 00:25:40.240
And like almost to some degree it's it's almost unthinkable to not use Git, specifically.
00:25:40.240 --> 00:25:52.400
And like I think it'll take five years for AI assisted coding to reach that level, where it's it's unthinkable that people aren't using AI tools to write code.
00:25:53.519 --> 00:25:54.799
How many years?
00:25:55.279 --> 00:25:55.920
Five years.
00:25:56.240 --> 00:25:57.359
I disagree.
00:25:57.359 --> 00:25:59.519
I think it's gonna be way sooner.
00:25:59.519 --> 00:26:06.000
And I don't we can't do we know how many engineers how many employees does NVIDIA have?
00:26:06.000 --> 00:26:07.039
Like 30,000?
00:26:07.039 --> 00:26:09.359
36,000.
00:26:09.359 --> 00:26:13.440
36,000 as of 2024 end of year.
00:26:13.440 --> 00:26:15.440
So that might be out of date.
00:26:15.440 --> 00:26:25.519
And I mean, we have to redact this, but in the cursor dashboard, the people that are using cursor.
00:26:25.759 --> 00:26:29.119
And of our Yeah, but dude, we're the we're the we're the AI company.
00:26:29.119 -->
00:26:30.720
Yeah, I mean we're the biggest company in the world.
00:26:30.799 --> 00:26:31.920
You just said the big companies.
00:26:31.920 --> 00:26:34.559
And also, how many how many employees does Adobe have?
00:26:34.559 --> 00:26:39.119
Because Sean said there was like 8,000 people at Adobe.
00:26:39.119 --> 00:26:43.839
How many employees at Adobe?
00:26:43.839 --> 00:26:44.960
Over 30,000?
00:26:44.960 --> 00:26:46.400
Okay, so that's a lower ratio.
00:26:46.400 --> 00:26:52.960
But like of the 36,000 roughly people at NVIDIA, how many do you think are in engineering that are writing code?
00:26:52.960 --> 00:26:54.559
I don't know.
00:26:54.799 --> 00:26:55.200
I don't know.
00:26:55.200 --> 00:26:56.240
What that's a good question.
00:26:56.240 --> 00:27:04.799
I don't I don't know what like the percentage is of engineering versus non-engineering, but it's also complicated for NVIDIA because we have uh both software and hardware engineers.
00:27:05.440 --> 00:27:06.079
Yeah.
00:27:06.079 --> 00:27:25.519
Anyways, I think it's when I was giving a talk recently, uh, you know, I asked the audience what percentage of folks, you know, consider AI as I don't want to go back to I think it's about 18,000 are engineers at NVIDIA.
00:27:25.519 --> 00:27:29.839
Or at least have logged into Cursor.
00:27:30.160 --> 00:27:43.920
I I don't know that I think uh based on that, I think that that just means that I I I would I strongly suspect that that would mean that we've auto-enrolled some large part in cursor, like some large engineering DL.
00:27:44.480 --> 00:27:46.000
I don't think it's auto-enrollment.
00:27:46.000 --> 00:27:52.079
I think you literally have to punch your email in and download it in order for you to show up in these metrics.
00:27:52.640 --> 00:27:52.880
Okay.
00:27:52.880 --> 00:27:54.720
That that that is that is pretty impressive.
00:27:54.720 --> 00:28:01.200
I would be more interested in seeing like numbers about who's like actively using it, not just who's logged in one time.
00:28:01.200 --> 00:28:08.079
But but that's just that because there's probably research people and product management and other things that fills out some amount of roles.
00:28:08.480 --> 00:28:17.119
Anyways, my my theory is that this stuff is is already like we can't go back because it's so useful.
00:28:17.119 --> 00:28:26.559
And I also think that probably my boldest prediction is that people will stop treating these models as unintelligent.
00:28:26.559 --> 00:28:36.640
A lot of people say that this is not, you know, it's not I don't want to use the word sentient, but it's not the equivalent of like human intelligence.
00:28:36.640 --> 00:28:48.559
And I think that all these different features that we are adding on to LLMs, first it was reg retrieval augmentation, then it was memories.
00:28:48.559 --> 00:28:50.799
You know, that's what they're kind of currently working on.
00:28:50.799 --> 00:28:57.759
On top of that is like context compression, which you could argue is a form of synthesizing information.
00:28:57.759 --> 00:28:59.200
Like you're just look at you.
00:28:59.359 --> 00:29:05.039
You're just you you think you're you think you're not gonna get nerd sniped into working on ML things.
00:29:05.440 --> 00:29:05.839
We'll see.
00:29:05.839 --> 00:29:13.599
My point being here, though, is that in my opinion, you're just describing the process of like designing intelligence.
00:29:13.599 --> 00:29:17.279
Like what is in what is human intelligence, you know?
00:29:17.279 --> 00:29:19.839
Our ability to retrieve information.
00:29:19.839 --> 00:29:21.680
We do that, search engines.
00:29:21.680 --> 00:29:36.559
Our ability to like synthesize information from different sources and come up with, you know, a synthesized fact or whatever, memory, you know, a lot of intelligence, Jeopardy, all the game shows.
00:29:36.559 --> 00:29:40.559
It's just storing information in a way where you can retrieve like we're literally going.
00:29:40.559 --> 00:29:51.839
If you had to design if you had to describe the different aspects of the intelligence of humans, it is literally the different things that people are adding on to like LLMs.
00:29:51.839 --> 00:29:57.440
It started off just as this like token generator, and you know, feed tokens in, tokens out, whatever.
00:29:57.440 --> 00:30:05.759
But now it's like all of that plus this stuff, you know, context compression and and information retrieval and memory.
00:30:05.759 --> 00:30:20.960
And at what point do we like admit that we're just like we're designing intelligent systems that like, oh okay, it's not it doesn't have consciousness and therefore it's not sentient, but you know, just because a plane doesn't fly like a bird doesn't mean it can't fly.
00:30:20.960 --> 00:30:21.839
You know what I mean?
00:30:21.839 --> 00:30:22.400
Yeah.
00:30:22.400 --> 00:30:25.440
It is we are building intelligent systems.
00:30:25.440 --> 00:30:34.160
We have put intelligence in a bottle and we are adding intelligence features to these models, and it is mind-blowing what they do sometimes, you know.
00:30:34.160 --> 00:30:44.480
And I I think there's just a lot of, I don't know if it's just the hubris of humans and like arrogance that, like, oh, you know, it's it's not it's not like us, you know, it doesn't think like us.
00:30:44.480 --> 00:30:46.079
Well, okay, sure.
00:30:46.079 --> 00:30:51.440
Planes don't fly like birds, doesn't mean they can't fly, some would argue, they fly even better than birds.
00:30:51.440 --> 00:30:58.240
And I think that like we're at a we're we're approaching a point where these systems are going to think better than humans.
00:30:58.240 --> 00:31:04.720
And how is that not like it's it's a it's better than human-level intelligence at a certain point, you know?
00:31:04.720 --> 00:31:05.519
We're not there yet.
00:31:05.519 --> 00:31:15.440
I'm just saying we're approaching it, but I listen to all these podcasts
of people being like, ah, you know, we we passed the Turing test, but it's you know, we kind of disprove that, and so it's what are you talking about?
00:31:15.440 --> 00:31:17.200
We blew past it, it's amazing.
00:31:17.200 --> 00:31:38.960
We should have had a global holiday for passing the Turing test, and and it's it's just yeah, anyways, but as my wife tells me, I have like radical views on all these topics, and the most people, you know, she says she tells me that I'm my views are outside the Overton window, and that people aren't ready to accept our machine god overlords that are around the corner as much as I am.
00:31:39.279 --> 00:31:43.119
We gotta pause for a second because I have a book recommendation, but I have to go get the books.
00:31:43.359 --> 00:31:43.920
Alright.
00:31:44.240 --> 00:31:46.640
But I mean, I guess we can actually talk as I walk.
00:31:46.640 --> 00:31:48.480
It's just that, you know, I have to walk into the book.
00:31:48.640 --> 00:31:53.839
I hope this book I hope this book is the book that I just finished reading two and a half books ago.
00:31:54.160 --> 00:32:01.359
I guarantee you, I guarantee you you have not read this book because it's in a completely separate category.
00:32:01.759 --> 00:32:05.279
I will I will give my book recommendation after Bryce comes back with his book.
00:32:05.599 --> 00:32:06.880
Are you still here?
00:32:07.279 --> 00:32:07.680
Yes.
00:32:07.680 --> 00:32:11.039
I went to grab a protein bar, but I am back at my desk.
00:32:11.599 --> 00:32:17.759
You missed you missed some gold that I think you will have to cut because Ramona was making a doctor's appointment.
00:32:17.759 --> 00:32:21.759
But no, I was not looking for the tech books, I was looking for the religion books.
00:32:21.759 --> 00:32:22.720
Did you know?
00:32:22.720 --> 00:32:45.599
I'm not sure if this has come out in the podcast, but I my degree from LSU, which my origin story has been on the hand, yes, but my degree from LSU, I have a major in applied mathematics, but a minor in comparative religious studies, because I had to take one course on religion as like an elective, and the professor was really good.
00:32:45.599 --> 00:32:47.279
She was really tough, but she was really good.
00:32:47.279 --> 00:32:48.960
And I was like, this is fun.
00:32:48.960 --> 00:32:51.279
And so I took a bunch of other courses.
00:32:51.279 --> 00:32:55.279
And so I find the study of various religions very fascinating.
00:32:55.279 --> 00:33:05.839
And we had that was right around when I was getting into tech, and I ended up taking this one course on sort of like the Buddhist philosophy of the mind.
00:33:05.839 --> 00:33:19.599
And one of these two books has a great section talking about like Buddhist theory on how the mind works.
00:33:19.599 --> 00:33:30.000
And I remember reading it, and there was a particular chapter on like memory, and like talking about how do our minds retrieve a memory.
00:33:30.000 --> 00:33:31.680
Like, how does that work?
00:33:31.680 --> 00:33:34.880
And I remember reading that and thinking, huh, this is fascinating.
00:33:34.880 --> 00:33:41.279
I wonder if someday this will be applicable to people building intelligent, you know, computers.
00:33:41.279 --> 00:33:49.359
And the books are, I think it's this one, The Psychology of Awakening or this one, The Resonance of Emptiness.
00:33:49.359 --> 00:33:52.160
Let me let me look in the table of contents.
00:33:52.720 --> 00:33:53.920
Are these textbooks?
00:33:54.240 --> 00:33:56.799
Or are they these are textbooks.
00:33:56.799 --> 00:33:57.200
Yes.
00:33:57.599 --> 00:33:58.240
I see.
00:33:58.240 --> 00:33:59.759
Alright, I'll put them on my list.
00:33:59.759 --> 00:34:09.440
I got a lot of books on my list right now, though, so but uh if you are able to pinpoint which one it is, although I'm pretty sure an LLM could answer this.
00:34:10.159 --> 00:34:11.280
I'm sure it could.
00:34:11.280 --> 00:34:17.280
And one of them in particular had a section on memory.
00:34:17.280 --> 00:34:21.360
It could be possibly one of the other books, but I'm almost certain it's one of these two.
00:34:22.079 --> 00:34:27.360
We're using Gemini 3 folks, because ChatGPT has been broken for a number of days.
00:34:27.360 --> 00:34:33.599
Both books explore the intersection of Buddhism and psychology, but they approach the topic of memory in different ways.
00:34:33.599 --> 00:34:46.800
The book that focuses more explicitly on the psychological and philosophical mechanics of memory is The Resonance of Emptiness, a Buddhist inspiration for contemporary psychotherapy by Gay Watson, Memory in Resonance of Emptiness.
00:34:46.800 --> 00:34:53.679
In this book, Watson discusses memory primarily in the context of how our sense of self, in quotations, is constructed.
00:34:53.679 --> 00:34:58.719
She explores how memory acts as a bridge that creates a false sense of continuity and identity.
00:34:58.719 --> 00:35:06.719
The key chapter, memory is discussed most significantly in chapter four, the consciousness that views some ideas of the self.
00:35:06.719 --> 00:35:13.599
The argument Watson explains that our mental continuity is the result of habit, memory, and conditioning.
00:35:13.599 --> 00:35:25.440
She argues that what we perceive as a solid in quotations eye is actually a construct built from aggregates of past sensory perceptions that have quote unquote hardened into memories.
00:35:25.440 --> 00:35:26.880
Does that sound right?
00:35:27.599 --> 00:35:28.239
Yes.
00:35:28.239 --> 00:35:31.920
I'll have to read a little bit later and see if I can find the specific.
00:35:32.239 --> 00:35:33.599
Yeah, that sounds about right.
00:35:33.599 --> 00:35:47.519
To be confirmed next episode, when Bryce has read a little bit, and once he has once he has nailed it down, I will add it up to my books to read, folks.
00:35:47.519 --> 00:35:54.400
The book that I was hoping he was going to say was Permutation City
by Greg Egan.
00:35:54.400 --> 00:35:55.360
Have you heard of that book?
00:35:55.360 --> 00:35:56.239
I have not.
00:35:56.239 --> 00:35:56.960
I was.
00:35:56.960 --> 00:35:59.679
This will be our last story, because we gotta go soon.
00:35:59.679 --> 00:36:03.760
I was listening to another podcast, and a future podcast.
00:36:04.400 --> 00:36:04.960
Where are we going?
00:36:05.119 --> 00:36:05.360
What?
00:36:05.360 --> 00:36:10.400
I gotta go to dinner at my now wife's mother's tonight.
00:36:10.400 --> 00:36:29.039
And anyways, there will be a future episode when that I'm gonna record in the next week or so called The Podcast Purge, which is about all the podcasts that I've removed from my list of podcasts, which it'll be a backup episode for when whatever I've run out of episodes and I don't have time to record one.
00:36:29.039 --> 00:36:32.800
And anyways, this podcast did not get purged.
00:36:32.800 --> 00:36:42.480
It's called the Peterman Pod, and it is interviews with high-level ICs at different companies and talking about how to get promoted and advice, etc.
00:36:42.480 --> 00:36:48.480
It's pretty decent, more because he talks to folks at different companies, meta, alphabet, blah, blah, blah.
00:36:48.480 --> 00:36:55.440
In one of the more recent interviews, he talks to Boris Cherney, who is the author of Claude Code.
00:36:55.440 --> 00:37:04.639
And in that episode, link in the show notes, he discusses the interview process when he was interviewing at Anthropic.
00:37:04.639 --> 00:37:12.079
And he mentions that at some point his book, Favorite Book or something, comes up and he says it's a book by Greg Egan.
00:37:12.079 --> 00:37:13.760
He doesn't actually name the book.
00:37:13.760 --> 00:37:17.440
So I don't actually know if this is the book he mentioned, but I asked Gemini.
00:37:17.440 --> 00:37:22.880
There was a Peterman pod where Boris Cherney was being interviewed, and he mentioned a book by Greg Egan.
00:37:22.880 --> 00:37:23.760
What was the name of the book?
00:37:23.760 --> 00:37:27.280
And the book that the LLM came up with was Permutation City.
00:37:27.280 --> 00:37:35.920
And the remark that Boris made was that in general, whenever he brings this book up, no one's ever heard about it, let alone read it.
00:37:35.920 --> 00:37:47.920
And he was talking or being interviewed by a panel of folks, and not only had all like three of them or all of them heard of the book, they had all read it, and then instantly they were like, oh yeah, that that book is good.
00:37:47.920 --> 00:37:49.519
What about these books?
00:37:49.519 --> 00:37:52.880
And the book is fantastic.
00:37:52.880 --> 00:37:57.519
It's not as good as the three body problem trilogy, which is my favorite books of all time.
00:37:57.519 --> 00:38:16.800
But it is very thought-provocative if you like the TV show Pantheon, which apparently Pantheon is based on a set of short stories by Ken Liu, who is the individual that translated the three body problem, which was originally authored, I believe, by Jin Lu, who is a Chinese author and wrote it in Chinese.
00:38:16.800 --> 00:38:21.440
Anyway, so I do plan to go read the Ken Liu short stories that Pantheon was based on.
00:38:21.440 --> 00:38:24.079
I think that was Joao, the recommended that show.
00:38:24.079 --> 00:38:27.519
Once again, not the world's best show, but it is very thought provocative.
00:38:27.519 --> 00:38:36.400
If anybody has suggestions similar to Permutation City, I'm on a massive AI uploaded intelligence kick.
00:38:36.400 --> 00:38:40.400
And I just finished reading Diaspora by Greg Egan.
00:38:40.400 --> 00:38:42.400
Wasn't as good as Permutation City.
00:38:42.400 --> 00:38:48.159
I'm in the middle of reading, although this is rated R, so if you are below a certain age, do not go read this book.
00:38:48.159 --> 00:38:51.360
I was shocked at how like rated R this book is.
00:38:51.360 --> 00:38:53.679
It's called the Rated R in what way?
00:38:53.679 --> 00:38:55.039
Uh like the content.
00:38:55.119 --> 00:38:58.000
Like it's it's like vi violence or sex, Connor.
00:38:58.000 --> 00:38:58.559
Violence or sexual.
00:38:58.800 --> 00:39:00.000
All of the above and more.
00:39:00.000 --> 00:39:18.880
I'm in fact, my my one of my best friends, you met him at the wedding, Victor, he recommended this book to me a while ago, and apparently also recommended Permutation City, and I, for whatever reason, I usually read whatever he tells me right away, but for some reason this slipped through the cracks, and I am surprised he did not give me a warning about reading this book.
00:39:18.880 --> 00:39:29.199
I mean, I'm a adult, so it's totally fine, but it's like when you recommend someone Black Mirror, if they're gonna start with season one, episode one, which is the one that involves the pig, you have to give people a warning.
00:39:29.199 --> 00:39:34.079
And I actually tell people just skip that episode because it's just too disturbing.
00:39:34.079 --> 00:39:40.239
Anyways, I the name of the book that's rated R is The Metamorphosis of the Prime Intellect.
00:39:40.239 --> 00:39:48.639
So far it's it's it's not lived up to the hype that my buddy Victor sold it, because he said if you like Permutation City, you have to read this book.
00:39:48.639 --> 00:39:50.719
And so far it's not as good as Permutation City.
00:39:50.719 --> 00:39:56.960
Anyways, do you have any other book recommendations while we're wrapping up this 2026 AI and predictions episode?
00:39:57.119 --> 00:40:01.280
I've been trying to work my way through the the entire works of Asimov.
00:40:01.280 --> 00:40:06.320
I've read a lot of his later stuff, but I haven't read some of his like earlier stuff.
00:40:06.719 --> 00:40:10.079
What is is the earlier stuff foundation or is the later stuff foundation?
00:40:11.199 --> 00:40:14.239
Sorry, the by later stuff I mean like in his timeline.
00:40:14.239 --> 00:40:23.360
Like I've read like Foundation and like
onwards, I've read I had not read a lot of the like earlier things, like earlier in his timeline.
00:40:23.760 --> 00:40:25.840
One, have you seen the Apple Plus TV show?
00:40:25.840 --> 00:40:26.960
And two, yes.
00:40:26.960 --> 00:40:29.039
And two, are you not bothered?
00:40:29.039 --> 00:40:36.880
Because I tried to get through, I think I got through one and a half of the Foundation books or however many there are, and I just could not stand the time jumps.
00:40:36.880 --> 00:40:40.800
It's like I get attached to these characters and then boom, they're all gone except for one.
00:40:40.800 --> 00:40:41.920
And they're they're like different.
00:40:42.159 --> 00:40:43.840
Nah, I was ca- I was always kind of fine with that.
00:40:44.000 --> 00:40:44.480
It just dragged me.
00:40:44.719 --> 00:40:47.599
And I think that they I think that they did it very, very well on the TV show.
00:40:47.599 --> 00:40:49.519
Right now I'm on the robot series.
00:40:49.519 --> 00:40:59.039
I'm on The Robots of Dawn, which is it's like this series of three books about a detective from Earth who goes and solves some crimes that involve robots.
00:40:59.039 --> 00:41:03.920
But my favorite one was the is it, I think is it iRobot?
00:41:03.920 --> 00:41:09.760
Yeah, it's iRobot, which is its collection of s of short stories by Asimov.
00:41:09.760 --> 00:41:14.559
It's 1950, and that's the book that introduces the three laws of robotics.
00:41:14.559 --> 00:41:24.559
And and and the short stories all involve various contradictions or paradoxes involving those three laws.
00:41:24.559 --> 00:41:26.639
And I I think it's a very good book.
00:41:26.639 --> 00:41:29.840
And I think it's it's it really got me thinking.
00:41:29.840 --> 00:41:32.320
I think I read iRobot like a year or two ago.
00:41:32.320 --> 00:41:39.519
It really got me thinking about how are we going to actually design, you know, robots that don't kill us all.
00:41:39.519 --> 00:41:42.079
And it's not my job, but it's somebody else's job.
00:41:42.079 --> 00:41:45.039
But good luck with that, whoever, whoever's job that is.
00:41:45.039 --> 00:41:46.239
You know, good luck with that.
00:41:46.239 --> 00:41:47.280
That seems like that's a hard one.
00:41:47.599 --> 00:41:53.360
It's crazy that you just mentioned that because in the metamorphosis of the prime intellect, I'm only 40% of the way through it.
00:41:53.360 --> 00:41:59.599
It literally brings up the Asimov three rules of robotics or laws of robotics or whatever it is.
00:41:59.599 --> 00:42:10.639
And literally they're talking about that contradiction that at one point, you know, there's this sentient, intelligent, whatever, I don't even know what it is, system algorithm.
00:42:10.639 --> 00:42:19.840
And it's called the prime intellect, and it is told to do something, but it would have harmed or potentially put a human at risk.
00:42:19.840 --> 00:42:23.119
And so it says, Well, I can't do that because of my the first rule.
00:42:23.119 --> 00:42:32.400
The first rule overrides the second rule, and then military corporate interests are upset because you know they can't harm people.
00:42:32.960 --> 00:42:33.599
Yeah.
00:42:33.599 --> 00:42:36.480
Alright, well, I should let you get going to your Alright.
00:42:36.559 --> 00:42:39.840
We're supposed to still on the on the docket of topics is Parrot.
00:42:39.840 --> 00:42:42.960
We still have not actually had a full uh parrot deep dive.
00:42:42.960 --> 00:42:44.400
Oh, we've not.
00:42:44.400 --> 00:42:45.119
We have not.
00:42:45.119 --> 00:42:49.199
Was was back in October.
00:42:49.199 --> 00:42:53.920
We gotta have a parrot breakdown, but coming in the future, folks.
00:42:54.079 --> 00:42:54.320
Yeah.
00:42:54.320 --> 00:43:00.400
Well, well, we can record at some point we can record when you give me an update on parrot, and uh and then people can experience.
00:43:01.039 --> 00:43:01.519
Alright.
00:43:01.519 --> 00:43:02.960
Till next time, folks.
00:43:02.960 --> 00:43:06.400
That is the 2026 Look Ahead episode.
00:43:06.400 --> 00:43:11.920
And we look forward to all of your comments and feedback on the last episode.
00:43:11.920 --> 00:43:17.440
If you want to leave comments and feedback on this one, there will be another GitHub discussion as well.
00:43:17.440 --> 00:43:28.639
Until then, be sure to check these show notes either in your podcast app or at adspthepodcast.com for links to anything we mentioned in today's episode, as well as a link to a GitHub discussion where you can leave thoughts, comments, and questions.
00:43:28.639 --> 00:43:29.440
Thanks for listening.
00:43:29.440 --> 00:43:31.199
We hope you enjoyed and have a great day.
00:43:32.000 --> 00:43:34.719
Low quality, high quality.
00:43:34.719 --> 00:43:37.280
That is the tagline of our podcast.
00:43:37.519 --> 00:43:38.400
That's not the tagline.
00:43:38.400 --> 00:43:41.360
Our tagline is chaos with sprinkles of information.