Algorithms + Data Structures = Programs - Episode 279: ArrayBox.dev & Agentic Software Development

Episode Date: March 27, 2026

In this episode, Conor and Bryce chat about ArrayBox.dev, some Parrot algorithms, the future of agentic software development and more!Link to Episode 279 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)TranscriptSocialsADSP: The Podcast: TwitterConor Hoekstra: LinkTree / BioBryce Adelstein Lelbach: TwitterShow NotesDate Recorded: 2026-03-10Date Released: 2026-03-27arraybox.devTryAPLBQNPADUiuaPADemscriptenJ Language: From C to C++20 - LiveStreamSafe3.dyalogBill Burr destroyed Steve JobsSoftware is in Decline - Jonathan BlowParrotParrot on GitHubCCCL cuda.computeHoogle Translate whereZuriHacNorthwest C++ Users' Grouppodgod.caIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8

So Wiwa is implemented in Rust. Dialog APL is implemented in a combination of C and C++, but it's closed source, so you can't see it. J is implemented in C, albeit a version of C that I would call macro C because there's like 10,000 macros and you basically code in the macros, not an actual C. BQN is implemented in C, although the initial version that I used was a JavaScript implementation. Tiny Apple is implemented in Haskell, and CAP is implemented in Kotlin. You know, we might have services that are like 99.999% reliable, but we do not have software that is 99.99% bug-free. Even the best software releases have some amount of bugs in them. It's called Map in Parrot C++. It's also called Map and Parrot-C-Pythor.

And the KudaC-plus Back-Bin uses an iterator. Transform iterator. So it's, you know, basically the same thing. Welcome to ADSP the podcast, episode 279, recorded on March 10th, 20206. My name is Connor, and today with my co-host, Bryce, we chat about arraybox. com, some parrot algorithms, the future of agentic software development, and more. All right, what should we talk about next? Should we talk about, we've mentioned array box a couple times. We should, yeah, let's talk about a parrot is still on the short list of things that we have yet to talk about.

But you said a ray box, okay. So array box is something that I started back. in January. It's now been live arraybox.dev for, it looks like, since February 6th or 7th. So over a month now, we're recording this on March 10th. And there's been just under 1,000 unique visitors. I made the mistake of when I initially launched it. I didn't really look at how they were tracking the visitors.

And I only wanted, like, unique IP addresses, but they were resetting it every 24 hours. So pretty quickly, I hit, like, 1,500 visitors. and I was like, that seems a bit high. And when I asked for an explanation, they said, oh, yeah, it's like resets every 24 hours. And I said, no, no, no, no, no. Like, just, I want, once they visited, I don't want it to count. I want to know, like, over time how many people actually visited. And it said, okay, and I'll store the IP addresses.

And I was like, no, no, no, no, don't store people like, IP addresses. I don't, I'm tracking nothing here. And they were like, all right, I'll do whatever, hash encoded, so you don't know. And there's been just under 14,000 code evaluations. and it's pretty, it's pretty fantastic. So the idea of the website is there's a bunch of online repels for different array languages. There's try APL for Dialogue APL. There's BQN pad for BQN.

There's WiiWA pad for Wii wa, et cetera. Some of these are better than others. And I basically just wanted a one-stop shop where you could code in all of these languages. And so that's basically how I started. I went to, I went to cursor, 4.6 opus. or maybe it was 4.5 at the time and said, I want like an online repel

and at the time I thought this is how the way would have to be built. Tiny Apple is built in Haskell and they have a Wazam back end so that can be client-sat. Tiny what? Tiny Apple, tiny APL. The creator of the language

pronounces it tiny Apple. So the six languages that I support at the moment are Dialog APL, BQN, J, WeWA, tiny apple, and cap. That's KAP. And so five of those are Unicode languages, and J is an ASC-based language. And so in order of how I'm looking at them, Wee was implemented in Rust, Dialogue APL, and most of them, I think actually all of them are open source except for Dialogue APL.

So Wewa is implemented in Rust. Dialogue APL is implemented in a combination of C and C++, but it's closed source, so you can't see it. J is implemented in C, albeit a version of C that I would call macro C, because there's like 10,000 macros and you basically code in the macros, not an actual C. Although, you know, technically a macro is C code. BQN is implemented in C, although the initial version that I used was a JavaScript implementation. Tiny Apple is implemented in Haskell, and CAP is implemented in Kotlin. And so initially, I thought that Wiiwa, because it's in Rust and they've got a Wasam, Comptain, compilation, you know, backend. BQN because I had the JavaScript implementation via BQN.js.

And Tiny Apple, because it is in Haskell and has a WASM backend as well, I thought those three you could just build, you know, the JavaScript wasom things that can live in the browser. And the other three would have, require a server. And so that's what I went about doing that, got it all working. I actually thought because Kotlin has something called multi-platform Kotlin or Kotlin multi-platform. I think that's what it is. KMP. And they have the ability to do stuff across, you know, different platforms. However, I couldn't get this working initially.

And so that's how the website started. I launched it at the beginning of February. Three of them were client side and three of them were server side. And server side was a laptop sitting down beneath my TV. But of course, you being a mature and responsible adult have moved it to a secure. you know cloud environment right no no it is still and it's not just any laptop it is my my wife's old 2012 macbook pro which barely works i mean yesterday i think yesterday the so i have an array box server manager that basically runs and serves endpoints and it's it was running for i think like

200 plus hours which 24 so it was like over a week straight and we this is all this is all also our media laptop. So it's H.D.I. plugged into our TV. So if you want Conner's Netflix password. And admittedly, when I set this thing up, at some point I said, you know, put this in, you know, a Docker sandbox and, you know, make sure it can't be hacked. And when I launched it, though, as soon as I put it live, I didn't launch it on the YouTube channel, so I just told a few people about it. And you were, I don't know, probably the sixth or seventh. And everybody that I told immediately started trying to go, like, run shell commands because APL, Dialog APL, J, and CAP, all have the ability to run, like, you know, shell commands locally. And so I started getting

all these messages of like, oh, I can look at the contents of this container. And I'm like, okay, that's great. And, but like, it didn't matter that much. But you pointed out to me when you, so when I told you about this, you immediately started trying to hack this stuff. You might be thinking, how does Bryce know J? Bryce does not know J. But AI knows J. Jay. So Bryce is like showing me that he's like looking at the contents of the container. But you asked or pointed out at some point, you were like, if these are, you asked what they were implemented in. And I said, J's implemented in C and a dialogue APL is in C and C++, but it's, closed source. And then you said, well, if it's implemented in C, can't you get an inscriptum build

running? And I was like, that's a fantastic point. And idea. Why did I not think of that? Sure enough, I went to the J source code. They already have like flags for. an inscript and build. So I just had to build it. And there was actually another Repel online called the J Playground. And I actually just asked Cursor and Claude, like, what are they doing? And they said, oh, they're actually using an inscriptum build as well. So I went and set up the, and that's the thing. I don't know how to go and, you know, set up the and I remember actually several years ago, I did a 10 or 8 or 10 hour live stream where I was porting the J source code to C++. And I swear to God, I can go find it. I spent the first

five hours of that live stream just trying to get Jay to build. Like this is what we're talking about in terms of like 100x productivity multiplier. I now ask cursor and Claude to do it. Not only do they go and do it,

they get the inscriptin one working in like 10 minutes later. I have my whole backend written. It's now client side. It's no longer on the server. And so now we're down to two languages on the server. And I was like, well, if I can do it for Jay,

I certainly should be able to build this from scratch because at first I was just trying to pull like executables from other places and not build stuff from source but then I basically once I had the website up and running and people were trying to hack it I was like all right so I just said this is Kotlin multi-platform can you build this and get me like a Kotlin native or like running in the browser sure enough five minutes later it's working and so now we're down to just Dialog APL which is the only one running on the server and even that was a bit insecure

but I asked a couple folks about it or I'm not they had told me about it and so then I said I told I asked cloud and cursor like there is some kind of security thing that try APL uses and that's called like safe three dialogue so it went and found that it took it a while for it to iron out all the kinks but it's just wild like you know you're a passer buyer you don't know anything really about like Jay or these languages but you using AI figure out basically how to hack my machine but then you come along with an idea and that idea like that idea like you're a I take, send it back to the AI, and it is just wild that like I have wanted this kind of website like forever because I'm constantly for my YouTube videos, you know, testing out these esoteric array languages like cap and tiny Apple that like admittedly not many people have heard of, but there's some really interesting ideas in those languages, but the online repels are pretty bad and like navigating the docs and like switching. It's just cumbersome and not the experience that I want. And now, like, when I want to bring up docks and stuff, I just hit F1 next to a glyph.

And the code editor just slides to the left. The docs show up, like, on the same screen. It looks beautiful when it works. There are some bugs here and there. But it's just wild that this is the world that we live in. And I just, I thought it was so awesome that you just, like, it reminds me of Bill Burr has this, like, Steve Jobs joke, where he's like, what did Steve? What is the big deal? Why are all these nerds such a big fan?

You know, what did he do? He has this bit. I'll cut it in here. But my impression of it is he's eating an apple going, All right, here's an idea. Big small, big small, make it happen. Actually, nerd Jesus died in the last year, right? Steve Jobs.

Yeah, he died, right? I know, I know, a lot of nerds here tonight. I know, you're sad. I didn't get it. I didn't get the big deal they made about that guy. What did he do? He told other people what to invent? I want my entire music collection in that phone.

Get on it. Nameless, faceless scientist. Got to go in a back room and figure it out. Steve Jobs just walking by. I don't hear any thinking going on in there. Just strutting around the office, eating some pretentious fruit like a pear.

Right? Just throwing out ideas. There's another one. There's another one I just came up with on the way to work. I was reading a magazine the other day, turning pages, you know? I'd like to turn pages on a screen

that aren't even there. Yeah, wrap your fucking heads around that guy. See you in eight years. Where are you going, Michael? Big little, big little. Get on it. And he's doing the gesture with his hands to like zoom in and zoom out of a photo. And so he's just this, and like Bill Burr's like a joke is that he's just this guy that would like walk around throwing out ideas and be like, I don't hear you thinking hard enough.

Well, I feel like that's been like a large part of my value add to in the videos. Like every now and then I meet with like a wide variety of people and sometimes I'm like, hey, why don't you try this? or that and then like somebody comes back to me like three months later and they're like I spent the last three months working on that and it worked out or as is the case somebody comes like a week later and they're like yeah I looked into that it's a terrible idea that's like 90% of them but there there is value that's a thing is there is like extreme value in insights like I was about to say ideas but you know taking from Michael it's like ideas that are like you know I don't know what's the word like meaningful you know or worth keeping

in the words of Michael once again, it is like small things that I think about just like experience like UX things with my podcast player. It's so nice now when like these things works. Like every once in a while you'll accidentally end up like hitting the 100% mark on a podcast that you already listen to and I have this like history now. So like I don't have downloaded and up next. I just have a cue and when you're you listen to something,

it gets put in history. And the idea is is you might be able to share like your weekly recap on social media at some point. But every once in a while you listen to something twice, you can just go swipe left, hit a delete button on your history. And maybe you don't even want to share it. That's why you don't want it in your history for whatever reason. You're ashamed.

I listened to the reality receipts podcast because I saw a reel on Instagram on the Love is Blind season 10 finale episode because Shima and I watch Love is Blind. And, you know, am I ashamed that I listen to the reality receipts podcast? Clearly not because I'm mentioning it here. but others might be. And they might want to remove it from their history before they, you know, share some weekly recap. And stuff like this, you know, if more people had great ideas and were implementing them, we would all not be whining about the quality of the software that we use on a day-to-day basis,

you know? Have you seen that Jonathan Blow 10-minute clip where he just, like, tracked everything that was like broken with the software he was using over like a one or two-day period? No. But yeah, I can imagine. I can imagine. And his point is that like we, we are like desensitized to how awful software is. We're just used to like, you know, swiping up on the app to close it and then reopening it.

Like we are so desensitized to like, oh, it's not working. I'll just restart it. Like, and when it shouldn't be that way, it shouldn't be that way, you know, like, why is it so hard to get things to work correctly? It's like, you know, the complaints that you have about cursor when it was freezing, you know, it doesn't do that anymore. Why? Because you fix it. You fix it. Yeah. I mean, I certainly, you know, it's funny because I do go through that exercise, but like almost only when I'm like using some open source library or like I'm using like one of invidia's products. Like that that Google doc that I showed you earlier with like a like, you know, 100 or 200 to do's in it. Like some of those are things that are to do's for the project I'm working on.

Some of those are to do's for like other projects. Like because I'll like collect like a list of, you know, what's wrong. what could be better. And when you go through and you like actually do that, like, it is kind of amazing just like how quickly that list accumulates. Yeah. It can be, it can be shocking. And yeah, I mean, we take all these things for granted as the reality.

Yeah, it is. And that's the thing is like, even though the Podgod app still has its issues, like it has less issues than the other podcast players that I used to use. Like the cast box had gotten so bad that if you were just not on Wi-Fi, like the app would almost stop working. I think I recounted that, you know, like you'd have to go to the downloads because the queue would just entirely disappear. Like it was, it wasn't network dependent. It was, oh, go ahead. The Amazon Prime Video app for like the last week for me, I cannot watch any content when not connected to Wi-Fi.

I've checked all the settings. I have uninstalled and reinstalled the app. I have cleared my cache. I have, like, cleared all my data. It's like nothing I can do can fix it. Or I remember one time right at all right at my iPad, there was a period of time where, like, my iPad, the screen brightness setting was like always messed up. And if you set it to full brightness, like, any video that you would watch would just like look completely wrong. And it was like that for like, you know, a month.

And it's like, how does, how do big companies in a scale? how do like things get out in the wild like that, you know? And the reality is that, you know, quality control is just not, you know, we might have services that are like 99.999% reliable, but we do not have software that is 99.99% bug free. Even the best software releases have some amount of bugs in them. Yeah, I mean, this is something that I've really started to think about in terms of, like, how do you develop in a, you know, vibe coded or agentic, you know, you know,

lead driven world. And I was talking to Asher Mancinelli, a fellow Nvidia about this the other day. And I was, I was thinking about this while I was like falling asleep as like, what is going to be the new, like, you know, there's TDD test-driven development, DDD, domain-driven development. There's a bunch of these different ones. And I was thinking of the title of a talk, that's odd for ODD, which is like outcome

driven development or something like verification driven development. Because like right now, one of the issues I run into with the podcast app is that sometimes I'll fix something and that'll break something else. But like, you know, I know. I know that there are some kind of Android, you know, UX. You know, it'll have some like workflow and it'll test stuff. But, you know, I have to look into that because it's very tricky for like download an episode and then listening to it and it hits the 100% mark. And then it should automatically remove like testing.

And so the point is, is like even if we're not talking about like some hobby project, we're talking about work. And we're trying to write some kernel that, you know, is speed of light. And like, are we just going to be like setting up, you know, we have unit tests and we've got lynn's. We're all going to become, to some degree, DevOps engineers and test engineers. And what I mean by that is that the importance of testing and verification will only increase. Of course, of course. You know, like, I think if you think about it in the past, if you had your own project, you would, you didn't necessarily need to set up like code formatting or code linting rules or like all these various checks because it was like just you working on it.

But, like, my experience has been as soon as I have a project where I have external collaborators, then I have to set up all the code formatting and everything so that, like, everybody, everything is consistent across the code base. And I think it's, like, sort of similar here where it's like, you have this external collaborator on any project. And, like, the thing that I spend most of my, the majority of my time thinking about is, like, how can I add more checks or verification or validation? And it's funny.

I recall a conversation with Titus Wenders, like, in the early days of AI, where his proposition is basically you can't have the AI write the tests, that like the tests need to be written by the people because if you have their AI write the tests, then they will, you know, write tests that will, you know, basically just test what the code currently does, not necessarily what it should do. And I think time is, like, this was like in 2022, 2023. I think things have evolved a little bit now. And like, obviously, if you're writing tests, like, you know, you're going to use AI to help

you write the tests. But I do think that, like, that's one of the. the places where I spend the most time thinking or like manually reviewing thing is like in the setup of the tests. Because in an ideal world, I shouldn't really need to review the code because, or sorry, I shouldn't need to review the code really for functionality. Like the functionality should all be verified by the tests. Even the performance should ideally be verified by the tests.

Maybe I review the code for like maintainability or style. But like I should know if I've got some AI written. change, I should have a high confidence about whether or not that change works based on the test results. Yeah, I want to show something because it's like we're going to, it's going to, we're just going to be bootstrapping, like using AI to set up these frameworks for testing and performance. And it's just, it's AI all the way down, folks. But so I've got, you know, we're probably going to have to defer to the parrot, you know, the parrot conversation that we've been saying we're going to have for a while. But so parrot,

We released back in October, depending on when you're listening to this, it was 2025. And we're chatting about this in March of 2026. And so we're in the middle. We released that on NV Labs, which is the research GitHub repository. And we're in the middle of building. And so that was built on thrust in Cub to Kuta C++ libraries. And we're in the process of building a Python version built on top of Kuta compute, which is basically a kind of equivalent of the thrust algorithms in Kuta C++.

Plus, we've kind of brought those to the Python ecosystem. And so, you know, I've obviously been using AI to, you know, build this library. And at some point, you know, working on a potential paper. And I went and asked it to build a table of, you know, the names of the different functions and then the implementations. You kind of, you know, succinctly, not the full implementation, but a lot of these operations, here I can blow it up a little bit, are implemented in terms of other things. And so. I'm not that old, Connor. It did this.

Well, I mean, the text is a little bit small. It one-shot at this. And so it basically shows at the top of the table. And there's a bunch of pages of this stuff. At the top, it says it's called map. So for a unary operation, you know, what you call it transform in C++. It's called map in parrot C++. It's also called map and parrot Python.

And the CUDA C++ back-in uses a make-transform iterator. And the cuda.computtube back-in uses an iterator. dot transform iterator. So it's basically the same thing. But you can see that I'm missing the I div from Parrot Python just because I clearly didn't get around to adding it. And on top of that, like when you go down to more interesting operations, so the where function, which is one of my, we'll do a whole episode on where at one point.

It is called where and indices in NumP, if you're familiar with it. We've talked about it on ADSP before. Look at that, a little algorithm content for the listener here. where is a function that takes a Boolean array. So zeros and ones. One for true, zero for false. And it returns you the index that corresponds to the truths, to the ones. So if you're given one zero one zero one, one, for a zero indexed implementation of where indices, it'll give you back zero, two, and four.

And so the implementation for this in Kudacy Plus Plus is range with the size passed to it. dot keep this so you're basically range is the equivalent of iota and you're doing it for size which is the size of your array and then you're doing a dot keep this where this is the mask of ones and zeros so you can think of keep is basically a filter a filter takes a unary operation and does a compaction based on whether the unary predicate returns true or false keep is the equivalent of that but you're given a mask that is equivalent in length to the array that you want to do the compaction on.

So another way of thinking this is well I guess copy if where you're giving it the stencil over the that's not exactly the same thing. But think of keep. Basically another name for keep could be filter based on

Boolean sequence instead of unary operation. Yeah. And anyways, when you go to the Python implementation, it's range, aka Iota, for length,

because that's what they call, you know, size and Python is length. Dot keep self. And so it's just, it's this kind of stuff where you're building a summary of like implementations of two different libraries to see what are the missing pieces, where do they differ. I can't believe it got that like it did this on like the first try. One shot it. One shot it. And it's just so nice.

It's so nice. Can write your paper for you. Well, I mean, I'm going to write the paper myself. But this table, this table is just like a deterministically. that's just like a waste of my time if you can get. But like the idea of this kind of stuff, right? Like having some another dashboard or some kind of thing where you're able to have an LLM, you know, generate this thing and check, you know, where the changes are.

You know, like I said, I feel like unit tests and like lint tests or static tests, this is just like the small, like it's the beginning. Like now, I feel like in the future at NVIDIA we're going to have a bunch of like performance, you know, because we're going to get these AI produced diffs on our libraries. And we're going to have to be able to do performance validation on it. Yeah, totally. Like, like, automating the like code optimization process. Yeah, that's like a very interesting topic.

Like, you know, you can, it's not because you need to not just do performance testing, but you also have to hook in all of the various profiling tools to the LLM. And you have to make sure that it's, it's, it's, reward mechanism that the way that it's measuring is, is, you know, going to be accurate. That it's, like, you have to have your functional checks correct to have your performance checks correct. Because if you, if you don't have really good functional checking, then you can't even start performance checking because then if you start doing performance optimization without the good functional checks, then you'll regress functional behavior. So you have to

have really solid functional testing. And then you have to set up good performance validation that is not going to be accidentally cheated, and then you have to hook up the tools to all the various different ways that we identify and fix performance problems. Yeah, I mean, it's such an interesting, like, problem to think about solving of, like, you can imagine a world where we build systems

by launching these sophisticated, you know, LLMs to generate code, but there's admittedly going to be a bunch of issues, right? But how do you, and that's already what these frontier labs are doing, you know, how do you build context or add context to their prompts so that they give you better code and better whatnot? But you can imagine like some, like, some static analysis tools in C++ and like Klaying, I know they have like a complexity metric where if you have like a certain amount of nesting, you know, it has some flag, right? So like you

can imagine. And one of the issues that I run into with array box is duplicating code instead of having like a single source of truth for something that shouldn't be duplicated, like the set of primitives. And if you can build that into like some kind of unit testing framework, that it is able to track when you duplicate something that shouldn't be duplicated, if you can build enough like guardrails, whether that's for unit tests or for performance or for complexity analysis or like, I don't know what you call it like the code quality, we're just off to the races then. Do we, do we, you know, we are just going to be people that kick these things off.

And then that's it. You know, right? Yeah. Ship it. Yeah. We retire. I don't know. Are we going to, I don't know about that, but yes.

Yes. I mean, I already have my retirement plan. I got to, I'm just going to code. I've decided. Array languages, worst case, they're just fun. They're just fun. And I like thinking about tacit programming models. I like thinking about how awful math.

mathematics notation is and how Iverson tried to reinvent mathematical notation and failed. And there's no reason we can't, you know, we can't change mathematical notation. That's when we, you know, I think I'm going to take the Bartaj Maluski path, you know. We talked about the four horsemen of the Pacific Northwest C++ meetup. There was Andre Alexandrescu, Eric Niebler, Walter Bright, and Bartaj Maluski. and all were hanging out while they were falling in love with functional programming and Haskell and whatnot, Eric took the pragmatic path and he went and tried to bring the power of functional programming to a very popular language like C++ via ranges.

That's not going to be you. Walter went and tried to do a whole language better than C++ called D. Andre joined that fight at a certain point and was working on the D language for like a decade, but then came back to C++. And Bartaj Maluski, he just went and tried to evangelize functional programming and category theory for his whole career, basically.

Yeah. Have you seen him recently? I haven't seen him in so many years. He's a great guy. I met him whenever I was at Zuri Hack, which was definitely like three or four years ago. I... Actually, why did I go to...

I went to Switzerland for a couple of weeks, for vacation and Zuri Hack ended up being there and so I popped in and then I met him in person there and then I've seen him on I think a couple online talks since then but not in person

Yeah have you had you met him in person before like I assume I guess C++ now the original boost con or the last boost con 2011 I think I met him maybe maybe he was at like one C++ now or two C++ now Yeah he's given a bunch

talks to C++ now that I've seen. I haven't been there. Although they were before the recording quality was like peak. Yeah. Good old days. Yeah. All days. Oh, man.

So yeah, we should talk about parrot, but maybe we, maybe we're going to save that from next time. Yeah, it's funny too because someone was asking Discord if I had released the YouTube version of the Parrot talk because the C++ under the C1 still isn't out. And I had said that I was going to record it and put it on YouTube back in like November, December. and I still have not done that. Mostly because I feel like this work that I'm doing right now, I want to give like an updated version of that talk where I talk a little bit more about the implementation

because the talk that I gave at C++ Under the C was mostly about usage, not about the implementation. And admittedly, I think the usage is more important, but the implementation might be more interesting. But anyways, be sure to check these show notes, either in your podcast app or at ADSP the podcast.com, for links to anything we mentioned in today's episode, as well as a link to a get-up discussion

where you can leave thoughts, comments, and questions. Thanks for listening. We hope you enjoyed and have a great day. Low quality, high quantity. That is the tagline of our podcast. It's not the tagline. Our tagline is chaos with sprinkles of information. So when's your, what's your due date?

Due date is September 15th. Okay. Yeah. Pretty, pretty exciting, I guess. Yeah? It's pretty exciting. I'm excited for you. I'm sure you're going to be a great dad.

We're going to have lots of, we'll have lots of baby pictures. That's awesome. I will not take any pictures of my baby. You don't take any pictures of your baby? No, I'm just kidding. So you're going to take some time off? Yes, at some point.

But like not right when the kid's born? You don't know what your plan is yet? We haven't really figured out exactly what we're doing there yet, but because we still got six months or something. Yeah. Cool. exciting. Well, tell she my congratulations. Yeah, we got to get, I got to get the pod guide editor done so I can just hit the button. Otherwise, we might be taking a break. But I, I, I, I, we've made it, what, 280 episodes without taking a break yet.

A child shan't stop me. He says now. He says now. Yeah. We'll see though. Maybe, maybe, maybe we should record a bunch of like a month or two worth of. Well, we'll like, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll, we'll. buffer them up, right? Yeah, yeah. And just say, listen, folks, you're going to get 20-minute episodes for the next two months, and then I'm going to resurface in November. All right. I should probably call it because I've got to go make all these slides and... Yeah.

Are you doing training or just giving a talk next week? I'm doing both. And I've just been, oh, man, you know, I feel like the AI makes things more intense. Like, I feel like I'm working more intensely than I have. ever have in the past. And I don't know, I just, I'm almost like, I almost feel a little drained. It'll be nice to, I need to find a time to take a little bit of a break after GTC. Yeah. Yeah, no, it's true. I mean, I said that whatever the last time we recorded is that, like, I work way more now. Yeah. Because. I definitely think that's true. Yeah. I just feel like there's like

a window here too. Like, if I'm going to do, like, everyone's going to be trying to do this in a year. Because it's going to be, you're not going to need to know what like ADB is and how. to host a website and how to whatever like there is there's going to be like a tsunami of like everyone can do everything for a fee all right buddy good to chat later congratulations again yeah yeah thanks it's very exciting later later later