# How to Actually Code with AI (ft. Matt Pocock)

**Channel:** NetworkChuck
**Source:** https://www.youtube.com/watch?v=mU8WKII1gpk
**Transcript page:** https://www.withtranscript.ai/video/mU8WKII1gpk

## Chapters

- 0:00 — Introduction: Who Is Matt Pocock
- 5:03 — Tactical vs Strategic Programming
- 9:45 — Software Engineering Is Easier Than You Think
- 12:37 — Live Demo: Grill With Docs Skill
- 19:23 — Skills Anatomy: Glossary and ADRs
- 24:59 — From Grilling to Specs and Tickets
- 28:27 — Context Windows and Effort Levels
- 34:29 — Code Review, PRs, and the Retro Loop
- 44:52 — Trust Ladder and Automated Checks
- 52:32 — Getting Started Stack and Deep Modules
- 1:01:02 — Improve Codebase Architecture Skill
- 1:08:38 — Teach Skill and Learning Fundamentals
- 1:14:10 — DevOps, Hosting, and Deployment Made Simple
- 1:20:09 — Security, Skill Evals, and CI/CD
- 1:25:57 — Open Source in the AI Era
- 1:34:41 — Advice for Aspiring Developers and Books
- 1:40:42 — Hiring, Courses, and the Software Factory
- 1:47:35 — Video Editor, Course Creation, and Knowledge Work
- 2:00:13 — Outro and Closing Prayer

## Transcript

**[0:00] Speaker A:** Would you say that anyone needs to learn a specific programming language right now? Nah. I think that software engineering has always been easier than people think it is, right? Coding has always been easier than people think. I would have relatives coming to me and say, "Yo, you must be so smart. You're a coder. You know, you know how all that stuff fits together." You know, but you just learn it. I do not have a software development background. Yet, I can now do it all. If I ask AI to code something, it can code it all day. But I can feel the limitations and I think everyone else does. Engineers tend to produce better products than non-engineers right now because they have the domain expertise. They know what to ask for. They have the right language. Let's take a high school kid. They want to become a software developer.

**[0:40] Speaker A:** And in this day and age, it's like what does that mean? Should they? What I would say is

**[0:54] Speaker B:** first of all, thank you for making the time to do this. No worries.

**[0:57] Speaker A:** I know you've been busy. Like you just launched your new uh AI crash course and your new skills like was it 1.3 you released?

**[1:04] Speaker B:** That's right.

**[1:04] Speaker A:** Yep.

**[1:06] Speaker B:** That's awesome.

**[1:07] Speaker A:** Y congrats. I've got a I've got a baby coming in uh late November and I'm trying to get a course out before then. It's unusual. I have this hard of a deadline, you know, but the baby is coming. Let's go ahead and get started. So, first for people who don't know who you are, which I'll kind of give you an intro. We can just kind of cold start here. Um you are Matt PCO and the where I've heard about you was initially your skills, which I think is what most people um that's their gateway drug to Matt PCO and um everyone uses them. It's like the de facto thing to use for AI coding now. But everyone just kind of adopts your skills to their own workflow without exactly looking at everything you do. I think that's kind of my my that that was kind of my approach.

**[1:49] Speaker A:** But then I saw that you had a course and I'm like I'm going to buy the course. So I bought your course and it's awesome. Um but it's also challenging and which is why I wanted to have this conversation with you. So um real quick, if there's anything I missed about you, can you go ahead and tell the audience who you are and what you're about? No, I mean I right now I'm the AI guy. I suppose I'm the skills guy. Um I've not always been this person. Uh before I was the TypeScript person actually. So I was a hu influencer in the TypeScript space. I was teaching Typescript courses and that came out from uh working in open source on very very very challenging TypeScript projects like XATE. I don't know if you've heard of Xate. It's a tiny little library. Well, not actually that tiny but it's about state machines and state charts in Typescript.

**[2:32] Speaker A:** And I was trying to make that type safe and that was a blooming nightmare. Uh taught me a lot about TypeScript and I released a course about that and went full-time teaching based on that course which was called total typescript and that meant that when a AI came around I was looking for my next project. Basically I didn't know what I was going to do and AI came and I realized ah this seems interesting. took me a while to get there because I was pretty skeptical, but I have risen through my skepticism and now yeah, I'm definitely one of the skills people pushing their skills out there and just trying to write down interesting processes I find and things that work and shipping them as markdown files. So, the reason I'm so excited to talk with you is I think I'm in a place of a lot of other people where I I have now been given a magic wand.

**[3:22] Speaker A:** I can do whatever I want, but I need to go to Hogwarts to learn how to use this thing. And I uh I I'm coding like crazy. I'm probably coding as we speak. I I I'm sure I have an agent doing something, but I know I'm not doing it well. And I know there's a way to do it well. And and and where I'm really curious, and I think we're going to end up talking about this at some point, is where is coding sitting right now? how much can we give away to the agent and trust it versus how and I think you the term you use is putting agents in a straight jacket which I love that because it's like they do go off the rails and they do get kind of crazy. So that's why I'm excited. I think a lot of people in my audience are in the same boat.

**[4:03] Speaker A:** Like I do not have a software development background yet I can now do it all. I don't have to know how to write any code but I can feel the limitations and I think everyone else does. Like I made this app but it's on my computer. How do I get other people to use it? I don't know what's the best way to do it. let me ask my AI agent and then they spin up Versell or they do something random and it's it's their opinion and it's not good. So what I would love to know and we I guess we can just go ahead and jump into this. Can you tell me what actually you tell me what what is the best way to approach software development right now with AI coding? Cuz like you you teach the course, you're the master. How can how can we step into this?

**[4:43] Speaker B:** I don't like this framing. I don't like the framing of me being the guru and you guys being the students. You know what I mean? Like that's that's it's that's not what I'm going for at all. Like I you know I've got a bald head, right? I live near Oxford. I've got glasses. That doesn't make me smart. Doesn't make me smarter than you. Right. And I've got the British accent too which helps. But it it helps so much. You have no idea.

**[5:01] Speaker A:** So much right.

**[5:03] Speaker A:** So okay, Johnow in his book a philosophy of software design talks about the difference between tactical and strategic programming. Right? Tactical versus strategic. Tactical is like the on the ground sergeant trying to win the battle and the strategic stuff is the general trying to win the war, right? The long view. And whenever, you know, preai, whenever you were working, you would try to be working with a bit of tactical and a bit of strategic all the time, right? You'd be thinking about, okay, how does this change make a difference in the long term? And also, how does this change like how does it accomplish my short-term goals? How does it help me win the battle of today? Now AI is really good at tactical programming and terrible at strategic programming. It's just garbage at it. It because of the way it's trained and because of the way like you think about an AI in a benchmark, right?

**[5:57] Speaker A:** It has a task to fulfill and it's being judged on that specific task. In other words, its focus is 100% tactical. Whereas it's not you're not going to get better scores on the benchmark by thinking long term and thinking strategically. And even how would you grade that, you know, it's very difficult to grade that because your strategic mistakes don't usually come back at you until like 9 months down the line, you know. So to in order to get good at working with AI, you need to get good at the strategic stuff because AI can take the tactical stuff, can eat it for you, but unless you're careful, it'll just focus on the stuff for now and won't care about the stuff long term.

**[6:38] Speaker B:** Okay. And I I do feel that because you're right, like if I if I ask AI to code something, it can code it all day and it it will even go in a very bad direction because it just wants to be that agreeable assistant for me. But strategy is where it's weak. Um would you say that's the the biggest weakness you see right now with people jumping into vibe coding?

**[6:59] Speaker A:** Totally. I mean with vibe coding is a people have like there's this term called semantic diffusion where like words stop meaning the thing they originally meant right and so vibe coding is a stupid um term that now means all sorts of different things I take the original definition which is coding without looking at the code without thinking about the code with considering that the code is just like a an artifact we don't care about now vibe coding I don't think has ever worked if it's the only thing you do right if you're only vibe coding It means that your code will slowly get worse and worse and worse because again this tactical agent is just thinking about how to solve the current problem. It's not thinking about the long term and it gets worse and worse and worse. And because the code is the environment your agent operates in, the environment your agent operates in slowly gets worse.

**[7:48] Speaker A:** It's like the dog meme of the house burning around them, right? And the dog is just sort of sat there going, "Oh, okay." Right? the agent just just watching the house fall down as they're trying to get their jobs done. So, you need someone to keep the house in order and that person is probably at the moment you. I do think that agents might be getting better at this, but they still need to be prompted and told to think about strategy, to care about strategy long term, and right now they just don't. So, you you don't call your course a a vibe coding course. And I and I see why you would steer away from that because that that vibe coding definition still has that negative connotation even though everyone is kind of vibe coding if you if you um if you call it AI assisted vibe coding.

**[8:35] Speaker A:** Vibe coding has a negative connotation. Uh do you think that developers right now all of them should be using AI? Like are they foolish to not use AI? Yeah, it's ridiculous not to use AI because so much of our job before was tactical programming, right? It was it was just mostly tactical and you would get these nice uh relaxing breaks where you could just focus on the tactical stuff, just solve the problem today. Oh, I get to kind of just go into a nice flow state and just solve it. But now you can pay less than minimum wage for someone else to do it, right? It's unreasonable for you to be spending your time doing that. And to be honest, the stuff that always interested me most as you know a developer, as someone who's interested in increasing velocity on our team, increasing the um just the quality of code that we're putting out, the in

**[9:24] Speaker A:** quality of features for people. The strategic stuff was always the most interesting stuff for me. Anyway, so I I mean I love this new age. I don't mind that tactical programming is dead. I'm fine with it. You know, just get me thinking about the long view. let me just sort of cook and create this beautiful um environment for my agents to operate in. I find that stuff really exciting.

**[9:44] Speaker B:** M okay.

**[9:45] Speaker B:** So that's that's where I want to live and I'm hoping that throughout this conversation you will give me and the audience a direction on where we can start actually becoming I guess becoming software engineers in a way cuz like right now I I don't see a place where I'm going to actually go out and hire a software engineer. Like I know I can do it myself. I just know there's a few things I'm missing, a few gaps I need to fill in. Um would you say that's where where people can be right now? Like can we just become software engineers with a few like a course that you produce?

**[10:14] Speaker A:** I think that um software engineering has always been easier than people think it is, right? Coding has always been easier than people think, you know? Uh you know, I would have relatives coming to me and say, you must be so smart. You're a coder. You know, you know how all that stuff fits together, you know? But like it's just you just learn it, right? you know, you just spend like a couple of weeks learning it and you get better over time and you make mistakes and you know, and you've got all these tools to help you out and now agents can help you too. And it's always been easier than it looks. And strategic programming is really just starting to think and care about different things than you're used to caring about. And honestly, so much of strategic programming is just caring a bit more than the person next to you, right?

**[10:57] Speaker A:** is caring about the quality of the thing you're producing, of the code, the environment or the agent operates in. And so so much of that like I could always tell which of the my team members were strategic programmers that had that long-term view because they just cared more. And I think honestly if you're just interested in it, if you want to produce better code and you want your agents to do it, then that's the first place to start. It's just, you know, can I can I swear on this? I'm not sure. Can I curse?

**[11:25] Speaker B:** Yeah. Yeah. Go ahead.

**[11:26] Speaker A:** Yeah. Okay, you have to give a you know what I mean? You just got to give a And so that's the first place to start. Hey, time for a coffee break. And this coffee break is sponsored by Threat Lucker and their learning event Zero Trust World. Did you know about this? It's a thing and it's kind of sick. It's happening February 17th through 19th, 2027. Gosh, is it really already 2027 coming up? At Zero Trust World, you're going to get access to hands-on hacking labs where you get firstirhand experience hacking stuff. And it's okay if you're new to hacking. They have every skill level. They're also going to have mainstage talks, breakout sessions, and technical deep dives. These are experts in the field sharing their knowledge with you. And speaking of experts, you're going to be around a bunch of them at this event. Networking is one of the main reasons you want to go to any type of learning event.

**[12:05] Speaker A:** You'll be spending time with people who are dealing with the same threats that you are. And it's people who are practitioners and also executives. You're going to be making some connections and those sessions you take can be continuing education credits. This event has so much and it grows every year. And the afterparty, I heard, is something you don't want to miss. Why? You got to go and find out. So now I know you want to go. I got a link below. You'll get $200 off or use the code ZTW networkchuck 27. So go to ztw.com and use the code ZTW networkchuck 27. And thank you to Threat Locker for sponsoring this podcast and thank you for taking a coffee break with me. Okay.

**[12:37] Speaker A:** So I I know I didn't prep you for this um and you can say no, but would you be able to walk me through an example of how you approach a coding problem and with with your skills?

**[12:47] Speaker B:** Yeah, totally. So what you want me to screenshot?

**[12:49] Speaker A:** Yeah. Yeah, that'd be great.

**[12:50] Speaker B:** Yeah. I think that's that's the one thing

**[12:53] Speaker A:** I think most people are missing. Anyone can jump into Codex now and go make me this thing. And Codex will start doing lots of things using lots of words people have never seen before. They assume it knows what it's doing. And then they spit out some code and you're like that's cool, but it's not strategic. And I want people to kind of feel what that feels. Oh yeah. See what that feels like as you do this. Totally. So essentially my skills have evolved into a process, right? And that process is different depending on the kind of task that I'm trying to do. And uh I think to answer your question is how am I thinking strategically is that the strategic thinking is sort of blended into every stage of the process. It's not just what am I solving today. It's how my how is the thing I'm solving going to be um uh you know going to benefit this project long term.

**[13:45] Speaker A:** So one I'm I'm inside a repo right now which is I have a sort of course video manager repo which is essentially this huge great big project which is like a video editor. It's an AI writer. It is um essentially where I produce all of my videos, all of my content. And the first place to start is by thinking very very carefully about the language you use when you're working with agents. Now, this comes from a software practice called domain driven design. Right? I've actually literally I've been filming this part of my course today. So, I've got the book next to me. This is Eric Evans domain driven design. Absolutely. Um it's a bit of a tome, right? But is the first couple of chapters that talk about the importance of language in development is so so cool. And so with a couple of my skills, I've got a skill called uh grill with docs, let's say.

**[14:35] Speaker A:** and grill with docs. What it does is it essentially quizzes you, grills you about the thing that you're about to build. You might have heard of my grill me skill, which is like my sort of most famous skill. Um, which is a sort of simpler version of this. So, let's say I go in with Grill with Docs. I'm going to say, I need to improve the teleprompter part of my video editor. I think it's just gotten a little bit cluttered and I think there's some stuff I no longer use in there. Can you help me out? So, I'm just going to give it a vague prompt. Basically, I'm going to send this off and it's going to do a couple of things. It's going to first of all explore the codebase and figure out what we're even dealing with and what we're looking at. And it's going to look in this glossery here for stuff that I've defined in terms of what is actually in my application and what the entities are.

**[15:20] Speaker A:** So inside here, you can see there's language, there's course structure, right? So I have a course and then we have sections inside courses. We have course versions, right? because courses change over time and I keep track of them. And then lessons are single learning units within a section. We have uh draft versions, whether it has changes, pending versions, and all of this stuff is language that I've developed with the agent over time. And that pays off because it means, you know, like how Opus 5 was just garbage to talk to, right? I didn't have that much of a problem with it because it was using the terms in these this glossery, right? It was using terms that I'd already agreed on. It wasn't that verbose because it was talking the language of my application already. And so,

**[16:05] Speaker B:** and by the way, are you using Whisper Flow right now?

**[16:08] Speaker A:** I'm using Whisper Flow. Yeah. Exactly.

**[16:09] Speaker B:** Okay. Love Whisper Flow. I use it all the time.

**[16:11] Speaker A:** Yeah. I'm a huge dictation fan. Like, um, if you're not dictating, you're just going way too slow, basically. So, it's got a sub agent sort of like looking in the background and sort of peeking at stuff. And then what it's doing is it's quizzing me about the thing we're about to build, right? So, this is essentially a grilling session. and it's going what does the teleprompter read from? When you film today, what's on screen? Now, this stuff is actually it's probably better if I just wait for the explore to finish because it's kind of asking me stuff that it can figure out in the code. When do I use it? What's on screen at once while you're reading? What clutter have you noticed? So, it's asking me sort of like vague questions that I can provide answers to. And we're sort of slowly getting aligned here.

**[16:50] Speaker A:** So, this is actually more tactical, right? This is about how do you get the agent to do what you want it to do? How do you align with the agent before you begin? Because I think what most people do is they just prompt the agent. And they don't they underestimate that there's a communication gap, right, between you and the agent. The agent is just like a developer that you're hiring in order to get the work done. And they've been dropped into this world like the guy from Momento, right, with no memory whatsoever. Just totally blank slate. How the hell am I going to like uh figure out what I need? So it immediately dives into the codebase and asks in in this case asks you good questions because usually what they'll do is they'll just kind of their way through and they'll just sort of say oh yeah sure that

**[17:35] Speaker A:** sounds good and I'll build something like what you want. Whereas if you force it to ask you questions if you try to get over that communication barrier it's much more effective and you're going to get the result that you want instead of the result that you sort of hope for.

**[17:49] Speaker B:** And I I feel that often. um I I won't be thorough enough in the initial ask and I'll get the result of it. Actually, just before this meeting, I I have I built a a tool to help me do interviews and keep track of my documents and I noticed the feature. I didn't ask it to build. It's just there. And I'm like, I kind of like that, but it wasn't in the original design. It just made the choice for me, which I'm like, uh I'm not sure if I like that it did that.

**[18:15] Speaker A:** Exactly. Yeah. And you have this sort of when you're communicating something, you have this like you kind of know some parts of what you want, but maybe you don't know everything you want, right? And maybe it feels clear to you, but it probably isn't that clear to an agent, right? I've been a teacher for uh since I was 21 years old. So, well, that that's 14 years I've been a teacher. I'm quite good at knowing when someone understands what I'm saying or not. Right? But even me, I will try to prompt something. I will get complacent and it will just build me something out of scope or like won't build the thing that I wanted. You know what I mean? So there's always that communication gap and that's not going to go away if the model gets smarter, right? That's just always there because it's the human that's the in the wrong essentially.

**[19:02] Speaker A:** So what we've got now is we've got our grillings come back and it's quizzing me on all of these sources and it's saying, "Okay, it's using my language." So we've got beats and scripts and animatics. Does the script still autoscroll? Is the status area at the top end space etc. So this is kind of like to answer your original question. This is the tactical stuff coming through.

**[19:23] Speaker A:** We are fixing the problem and it's benefiting from this nice glossery that I've been building and working on as I've been working on this app over the last 6 months.

**[19:33] Speaker B:** So when you say grill with docs because I'm very familiar with grill me. I use the grill me skill. I'm not familiar with grill with docs. So you're saying the docs part is this document that you've created

**[19:43] Speaker A:** or is there more docs that we're not seeing?

**[19:45] Speaker B:** I'll show you. So this is my skills repo and if we take a look at the grill me skill. So if we take a look at the grill me skill, it's essentially very short now. It's just call the skill tool with grilling. So it's going to find you this grilling skill and call it. And this is the grilling part of the grill with docs and grill me. Now what grill with docs looks like is it looks like this. It says use grilling but also use this second skill called domain modeling. And domain modeling is this extra docs. It's this glossery and also this extra little line about architectural decision records as well which is something I've added in here. ADRs what they do is they essentially document the stuff that you can't document in code. You know, code is like the current view of all of the decisions that went into building this product, right?

**[20:42] Speaker B:** But it's only the present. It doesn't tell you about the past. And if you don't have like a small record about the past, then the agent will just continually make the same mistakes over and over.

**[20:53] Speaker A:** And so these ADRs, this little list of markdown files, essentially they're quite small. I don't know if I've got any in in this repo. Docs ADR. Yeah, here we go. So these ones here. Uh yeah, I've got what 31 ADRs just knocking about in the repo. And these essentially just track the important decisions I've made that are hard to reverse, expensive to take back. And it means that the agent just has a lot richer context when it goes to build features and grills me.

**[21:21] Speaker B:** Okay. So when you're grilling or when it's grilling you, it will go through those it's instructed to go through those ADRs. It'll go through your glossery. Um, is that something that you had to like within that skill you you have it written in there go to the ADRs, go to the glossery. Is that built into the skill or is that something you added custom for you and this one repo? Um, this is built into the skill and it's also it's basically in every skill I have it says reference the glossery. Use the glossery when you're building specifications. Use it when you're building modules too. So the code will actually be using the same language as when I speak about the code, right? That makes the repo incredibly easy to navigate because everything it just pulls up everything about a course version and the database is aligned.

**[22:04] Speaker B:** The uh uh codebase, the front-end codebase is aligned, everything just reads properly. And it's amazing how many repos you'll see and that I've worked with in my career where the front end will call, let's say we have a refund or something, the front end will call it a reversal. the email that sends will call it a pending chargeback and the code will say something completely different, right? Code will call it a refund in the database. This sort of language, it just makes the app so much harder to understand, so much harder to work on for you and for the agent. And I think we underestimate again these communication barriers between you and the agent. And if you use a shared language, it just feels like the agent is in your brain. You know what I mean? It's just a totally different experience. So when you let's say you initially started this project and you're starting from scratch, are you by hand typing out or are you dictating the glossery and telling it what to make or are you kind of just giving

**[23:04] Speaker B:** the agent a general idea and letting it create the glossery for you. So the cool thing about this is you really like if you're thinking, okay, I want to use this on my project, but I don't I I don't want to have to go through the whole rigma roll of having to set all this up, right? That sounds like a pain in the ass. What you can do is you can just start grilling and it will mint the terms and quiz you about the right terms as you go. And that way you can just sort of slowly build it outwards just focused on the hot spots that you're actually working on. And then it will say, "Okay, would you like to update the code so that it matches the glossery?" And slowly slowly it's like you're peeling like a little window of sanity in your vibe coded slot base, right?

**[23:44] Speaker B:** It's just beautiful. And like as as you do it, it just feels like magic because you just realize, God, I understand what's happening in my project now. Everything reads as if it's like as if I wrote it. So, it's hard to describe without actually walking through and doing it and seeing how this benefits you long term, but it's the first strategic thing that I'd recommend folks do. So, for anyone just like watching this now, and just like by the way, what you said, I'm sure someone's like, "Oh, that sounds awesome. and that's what I need right now for this mess I'm coding. What's the quickest way to apply that? Is it just to go out to your skill repo and just say install or use it? Point your agent in that direction. What's the best way to do it? Yep. You just go to aihero uh.dev/skills and I've got the um essentially a full set of uh documentation on all of these skills.

**[24:35] Speaker B:** And for your next feature, just use grill with docs instead of uh let me just get the screenshot so it's open. What was that?

**[24:43] Speaker A:** What was that? I think that's tracking how much time I spend on Twitter. That's what that was. And it's Guess what, guys? The uh the verdict is not good. Um so this is Grill with Docs. So essentially, you just install the skill and you get started with the skill.

**[24:59] Speaker A:** Okay. Okay. That's that's pretty simple. Okay. That's awesome. Um and by the way, I had the same problem with Twitter. I had to um uninstall it from my phone and I'm now coding a thing that will keep me off Twitter but keep me up to date. So, it's a thing. Anyways, it's a bad bad uh bad addiction.

**[25:18] Speaker B:** So, once we've

**[25:19] Speaker A:** once we've grilled and we get to that point where the the AI understands what we want and it understands the feature, what's next?

**[25:27] Speaker B:** So, you've really got two choices. It depends if the thing you're building is massive. If the thing you're building is uh relatively small and you think it can fit inside the same context window as in the grilling, then you go to the implement skill. And the implement skill is essentially you turn the idea that you've just grilled about into code. Now when I talk about context window, I'm sort of talking about I'm not really talking about the 1 million token context window that Opus has. I consider there to be a smart zone and a dumb zone inside these context windows which is as you add tokens to the context window. The model makes uh dumber and dumber decisions sort of happens slowly as essentially you add tokens and the relationships between the tokens increase quadratically. you get this sort of crazy attention degradation where it's having to hold all this information in its head but also listen to the most important stuff in a room that's getting full of people right it's very very difficult

**[26:31] Speaker B:** task and I don't models are getting better at it but they're still not great at it so I get start getting nervous around 150k tokens right

**[26:40] Speaker A:** really that's early very early right because I I want the good stuff right I want my models making smart decisions and I don't want them like if I like ask a follow-up question, I don't want to be paying again for the um you know 300,000 tokens that I've got in my context window, right? I really like optimizing for small context windows. It keeps things very nimble, keeps things very fast as well because actually latency increases the more tokens you add, you know. So for me, it just feels like a general principle of health keeping my agent in the smart zone and keeping it very very early. Now the actual number I think doesn't matter. It's more about the instinct of context paranoia of keeping things small, keeping the agent uh smart. And so if you feel like your thing you're building is going to be bigger than 150,000 tokens, then you create a spec.

**[27:33] Speaker A:** So you take the conversation that you've just had in Grillwood docs and you turn it into a specification. And this specification lives either in a markdown file or it lives in your GitHub repo as an issue. And then that spec sort of defines where you're going, right? And from there once you've figured out where you're going and you can kind of go, okay, I can check the final product against this specification, then you turn that spec into tickets. And those tickets are the thing that the agent is going to walk through and actually implement one by one. So each ticket is going to be a session. So each ticket gets implements on it and then you can use my code review to do a sort of adversarial review on the thing that was built to check that it matches up against that spec. So that is the whole flow, right?

**[28:19] Speaker A:** So you've got two choices. Either you go down this spec and tickets route or you just implement the thing that you grilled.

**[28:27] Speaker B:** Okay.

**[28:27] Speaker B:** Um I have a few questions on context. How do you what what are your tactics to manage like sometimes when you when you're doing a grill me I can imagine is if you have a big code base it could fill up that context window very quickly. So how do you have sub agents doing I mean we saw a bit the sub agent was doing explorations are using sub agents to do a lot of that to manage the context. So yes, I think I think there there so there's like four things there, right? The first thing is I think people equate big code bases as big code bases always use more context, right, to explore. I don't think that's true. I think that hard to navigate, poorly organized code bases are harder to explore. And you can have a small codebase that's actually hard to navigate, right?

**[29:17] Speaker B:** And you can have large code bases that are easy to navigate. And so we can talk later about how to improve navigability of your codebase because that's again something that we've got here.

**[29:26] Speaker A:** Well, you said there were four things that you do to manage the or some tactics to manage context.

**[29:31] Speaker B:** Yes. And I can't remember what they were.

**[29:35] Speaker A:** Oh no, you compacted your context.

**[29:37] Speaker B:** Oh no, I've compacted at the wrong moment. Damn it. Damn it. What is going on with me? Um I've been filming all day and my brain is mushed. That's That's why

**[29:48] Speaker A:** I completely understand that. That is, by the way, thank you for taking the time to do this interview after filming all day. I know that you spend all your tokens in that those moments.

**[29:57] Speaker B:** Um, now I did have another question on that. So, when you're doing Grill Me,

**[30:02] Speaker A:** uh, which agent are you using? Are you using Fable? Are you using Opus 5.5? What do you trust with that?

**[30:08] Speaker B:** Yeah, I'm using Opus 5.5. And I think I remember one of the points I wanted to make which was I think there's an epidemic of people using too high an effort right I think most folks are using way too high effort either like high x high or max whatever and what that means is when they do an exploration the agent like if you think about effort an effort like producing um let's say a painting right or a animation you know you get opus 5.5 five and you maybe want it on like a higher effort because it's going to put more effort in and produce a better painting or produce a better animation. But if you think about the task of exploration like like is is more effort going to get you a better exploration, you know what I mean? Sure, it might sort of look in more files, but does more files it really just needs to read the right files, you know, like and find the right information and give you that information back.

**[31:05] Speaker B:** So I think people are using way too high efforts to explore their code bases when mostly what I just use for pretty much everything is Opus 5.5 median, right? That's just really

**[31:15] Speaker A:** Yeah. So for me, I'm like and I I think there's still massive confusion on this because I think effort well I want my AI model to do his best every time. I that's that's what what I would expect from a human like do your best always explore that with 110%. Um so I keep mine on extra high.

**[31:33] Speaker B:** Yeah. And I think I think that is a big mistake because what you're doing there is you're just telling it to spend tokens on tasks where it doesn't need to spend tokens and so you end up getting into the dumb zone faster because it's just and and it's going to perform worse because it spent all of its effort on too early a stage. So yeah, Opus 5.5 medium is what I'm on and I'm even thinking of dropping that right to low genuinely. Wow. So, are there any moments when you're specking something out that you feel the need to go to a higher reasoning or higher model?

**[32:04] Speaker A:** Not particularly. I think maybe research tasks are interesting one, especially when it's the web, right? Because the web is very hard to navigate. It's hard to find information in. And so, I think probably high XI is a good example of that. when I'm doing performance testing, I think, or maybe debugging where it needs to try lots and lots of different things, I don't want it to stop early, that's when I might go to a higher effort level. But in practice, usually I just default to medium bis because I I'm thinking about other things and it's not something I'm constantly twiddling or tweaking.

**[32:39] Speaker B:** Gosh, that is crazy. And I'm I'm probably going to switch to medium after this just to see how it feels. Um, and I imagine it's a lot faster and more token efficient. That would be that would be fun. So

**[32:50] Speaker A:** Opus 5.5 is rapid as well. Like it's fast anyway. And so when you reduce the it's it's a very good model, guys. It's a really good model.

**[32:57] Speaker B:** Do you switch back and forth between uh Anthropic and OpenAI?

**[33:02] Speaker A:** I've got an anthropic subscription and I I just haven't really picked up a codeex model or like I haven't had a fiddle around with it. I tend not to minmax between models that much. I tend to think like I I feel I think this is a little bit sort of I I like holding contrary opinions, right? It's it's fun to hold an opinion that most people don't hold. I tend to think that if you keep the model static and you stop the room around you from burning down, you're going to get much better results. In other words, if you fix the environment your agent operates in, there's often so much lowhanging fruit there that people just underestimate basically and they think, "Ah, the new model will fix all my problems, right? Or if I crank it up another effort level, then I'll get better results."

**[33:46] Speaker A:** And sometimes you will, but you'll probably just burn a ton of tokens there. I think instead of waiting for the next model to fix all your problems, why not just fix all your problems? That's my take.

**[33:56] Speaker B:** Interesting. Okay. saying you're saying that going through a method like you have a methodology with your skills and getting your code base organized that will probably fix the problems that you're hoping a new agent that's smart enough to just do that for you would do.

**[34:11] Speaker A:** Yeah, exactly. And we can touch on a skill that does specifically that if you like.

**[34:15] Speaker B:** Yeah. And if you want to keep keep on context.

**[34:18] Speaker A:** Yeah, let's let's stay on context before we um start a new session. We're just using a bunch of AI stuff. It's I'm so AI pilled. That's how I think now. I'm like, hold on, we start a new session because this context is already full.

**[34:29] Speaker A:** And it's so funny how humans are kind of like that. Um, so we we've done we we can take a large idea. If it's a large idea, it'll put it into tickets, which I imagine at that point you're having one orchestrator agent divvy that up between sub aents and they're working that in like work trees. Is that is that what's happening?

**[34:47] Speaker B:** Yeah, exactly. Um there is a skill here called implement spec which basically you pass in the spec that you've just created in a new session and it goes and implements it all with parallel sub aents doing it in work trees merging all back together until you get one mega PR ready for you to implement or ready for you to review.

**[35:04] Speaker A:** Wow. Okay. That's I like that. And I just can't get over the fact that you um you don't AI max because like I do you only have one anthropic subscription because that would surprise me. Just one.

**[35:17] Speaker B:** That is crazy.

**[35:18] Speaker A:** 200x. Yep.

**[35:20] Speaker B:** My goodness. Um, well, I don't I'm not token efficient, so I have three of those bad boys. And I also have probably a couple uh codeex ones, too. But I'm just always testing stuff. But the way you approach this, how simple. Well, it's it's not exactly simple, but it's just very straightforward. It's refreshing.

**[35:40] Speaker A:** Yeah. I'm I think that again it's this sort of slightly wanting to have a different view than everyone else. I was just sort of surprised by how well this works and by how token efficient it is actually. Um I think a lot of people would say it's not token efficient you know like uh sure implementing sub aent like people have different appetites for how many tokens they want to spend and that's fine. Um, but yeah, I think just keeping it relatively simple, having a clear coherent philosophy about the way you want to use AI is important. And I find the smart zone dumb zone thing has been very helpful in clarifying my decision-m and understanding. And this is not my idea, by the way. This is Dex Hy um came up with this who you should have on actually. He's very very clever with this stuff.

**[36:26] Speaker A:** And um yeah, just having that as like a guiding principle has been really nice just to clarify my thinking about how to use it.

**[36:35] Speaker B:** Now, with um with creating those tickets, I'm sure the agent is smart enough to divvy up those tickets to where they're small enough that the sub agent itself won't get into the dumb zone. Correct.

**[36:48] Speaker A:** Yes. They're not amazing at it, but yeah, they do a good enough job. Um, and I think of it as having like if you imagine each ticket should be around 150,000 tokens, then that's about right.

**[36:59] Speaker B:** Okay. How do you keep track of the tickets that's created? I guess it creates it inside the repo, right? So, it creates worked on

**[37:08] Speaker A:** just as GitHub issues basically. So, you can just go on the GitHub issues. They're tracked as sub issues underneath each spec. And so, then you can just see the spec being um completed as it's being worked through.

**[37:18] Speaker B:** Okay. So then after after it all completes and the work trees are finished and it's it's merging all the code, what's next?

**[37:27] Speaker A:** Yeah. So I do two things. So what we do is we go on a code review. So the implement spec actually calls code review on your um the code that it's done. And here two things happen. So it does a standards review and a spec review. So spec review is it compares the code against the original spec and it checks whether it did the right thing right did it build the thing that I wanted or has it gone over scope or under scope and then with standards it reads the standards files that you have in your repo so let's say you have a a codingstandards.mmd file and I can pull one up for you if you like

**[38:05] Speaker B:** these coding standards.mmd this is full of information on how I want my applications to be built right so I use effect which is a very cool TypeScript library and it has a ton of stuff in here for all the information I want to review. So every any in Typescript is a leak. Uh specific stuff about course versions, you know, this is really dense stuff. I think a lot of people would have this in their agents.mmd file, right? I imagine maybe is this something you do as well?

**[38:38] Speaker A:** You know what's funny is I don't even pay attention to that. I trust the agent with it.

**[38:44] Speaker B:** Yep. Right. You just think, okay, I'm not worrying about these steering files or not worrying about what the agent is reading or thinking about the agent's environment.

**[38:52] Speaker A:** Yeah. I'm more like I I I definitely tell my agent, I want to have a standard, but I want you to create the standard for me and I don't want to have to look at it.

**[39:00] Speaker B:** Got you. Yeah. I think that's um I would probably describe that as vibe coding. I think I think that's vibe coding, right? Because it's not really caring about, you know, I want you to be good, but I don't care how you're good, you know?

**[39:14] Speaker A:** Yeah. It's it's like that that meme I or some kind of Tik Tok I saw a while back. It's just like

**[39:19] Speaker B:** think faster. Deep research. Do it. Do just be smart. Make it happen. Like it's just making wishes and and um

**[39:26] Speaker A:** yeah, ultra ultra think you know um

**[39:28] Speaker B:** ultra think ultra think do it right until you're um you know or I'll fire you or something. You know what I mean? Just like so that is what we're that's the second axis that we're comparing on. Is it built correct according to my coding standards? because I sort of assume that when my agents implement something, they're going to get stuff wrong. And for me, that's fine because I've got a code review step that goes again and does this adversarial review and checks it against the standards. And so once that's done, then I'll go and human review, right? And I don't do this for everything. I do it for some things, for very important work. And if I was like being professionally paid to like build an application, then I would probably do it for most things

**[40:09] Speaker A:** really. So describe to me what the human review looks like. Is it you actually in the code looking at I mean is it line by line? Is it just like an overview or using an agent to help you look at it?

**[40:20] Speaker B:** Yeah. So what I do is I have a PR skill which is I think in reference skills here which basically builds me a PR body that does a couple of things. It's this is a nice skill by the way because you can just install this and the agent will call it. It's unlike my other skills. has just sort of improved your PRs and it does a few things. It gives me like a sort of visual summary of the thing that's being built. It gives me evidence that it's working. So, it has to take like a screenshot or have like execution based evidence. And then it tells me the merge danger. What is the danger of me merging this? Whether it's a one-way door or a two-way door. So, if it's a one-way door, then it's a door we can't walk back through, right? we merge it and then there's data loss or like you know an email gets sent out to 100,000 people where if it's a two-way door then we can merge it and come back

**[41:11] Speaker A:** and then also it's blast radius too so whether um whether if it goes wrong it's going to be a big bad thing or a small thing and so I use this merge danger as basically like do I need to review this because if it's a small blast radius and it's a two-way door then I probably don't need to like review it that hard you know what I mean I can probably just like test it in production So, wherever if it's a one-way door with a big blast radius, you better believe I'm reviewing not necessarily line by line, but I'm looking at um I'm trying to break it. So, that's kind of what I do for human review. And I like human review because it's not only a chance to make sure the stuff I'm shipping is high quality, but I then take the stuff that I'm saying in human review and I pull that back into my

**[41:57] Speaker A:** coding standards into my uh environments that my agents in. Right? So I start thinking, how can I improve my environment so I never have to write this comment again? And that's what I'm thinking when I'm reviewing.

**[42:10] Speaker B:** Now is that like an automatic thing? So when you're so let's say you're reviewing it human review you're looking at the code what is your method for giving so I imagine you're not going to fix it yourself you'd probably just tell the agent to fix it so it has that context um is it automatic to take what you're saying and add that to your your your coding standards or do you have to tell it that to actually initiate the skill there is a skill for that so we have a retro skill so this looks back on a session looks back on a PR and suggests improvement ments based on what the agent did, right? So, it's another look back on the agent session, on your review comments, on everything that just happened. Let's improve it next time.

**[42:51] Speaker A:** M okay. Okay. And I'm sure we'll get to this because it's more of an architectural and design question, but like your coding standards, is that just something that you as a software engineer with that background just know what you want to have? And how would someone who doesn't have that background even go about doing that?

**[43:09] Speaker B:** Yeah. Um, this is this is where the strategic stuff comes in, right? Because this is I don't want this to happen next time. I'm thinking about the long view. And you need to be able to recognize what good code bases and bad code bases look like. And that's really hard. I like I'm I'm we want to dive into that now because we totally can. Um, let's wait a moment because I and I'm like I'm like yes, but also no because I know we we probably want to keep going through this the different skills we have as we're adding features because I I do have a question like once we once we review it and it looks good. Let's say it's a two-way door. Blast radius is small. It's it's an easy thing to deploy. Um, what's next? Do do you deploy it? Does your agent deploy it?

**[43:56] Speaker B:** What's your approach? I mean what's next is I press merge or I say okay if there's a bunch of them I just say okay guys merge all these five PRs or something and you figure out the right order you merge them in together and then we're kind of done right you know we've done the loop and now we're back to wanting to um ship some more features either do another grilling session or just like plain ship something. Um, so that is the loop. We've covered the entirety of the main flow where you grill with something, you either then to spec and tickets, implement it, code review, and then retro so that it's better next time. So I think that that's probably the the part where most people stop cuz anyone can go Matt PCO's a smart dude. He's got skills that will make my agent smarter.

**[44:39] Speaker B:** I'm just going to copy paste and go. But the next part we're going to talk about is the actual thing the thinking that needs us to understand architecture design and a little bit of coding. So walk me through that.

**[44:52] Speaker B:** Okay. So before we think about we like we've got the tactical stuff kind of done right. We now know how day-to-day we're going to be um shipping code. But how do you then take the long view and think how do I um improve this over time and get my agents to a point where I can trust them? And the point of this is that uh Lauren Tan um who goes by Potato, who works at Grockbot, who's uh kind of famous now for shipping like 2,500 PRs a month or something, she talks about how do you essentially scale up your trust in your agents? Because the more you can trust your agents, you sort of walk up this trust ladder. And if you don't really trust your agents, then you're never going to be able to scale beyond like four agents at once, you know, because you're going to be watching them everything they do, checking all of their work,

**[45:44] Speaker B:** human reviewing every part of it. And even if you walk through this whole flow, you're still going to be doing that, right? So her question is, if you can go up the trust ladder and you can trust maybe some PRs to be merged without human review, you know, the two-way doors, how are you going to get your agents to show you evidence that they've done their work? How are you going to constrain them so that they do better work every time? And if you've got essentially a really great environment for those agents to operate in, then you can start trusting them to levels where you can have hundreds of agents operating at the same time comfortably. and trust that they're doing good work. And so all of this is about trust. And what you need is a codebase that's a good codebase. And if you read like the classics that I've got on my shelf, they tend to converge around one definition of a good codebase, which is a codebase that's easy to make changes in.

**[46:39] Speaker B:** A codebase where if you make a change, it's probably not going to screw anything up. And that's really hard to do actually because or actually I don't know if it's necessarily hard to do but you have to care about that in order to make your codebase easy to change. And so what that means for me is that you need a ton of feedback loops so that the agent can grade its own work and can verify that what it has done is good. And you asked me before about effort. I would say that the point where I really want a high effort level is when it's verifying its own work. When it's checking that what it's done actually functions and it's clicking around a real application where it's running like performance traces on its code to make sure it hasn't degraded anything, that's where I want it because if I

**[47:27] Speaker B:** can trust that the agent has done that work and has verified its own stuff and that the codebase is easy to make changes in, then that is stuff I can just like merge without thinking about it. I can just go, "Oh yeah, that looks good. merge it. You know, I don't have to worry about the code.

**[47:42] Speaker A:** Are you there? Like, do you trust your agents right now?

**[47:46] Speaker B:** I'm in an environment where I can, right? I can absolutely because I'm not working on a medical application. I'm not working on a finance application. My domain is I'm building personal software for myself, right? So, I have been in those situations before. I've worked on, you know, banking finance applications. And in those situations, I would not or or I would be looking very very carefully at at certainly the one-way doors, right? I would probably be asking my agents to verify everything from a security point of view really heavily as well. I would be burning a lot of tokens on verification so that I could get to the point where I trusted them.

**[48:24] Speaker A:** So, what are some examples of feedback loops you have right now that build your trust in your agents?

**[48:31] Speaker B:** Great question. So there are a ton of them. And by the way, um I have this really cool resource. It's called the AI coding dictionary. I've not really talked about it very much. And it's essentially every term that I use is somewhere on this graph, right? So we have uh model providers, context windows, and all of them have a definition associated with them. We have uh somewhere in here will be automated checks. And so automated checks are essentially what I'm about to talk about which is strict typing um you know a fast test suite and a bunch of other stuff. So the main automated and this is this is free by the way you just you know access it there's a GitHub repo if you want to point your agents at it. Very useful for just like this is kind of like the glossery that I showed you earlier but applied to AI coding right this is where I got obsessed with it.

**[49:21] Speaker B:** So all of my resources use the same language. Now, automated checks essentially you want strong types. So, you want to be using things like TypeScript and not JavaScript because types tell your agent um very very quickly that it's made a mistake. Then you want tests. So, you want actual runtime tests that verify that it's doing what it thinks it should be doing at runtime and that you don't break anything. You want things like llinters as well that uh for those who don't know a llinter is essentially a program that checks your code to make sure that it looks right that you can do all sorts of things with it like check that you're using the right functions check that you're importing from the right modules that you're not using bad patterns that the authors of the framework know are bad and are trying to protect you against.

**[50:10] Speaker B:** So llinters are very important too and what you want is to get the most value out of those you can. So you want to use like types really effectively. This is why I have let's say a this little rule inside my coding standards here says don't use the any type in Typescript because I know as a developer that if you use the any type it's actually a cheat. So it's trying to cheat around the type system and it's going to reduce the quality of my type checking further down. So I am trying to improve those automated checks so that they work better and catch more errors next time. Interesting. Okay. Now these all these automated checks the llinter the um the CI the testing is this something that anyone can easily implement? What's the process for that? You just you just have to care, right?

**[51:04] Speaker B:** You just tell your agent about them. You say, "I want to constrain my application more. I want you to find harsh lint rules." And this is something that retro does as well. So what retro will do is it will say, "Okay, we we found like a comment in um the PR um and it tries to find ways that it can prevent it deterministically with an automated check next time." So every time it sort of ratchets up the power of these automated checks every time you run retro or find something. And so eventually you get to the point where the agent is so boxed in. They're in their straight jacket, right? They literally cannot make a mistake. And what you worry about then is of course improving the speed of those checks to make sure that you can still ship work. But agents are really good at that as well.

**[51:50] Speaker B:** So all of these individual parts agents are good at. They're good at finding lint rules to constrain themselves. They're good at um making those tests run really quickly. It's just you have to care. You have to tell them to do that. And if they if they don't know to do it, then they won't care about it either.

**[52:07] Speaker A:** Is that a skill you have?

**[52:10] Speaker B:** I'm thinking about building a skill in this direction. Actually, I do have a skill um which we can talk about in a minute that sort of prompts the agent to improve its own environment a bit. But essentially, this is retro. That's what retro does is the more often you run retro, the more sessions you run it on, um, the better your codebase is going to be.

**[52:31] Speaker A:** Okay.

**[52:32] Speaker A:** Okay. So, let's say let's say we've got the average Joe. They have an idea for an application. Let's say it's a website that, I don't know, makes ordering coffee and tea better and easier. You can find the cheapest tea and coffee in the world. Doesn't matter what the idea is. How would they approach that idea? So, obviously, Cloud Code is your favorite. I think it's it's very good too. It's one of the best harnesses. So cloud code. Um would you say they need something like VS Code or can they just stay in the terminal? What's your what's your preference on that?

**[53:02] Speaker B:** I would recommend VS Code. It's nice to be able to easily access the code. I don't always use it to like read code or think about code. I would say that what what my stack is and it's very approachable like it's free is GitHub is VS Code is Git obviously and Claude code or whatever agent you like it doesn't really matter what the agent is to be honest as long as it can use skills and it can use um uh my skills u then you're good to go and pretty much every harness out there is you know can use skills because they're a common standard. Okay. So, doesn't matter what the what the harness is really. Um, and I think most of them use sub agents. Like everything's kind of the same now. They've all copied each other. Uh, so once they have that set up, what are the things they have?

**[53:50] Speaker B:** So, when we get to the strategic thinking, when they're building their app, obviously they'll they'll start talking with their AI. Do you have skills that ensure that they do that? Is that what the grill me is for? Like, is that does that ensure they have that strategic thinking they need, or is there something more they need to know? So it is baked into different parts of the process. So let's say when you call to spec, it's going to ask you sort of what shape of modules you want, which might be a little too technical for some people, but just sort of keeps you in the code a little bit. I don't necessarily think you need like a like full awareness all the time of everything that's happening, right? You can people talk about like software factories and they talk about a dark factory, right? which is kind of like, you know, you have your factory, your agents are working in there, and you never turn the lights on, right?

**[54:39] Speaker B:** You have no idea what's going on. I don't like the dark factory. I do think you need to look in there and care, but you can have little dimmer switches, right, for different rooms and stuff. There are rooms in your codebase that you never really need to walk into, right? You can just sort of have a little peek in there. And I think one thing we should talk about before we like go here is that there is another skill that I think really helps. So, I sort of talked earlier about

**[55:05] Speaker A:** um wanting to get the most out of your automated checks.

**[55:09] Speaker B:** Mhm.

**[55:09] Speaker A:** And when you one thing that I think people really underestimate is that when you write tests for your application, so specifically the things that test your application at runtime that actually run parts of your code and like verify that they work. Tests are really hard. They're really hard to get right. And this is this has been true, you know, before AI. The reason tests are hard is it's really easy to write a test that really doesn't verify very much. It can like, you know, you look at like a line of code and it just says um the the amount of characters you can have in a tweet is 240 or something. I can't remember what the actual number is, but let's say 240.

**[55:51] Speaker B:** And then you'll have a test that just checks that number and checks that that number is 240. Right? The test is just repeating the implementation. It's not actually like what you want from your tests is you want a big chunk of code that I'm going to call a module and you want that module to basically be hidden from the tests. The stuff inside the module is hidden from the tests because that means it can just test it via a very narrow little um sort of entry point to that module. And it means that you can change everything inside that module without needing to alter the tests. Because if I like have a single line of code that's tied to a single test, then every time I change that line of code or I restructure it or do something with it, then that test will have to

**[56:34] Speaker B:** change as well. And it's just sort of endless crappy churn. Whereas if I have these big what I call deep, what what John Asterout calls deep modules, then you can actually sort of turn the lights off inside that module. You don't have to care about what's in there. As long as the tests happen from outside and everything sort of seems to work, then it's probably going to be fine. And I have a skill that can basically turn your codebase into this shape. It's called improve codebase architecture. So you can fire this off at any repo and it will give you a visual report on the bad stuff that it finds and it will suggest improvements for making it better and then you can take the result of that and turn that into a spare tickets and run it through the normal loop. Ah, so using this skill, it will it obviously will show you the the holes and the errors and all the bad things inside your your codebase, but it'll also help you build those those tests.

**[57:29] Speaker B:** And are we talking about unit tests? Is that the same thing?

**[57:32] Speaker A:** Yeah, unit tests. Exactly.

**[57:34] Speaker B:** Okay. Which I I as I was learning coding before AI, I never got to that point, but I heard it was always the worst part of coding, just creating really good tests.

**[57:42] Speaker A:** Totally. It's really really hard. But agents agents make it easy to type out tests, but they don't necessarily think about structuring the codebase so that it's easy to change, right? So that those tests actually catch things that are important. It's very easy to write tiny tiny little tests when what you need are tests that actually like take out huge chunks of the application and put it all under test at once. So that's what this skill does.

**[58:10] Speaker B:** Okay. Okay. And that I think that would be a massive help for a lot of people. I mean, I'm going to run this skill on a few of my code bases right after this interview just to see what happens. Um, okay. So, we we've we can produce good tests and that's a good place for us to go to um to make sure our code base is is healthy and and it's um it's and you said it was we could be able to dim the the lights or turn lights off on a module as long as the tests are really good, right?

**[58:39] Speaker A:** Yep, that's right. you have like this feeling of um

**[58:44] Speaker B:** I don't know when when you work on a codebase that's been vibe coded I always feel this terror right this I don't know what's in there all right and I think it's bad and what you start to feel is right how will I know if something goes wrong right will I have to eventually like look at this code and review this code like how am I going to get to that whereas if you have this if you have improved codebase architecture and your codebase starting to be put into these big beautiful modules. You can go, okay, I understand the shape of this and my app understands how to use these modules as well, how to like um leverage them and how to call their functions and things like this. And you have these lovely big chunks of stuff that you don't need to review that's all using your domain language, all using your glossery terms and stuff.

**[59:32] Speaker B:** So, you know exactly what's going on in there. and you realize, okay, I can start thinking of my app's codebase in these big chunks, right? In like, okay, that's the bit where we do authentication, that's the bit where we do um transcripts, that's the bit where like the whole video editor interaction lives in one big chunk and it's all testable. So, when once you have that, you start realizing, okay, cool. I don't need to worry that much about this codebase because it's structured in a way where it's more robust.

**[1:00:00] Speaker A:** Hey, real quick, let's take a coffee break, you and me.

**[1:00:04] Speaker B:** This coffee break is sponsored by Coveron. Look at Zach. We talk a lot about AI on this channel. I mean, everyone's talking a lot about AI. And while AI has made you pretty good at your job, you know who else has made pretty good at their jobs? Scammers. They can clone a voice, write a perfect fishing email, spin up a fake fake website in minutes, actually maybe seconds. And they can do that at scale. And they're not just coming after you. They're coming after your family, your parents, your kids, everybody. And that's where Coveron comes in. Their family plan watches the dark web for you because that's where all that stuff ends up. So, they're watching the dark web and they will alert you when you or anyone in your family has like a new account set up. And if something does slip through, you got real people you can contact for help.

**[1:00:40] Speaker B:** They'll help you clean it up. Plus, up to $2 million for identity theft and up to 100 grand for online fraud, cyber extortion, and home title fraud. One scam can cost you everything and they're moving fast. Protect yourself right now. Get 71% off this Black Friday deal. Coveron.com/chuckoveron. That's coveron.com/chuckcoveron.

**[1:01:01] Speaker B:** Okay.

**[1:01:02] Speaker B:** So, do you think we're at a place now where we can get to the how do you structure your codebase? How do you structure your project? Yes. I think like there's no one like genius way to do it. Essentially, you use these deep modules. You if you have I what I I really want to actually just run this and um because it's very very easy to run, right? because we can just literally go claude and then I'm just going to run improve codebase architecture. And what this does is it's going to um pull in the codebase design skill which sort of um if you want to just read that that's got all of my uh like how I like to design code bases in there and it's finding the hotspots. So it's going to find my recent commits and look inside the repo to uh explore that and explore what might need to be improved.

**[1:01:53] Speaker B:** And then we're gonna get a HTML report back of the things that it wants to change. So once this is done, I'll be able to like exactly tell you how to do it. There is I think what people need to get is there's no one perfect codebase, right? All you can do is just improve it over time and get it better over time. And what I do is I have a cron job that runs on each of my repos where once a day it will run improve codebase architecture and it will give me a top suggestion back and then it will go and make a pull request based on improving that thing. And because those are two-way doors then I don't really need to worry about it. I just know that it's making decent improvements and slowly pulling the code into where it needs to be.

**[1:02:36] Speaker B:** And so you're essentially just trying to fight back against the wave of slop, right? because agents will make tactical mistakes and strategic mistakes and you just need to constantly be pushing it to this position where they use these deep modules.

**[1:02:51] Speaker A:** Uh when you have these cron jobs running, do you trust it enough just to fix things without your approval?

**[1:03:01] Speaker B:** Yeah, I what I do is I do sampling, right? I will just sort of check in every five PRs or so. And this this works for my application because it's again not finance, not medical.

**[1:03:11] Speaker A:** So I will do sampling. I will just sort of check that the thing is running. I will occasionally um retro it. So just say retro look at the last five of these and see if they're actually reasonable. See if they make sense. See how we can improve them next time. And so yeah, basically I do.

**[1:03:27] Speaker B:** Hm. Interesting. Now do you do you use like the Cloud Code app on your phone? Do you do you do things remotely? Do you text it? Use Telegram? What what's your stack for that?

**[1:03:38] Speaker A:** So, I have been like in all sorts of like I've tried all sorts of setups basically. I've like my recent one is I liter I literally tore it down today which I built a uh a custom Discord bot for myself. Kind of like my own Hermes basically. I put it up in the cloud. I was like texting from my phone and stuff. I think phones are cigarettes basically. Phones are poison. Um so I tried to make my phone as boring as possible. So I'd sort of go away from that. I didn't want to do it anymore. So right now, as of now, I'm just using claude code and using um GitHub actions for some scheduled jobs as well. So this is an open source repo. GitHub actions allow you to run cron jobs and I just run claude inside the GitHub action and it updates and creates pull requests for me.

**[1:04:19] Speaker A:** And

**[1:04:20] Speaker B:** agents know GitHub actions really well. It's actually free for open source repositories and so it's a really good option for me.

**[1:04:27] Speaker A:** Okay. I I love what you said that phones are poison. And what's funny is I I um I have it to where I can use iMessage for my agent right now and it's I was just thinking this morning as I was on my walk. I'm like this is so fun just being able to text my agent to do whatever I wanted to do and it it does feel freeing. So I I find it interesting that you're like the opposite. You're like no phones are poison. I want to make my phone as boring as possible. Why?

**[1:04:54] Speaker B:** Well, because I had that too, right? I would have Whisper Flow running on my phone. I would be chatting to it on Discord as I sort of went, you know, for my walk and stuff. Um, but this is more, this is just a personal thing really. Like I think we'll look back on this generation and think of it in the way that we thought about cigarettes in the 50s, you know, like you know, we're giving, you know, like phones to 13-year-old kids and stuff, you know, like it's it's miserable. Like these kids like I it's just, you know, life is there to be lived, you I I I I just I don't having this constant access to information and uh especially the social side of it as well and this constant hankering of people wanting to pull you in and scroll basically just scroll scroll scroll scroll a bit more.

**[1:05:41] Speaker B:** I just hate it. I'm with you there. And I I I I like the idea of keeping my agents close to me, being able to text them. But like I said, like just this past weekend, I deleted Twitter. I deleted or X I deleted Tik Tok and YouTube and everything off my phone because it was sucking that that time away

**[1:05:59] Speaker A:** and it's and it's so funny when you take that stuff away you notice you kind of have that itch like

**[1:06:04] Speaker B:** I'm bored for these 3 seconds I have to wait let me go check no I don't I can't I don't have it and you you feel that urge start to like it's and it's nasty. I've even gone further which is I've uh removed the web browser and I've removed the email from my phone as well which is apparently something you can do on Android and so it is as boring as possible. And what I noticed was I would hope that or I hoped that when I did that I would get all this extra inspiration. I'd feel so much more energy. I would like become this whole new person and then nothing happened. Right? Essentially nothing h nothing rushed in to fill that gap. You know what I mean? It turns out that yeah, these things are really addictive and you you know I've been trying to read more books, I guess, but it nothing is as good or feels as good as checking Tik Tok, right?

**[1:06:52] Speaker B:** Or checking Twitter. So, you just have to kind of live with that.

**[1:06:57] Speaker A:** It's like a you're you're talking like a former addict or something like

**[1:07:01] Speaker B:** I'm always a drug addict and there's nothing better than that, but it's ruining my life.

**[1:07:04] Speaker A:** Absolutely.

**[1:07:05] Speaker B:** Uh so, what is this? Well, this is the report that we just got back from uh improved codebase architecture. So, what we're essentially seeing here is a before and after of each of the um modules. So, what we have is a problem. Submit and duplicate course contain 150 near identical lines. So, there's some duplicated code inside our repo. And what it's basically proposing is instead of this horrible sort of setup where we have a bunch of shallow thin modules on the left hand side, we say, okay, all of these different parts of our application are all going to rely on a single deep module and we can then test that module. And so this one feels like a like a total win for me. So this is cool, but honestly I think and I speak for myself as well as probably my audience and many people watching.

**[1:07:56] Speaker B:** I'm like, um, I see that I found stuff and it's very interesting, but also I probably have to ask AI about a lot of these things. Like, what does that mean? What does that mean? Why did you show me that? What is this?

**[1:08:07] Speaker A:** No, absolutely. Absolutely. So, this kind of maybe goes into another section of our our conversation, but um I'll ask it now and maybe you can tell me where we should ask or answer it. But for people who are wanting to get into this world and what it means to be a software developer, what is that knowledge that you still need to learn? What's the thing? Because obviously it's not it's not tactical coding anymore, but I look at this and I'm like, I don't know this, so I probably should learn this. What What is it?

**[1:08:38] Speaker A:** So, there's a skill for that. Um, so, uh, do you have a t-shirt with that? Like, that should be a t-shirt.

**[1:08:45] Speaker B:** I have a teach skill, right? I'm a teacher. I was bored on the tube one day and I like I thought, why don't I just write down everything that I know about teaching um, and turn that into a skill. And what I would say is that let's say you have improved codebase architecture. You get a report and you look at the report and you think, I can't read that. I don't understand what's going on there. I don't understand the terms it's using. Um, I've thought very carefully about the terms that I've I've used in the skill so that they point out to um books and they point out to well-known methodologies. For instance, let me just I've got a big pile of books next to me. This is one of the books that I recommend called uh working effectively with legacy code by Michael Feathers.

**[1:09:24] Speaker B:** Um, wonderful wonderful book. Teaches a lot of this stuff. And what teach can do is it you basically just say you pass it the report you've just received. you say, "I don't understand this. Teach me about this." And it goes and finds a like a workspace on its own. It keeps track of what you know and then it quizzes you and builds these again HTML lessons so that you learn things slowly. So it's essentially a build your own course for uh whatever you want. So it taught me how to um do a Rubik's cube actually. So this was how I tested it and uh I can now do a Rubik's cube which is wonderful. Um, but you can also I've tried it out by teaching strategic programming as well and it's really really good at it because my um these reviews here they're basically like they use a common language.

**[1:10:13] Speaker B:** So they talk about locality. So you probably have no idea what locality is. A lot of software developers don't know what locality is. It means how if I make a change to a piece of code, how likely am I that all of the changes are going to be in the same location? In other words, are all of the related pieces of code together in one file or in a couple of files? So, locality is good. You want locality? And yeah, like you just basically give it this and you say, I want to understand this. Teach me about it. And then it's going to do a great job. So, you're saying, which by the way, that teach me skill is such a fun idea. I love that. So, you're saying that it's important for us to know all this. um at what point is it not important for us to know this?

**[1:11:00] Speaker B:** Like are the models going to get so good to where it doesn't matter? So it comes down to caring again, right? And all you need to know is you need to know enough strategic programming to be dangerous and to know that it's effective and that improves things over time, right? because the models are still not going to care about it, right? I maybe there's a world in which they are um prompted to do this. And I I've been thinking about this myself as well, but for now it seems to me that people who are really good at something are going to be able to get models to be really good at that thing, right? M

**[1:11:44] Speaker A:** so engineers tend to produce better um products than non-engineers right now because they have the domain expertise they know what to ask for they have the right language right um you know you might say uh what's a good example let's say that you have a problem in your application where the you have some sort of flashing stuff coming in when you load the app right it sort of shifts around in terms of layouts right and I know what would cause that. I would say um fix the hydration error on the homepage, right? Or fix the uh layout shift on the homepage. Whereas someone else might need to say, okay, the when I load the layout page or the homepage, um it loads and then it shifts everything around. It just allows me to communicate more effectively and prompt the agent in a better way because I know the domain language because I'm an expert in it and I've seen that kind of thing before and I can communicate

**[1:12:43] Speaker A:** what I want much much better.

**[1:12:47] Speaker B:** H that does make sense. Um and I'm sure I'm sure you've seen this term uh the bitter pill engineering idea.

**[1:12:55] Speaker A:** Uh bitter lesson

**[1:12:56] Speaker B:** or bitter lesson. Yeah, I I forget it's it's then been used interchangeably, but the idea that all this all the um architecture, all the the the straight jacketing we're doing um will be replaced by better, smarter models and we just need to kind of get out of their way because they might know better than us how to architecture a given thing. But you're saying that it's it's the caring that matters the most.

**[1:13:20] Speaker A:** It's the caring, right? And I always say like I'm not a pundit, right? I have no idea where things are going. you know, I'm just in ox like rural Oxfordshire. I'm not in Silicon Valley. I don't know anything. Um I'm my job is not to predict the future. My job is to tell you how to get these things working now. And they're very effective now. Um but yeah, I and I think there probably is some sort of harness, some way of doing this that will make the agents care, right? Because you can get the agents to care. It's just you need to care yourself. So, that's something I've been thinking about and working on too is how do you get agents to think strategically? And I think that probably is something you can do in the harness, just not um it doesn't have to be in the model.

**[1:14:04] Speaker A:** But for now, this is what I consider the state-of-the-art way to do this.

**[1:14:10] Speaker B:** Okay. And then once you've I think what a lot of people don't understand how to do right now is they don't understand the architecture or rather the infrastructure like where to actually put this app they're building um do they use a database what type of database um do they put it on AWS or Google cloud like all these things are big things that normally are done by DevOps engineers or or software engineers who have that background. Now, how should someone approach that? Especially if it's someone who like only has done vibe coding. Let's say they they're watching your course and they're coming into it. Do they need to learn all that stuff or can they just ask the agent to do it? And do you have skills that help with that? I don't have skills that help with that. And I would say we don't really need skills to help with that.

**[1:15:01] Speaker B:** What's a little bit of a history lesson which is over the last 10 or 20 years DevOps has moved from need like being something that you needed a degree in to like figure out how to do you know like uh hosting uh self-hosting your own Linux box or something and doing really complicated stuff or stuff that could really go wrong and really bite you into a set of products that have been built by Google cloud by AWS um especially you know serverless platforms if you want to do some googling that really take a lot of that stress away from you and has resulted in products like Versel for instance who I used to work for and um Netlefi and all this stuff that basically take all the pain away from you right and what you really need to do is just figure out where your data is going to live whether it's going to be

**[1:15:49] Speaker B:** in a database you should probably just use like a Postgress database if you don't know what you're doing and once you've got that and there are many services that will host and manage your Postgress database for you planet scale Superbase. Once you've got your data, you can basically deploy your app anywhere. You know, just Netleify, Versel, whatever you want, and it'll be fine. You know, like this has gotten so much easier that an agent really can just do it for you and it will be good. So, as long as you're running some security checks and you're doing relatively regular security reviews, which agents are also pretty good at, you'll be fine. It's a lot easier, just like coding. It's a lot easier than most people think it is.

**[1:16:32] Speaker A:** Yeah. And I can speak to that. Like I I'm very much a home labber. I've got Proxmox and all kinds of things in my environment. But as soon as I felt comfortable enough to give the keys over to my agent, I can simply text him and go, "Hey, I want to deploy this app, make a new VM, make it happen, just do all the things. Give it an IP address, give it a domain name, and boom, it just does it." And it's magic. It feels like magic. But I did need to have a bit of that domain expertise to even know how to tell it to do that and to give it those keys. Um, but you're saying that a lot of the DevOps things um,

**[1:17:08] Speaker B:** so things like databases and and and Versell hosting now

**[1:17:12] Speaker A:** they've abstracted that away to where you don't really have to know it. Your agent can do it. Do you is that where you host your stuff? Is it is it Versel?

**[1:17:19] Speaker B:** Yeah, I'm on Versell. Yeah. M

**[1:17:21] Speaker A:** like I would say just use the thing that's easiest to use basically especially when you're getting started. I wouldn't worry about you know like going into AWS manually or figuring out all that stuff. There's stuff you can like there's foot guns there right which is why these companies like Versel exist. So like they just sort of make that easier and you don't have to worry about you know manually deploying or anything. You just push to your GitHub repo and it deploys for you. Um it really is very very simple. Um, you can even use something like GitHub pages or something. And all of this stuff is even when it comes to like domains and um, uh, DNS records and things like that. All of that is really easy for agents to figure out information on. And often um, these sites like, you know, Cloudflare as well.

**[1:18:07] Speaker A:** Um, you know, again, it's just something you have to care about. You just basically say to your agent, make this deploy as good as possible. Um, give me everything I might need in terms of security. um uh distributed denial of service attacks, DOS attacks. Um try to make it secure and just give me the basic level of what I need. And agents are really good at that. Time for a quick coffee break. I want to talk to you about something. You've probably seen one of these before. A video of a celebrity or a CEO giving away some kind of scammy thing. Actually, I just saw that with the Roadster announcement. You know, Elon's flying car. I was trying to find the live stream and I actually just found a scammer live stream that had a fake Elon sitting there talking. To me, it looked fake, but for many people, it would not.

**[1:18:46] Speaker A:** And there were like 30,000 people watching that stream, and he was pumping some crypto scam, but it looks stinking real. Voice, face, everything. Like, I was showing it to my family. They're like, "Oh, are you sure? Are you sure it's not him?" It's a deep fake. Scammers are literally using them all the time. And in a survey of 7,000 people, that's their biggest concern. Deep fake scams are so bad now, and one in seven have claimed they've fallen for one. So, here are some red flags you should look for. when the lips are a little bit off from the words. They have some weird blinking and an offer that's like too urgent or too true. I mean, come on. Most of these announcements we see from founders are like pre-order in 3 months. They're not like buy this right now. So, when you see that, pause, don't click, don't send any money, don't share it, and then check it cuz Bit Defender has a free app called Real Check.

**[1:19:27] Speaker A:** You can drop in a link from Tik Tok, YouTube, Instagram, Facebook X, upload the clip, and it tells you if the video looks altered and how likely it is to be a scam. And honestly, not every AI video is a scam. Real Check will help you discern which ones are. Now, you may be thinking, "Well, Chuck, I don't get fooled by these scams." Well, what about your mom and your grandma and your dad and your brother and your sister? Do they know enough to spot these things? Give them a tool that will help them do it. Run suspicious clips through Bit Defender Realcheck to see if it's a deep fake meant to scam you before you click or send money or share it. Links in the description. Bitdefend.me/realchecknc. That's bitdefend.me/realchecknc. And it's free. So like what do you have to lose? Just try it. What do you do for security?

**[1:20:09] Speaker A:** Um because I know that that's one thing everyone actually most people don't think about but they should is all these AI agents are just making things very quickly. They want to make it work and that's the primary objective. But then security is a whole realm. Do you have skills for security? No. I'm the wrong person to ask because um no

**[1:20:26] Speaker B:** the project the projects I work on are personal software essentially and I have a platform team that handles my site where we might have some security concerns. Uh so no I don't don't think about it that much but I know it's a concern. What I would recommend is if you are interested in security is to add something to code review so that it does instead of just um to access instead of just thinking about standards and spec you also do a security review and many harnesses have a built-in security review um skill. So that's what I recommend. H have you had any security issues with anything you've coded

**[1:21:02] Speaker A:** specifically with?

**[1:21:05] Speaker B:** No, but I haven't had those cons. I I I've definitely screwed up in many many ways, but I don't think I've ever uh especially preai, but I don't think I've ever caused a security issue. I don't think.

**[1:21:22] Speaker A:** That's good. That's good. We can trust you now. No, I'm just kidding. Um, now with your with your skills, how do you make sure what what's your method for making sure the skills are good? Because, you know, anyone can make a skill, but how do you test them? How do you make sure they're they're effective?

**[1:21:42] Speaker B:** Yeah. A lot of people ask me this and especially how do you like eval your skills, right? So for those folks who never heard of evals, they're basically benchmarks that you run against some system by pushing a bunch of data through the system and then seeing what happens. So you might eval coding agent by saying okay, is it better with this model or this model by running like um a benchmark of something? You you get it to do the same task every time and you see if it um succeeds or fails. So that could be a 0% score or 100% score on the eval. Now skills are incredibly hard to eval incredibly hard and incredibly expensive to eval.

**[1:22:21] Speaker A:** How would I eval my like grill with docs or something? You know, like how would you eval u domain modeling? How do I know if I've chosen the right term? A lot of these skills are just sort of augmenting what the model does anyway and what the harness does anyway. Trying to kind of get out of the harness's way and just give it basically trying to get it to care about different things. How do you eval that? And if essentially I have the fortune of having a ton of data going through my skills anyway, right? Because I have, you know, you know, millions of users all around the world who are using the skills and reporting issues back. I've got very active Discord where people talk about skills all the time. So I'm sort of running evals except my evals are people, you know, they're just So what I do is I listen to them and I react and I try to improve my skills all the time.

**[1:23:10] Speaker A:** Um, but I don't burn tokens trying to build evals that might or might not give me good data. So that's the decision I've chosen.

**[1:23:20] Speaker B:** If I was in a model lab and I was being paid to do this and I had unlimited tokens, I would build evals.

**[1:23:27] Speaker A:** Okay. And which I think even those eval wouldn't be as helpful as what you're experiencing now with people.

**[1:23:33] Speaker B:** Exactly. if I didn't like I'm very grateful to my users because they do report stuff really really effectively and that's the actual stuff I need right if I try to synthetically create that with evals it would be worse

**[1:23:46] Speaker A:** so when they do give you feedback how do you go about implementing that how do you verify it how do you test it

**[1:23:52] Speaker B:** uh I have an agent that um looks at it and looks at the issue it tries to recreate that issue so it runs it in like a dummy repo and then it says yes this seems good and then and it creates a PR. So I have that on a schedule running um every day I think because I get quite high volume of issues. Um but I also get a ton of crap issues as well. So that agent also filter stuff out.

**[1:24:15] Speaker A:** Uh did we ever talk about like what happens after the PR like do you deploy the changes yourself to your infrastructure or do you let the agent do it?

**[1:24:23] Speaker B:** Um I use a continuous integration platform. So on let's say Versel for instance, it will just whenever GitHub detects a change to the default branch, it will just ping off to Versel and then Versel will redeploy my application. We'll build it. We'll put it in the cloud.

**[1:24:41] Speaker A:** So that's something that's been solved for yonsks right before agents. And so it's just not something I think about. And it's and it's always deterministic. So it always happens the same way every time. And I don't burn any tokens to do it, right? It just does it by itself. That's yeah and I didn't think about that like yeah CI/CD has already largely solved that problem. I think so many people don't even think about CI/CD. They just think maybe uh they think about just having their agents log in and deploy the code itself. Um so you would say that people should think about CI/CD and implement that.

**[1:25:12] Speaker B:** Oh yeah. I mean if you have a choice between determinism and non-determinism, why would you ever pick non-determinism, right? Why would you do like why bother? Because determinism works the same way every time, right? your agents can always go in and fix if things go wrong. It costs you no tokens and it just costs you CPU cycles or something, you know, just costs you this resource which is incredibly cheap. So, always pick determinism. And this is this is true too when you're doing like a retro or something when you think, should I change this into like a rule where my agent is going to code review against it or should I change it into a lint rule that is deterministic and runs the same way every time. always always choose determinism when you have a choice and most people don't realize they have that choice.

**[1:25:57] Speaker A:** Yeah, I I don't think they do. And and even just me recently, I just started doing some CI/CD. I I um host I self-host Git Git T or Gideia, I'm not even sure how to say it.

**[1:26:07] Speaker B:** Um and I I use some of their CI and action functions, which is it's great. Um, now for you right now, I take it you mainly probably do mostly teaching, but you do also do some of your own development. Do you have any other projects that you're constantly working on that you're maybe going to sell or make public, make it a SAS?

**[1:26:28] Speaker A:** Nah, I'm not a big SAS guy. Basically, I'm like I'm in this teaching thing as like a lifestyle choice basically. Um, I have a young son and I want to spend as much time with him as possible. Um, being at home here, like getting to choose my own projects, choose what I care about and choose my own time is incredibly important to me. As as you can imagine, I've been approached by a fair few organizations saying, "We would love to hire you and come work for us." But I'm basically unhirable at the moment. like until my like uh my son and I've got another one coming uh go to school then like and I have a maybe a bit more time you know until that happens I'm going to stick exactly where I am so I'm I'm not doing the SAS thing but I am a bit of an open source boy so I have a project called

**[1:27:14] Speaker B:** S castle which is a kind of effort to um do agent orchestration in Typescript using essentially allows you to drop in any agent and run them in sandboxes. So like in Docker sandboxes or uh Podman or Versell or actually whatever you want. And then I've got another one which is sort of falling a bit by the wayside at the moment which is called Everlight. And Everite is actually an eval framework amazingly. So I I worked on this like a year and a bit ago I think. Yeah, it's really um fallen by the wayside to be honest. But essentially it's like a a visual eval framework that you can run locally and so yeah it's um it's open source for me and kind of that's that's where the bulk of my work is going and also into this video editor that I've been building and that I use for everything.

**[1:28:03] Speaker B:** I'm fascinated by that because I also build lots of video editing workflows for myself, you know, because we make videos. Um, we should chat about that in a separate discussion because I'm sure we can go get very nerdy very quickly and not many people are going to care about it.

**[1:28:16] Speaker A:** Oh yeah.

**[1:28:16] Speaker B:** Um, now with your open source, I love that you called yourself an open source boy. And I I think for many people, they would love to not only start their own open source projects, but contribute to open source, but they don't know how. And they never could until really now. But how do you do that? Well, like could they take your skills and start to contribute or even start their own open source project and what would they need to like what would they need to be aware of that isn't already like what we haven't already discussed?

**[1:28:46] Speaker A:** Yeah, I mean what I'd say is that this was a different conversation about 18 months ago than it is now

**[1:28:52] Speaker B:** because now we are living in a world where it's incredibly easy for anyone to just ping up a slot PR to a repo, right? to just say I want this change made here's a slot PR and very popular projects are now closing their PRs to new contributors so for instance uh if we look at uh HonoJS I think they just did this the other day um Hono is one of the most popular kind of like server frameworks in JavaScript and you can no longer create PRs against Hono unless you're a collaborator right because of just the level and I've closed uh PRs on my skills for instance as well because I want my skills to be very carefully curated and it's a rather popular repo. It's nearly up to 300,000 stars now and that is, you know, people just pinging crap into it all the time and I just didn't want to be notified about it.

**[1:29:43] Speaker A:** So, open source now is all about providing issues and providing good evidence, right? Because it's so cheap now to turn those issues into pull requests and to just get an agent to work through them and to figure it out. So the higher quality uh repros that you can do is great and like that will teach you a lot about how to communicate to people working open source and how to communicate to other developers and how to communicate to AI. But of course you can build your own thing, right? And the cool thing about having all of this code available to you is that your agent can read it. You know your agent can just like take a look inside this codebase. You can say for slashte me about the Hono codebase. What can I learn based on what I've told you about my experience already?

**[1:30:30] Speaker A:** What is cool about this codebase? What are they getting right strategically? How are they deploying their infrastructure? What infrastructure do they have? What do they need? You know, and all of this stuff, you should just look at these cool projects and just point your agent at them and say, "Teach me about this." And then like again, open source is a lot um it's a lot simpler than people think it is, you know? It's really just like deploying something to uh npm or something, you know. So, npm you can just use uh like a um a change set manager to just sort of do versioning and things like this. Very very easy to learn, very simple to get um to get right, you can just do it within GitHub actions, make it nice and secure and you go and agents know how to do it. So, if you want to build an open source um piece of software, you can and agents will enable you to do it.

**[1:31:22] Speaker A:** It's interesting that you you mentioned that people are closing their PRs to only verify contributors. Um, do you think that they'll go even further and just cut off contributors because you can just have AI do everything for you now? Why even bother with the messiness of humans? I think um some projects do need teams behind them. You know, you still need teams of people like making decisions and um some you know, some more managing triage and contributing and that kind of stuff. But I think yeah essentially what you're saying when you cut off PRs is only these five 12 two people can contribute to this project using their agents and we are sort of and I think that's sort of always been true like anyone who's done um any long-term open source will have encountered the everyone who's contributed to open source has met a BDFL a benevolent dictator for which is the person in charge of the open source project

**[1:32:23] Speaker A:** who is wants it to succeed but they also only want their point of view in the repo and they are the one who is the the gatekeeper for stuff entering it. So contributing to open source has always been weird, always been political, always been a hard thing to do well. Um, it's why I have a huge amount of respect for people that I know who are amazing at it and who contribute to all sorts of open source projects, but I think it's harder to get into than it's ever been. H so what what do you think is the and actually I think we're going to get into some of the last things I wanted to ask you here but uh I think before the benefit of contributing to open source was that it would show it would be a free place to uh get experience and show off what you can do in order to help you land a job and actually make money from that because obviously open

**[1:33:14] Speaker A:** source there's no money in that. Is that still valuable to to be able to show off what you can do now that it's mostly AI doing that?

**[1:33:22] Speaker B:** AI has eaten tactical programming, but it can't do strategic programming. So, you need to show evidence that you can program strategically. You need to show evidence that you can um manipulate infrastructure, that you can build a beautiful repository, right? That you can improve your agents environment, that you can steer it properly. And I think that strategic programming skill is actually more valuable than it's ever been. You know, I I genuinely think that I think it's like because now you have a fleet of agents, tactical agents that can just go off and do whatever you want them to do. And so if you're able to raise their level and care about improving them, then it's honestly a rid like it's so much better than when you were working with humans. I've always cared about this, right? Even when I was working with um with people, I've always wanted to make the project better and make us all work faster.

**[1:34:14] Speaker B:** I've always cared about that, I think, more than maybe my colleagues had who just wanted to clock in and go home. So, not all of them, of course, but like just being able to have those skills has just felt like a ridiculous uplift in the amount I'm able to trust my agents. And I think that is an incredibly valuable skill because that can take you from a you know 5x agent user into a 100x 200 200x agent user you know

**[1:34:41] Speaker A:** okay so for someone who let's let's take the let's take a high school kid

**[1:34:48] Speaker B:** they want to become a software developer and in this day and age it's like what does that mean? Uh what what advice would you give them? How could they become a software developer? Should they? and what do they have to learn?

**[1:35:01] Speaker A:** So, I'm not I don't again I'm not I can't predict the future. I've not been on the job market for yonsks, right, since 20 or something maybe. Um, so I don't know what it's like out there. So, your mileage may vary in this advice, but what I would say is demonstrate that you care and that you care about the strategic stuff. you might not even need like great expertise in it. But if you're using language like deep modules, if you're thinking about okay, how am I going to improve things next time? If you're constantly thinking about not only improving the code, but improving the next code that comes through, then I think that is enough to start de and you demonstrate that through projects, right? That you're actually shipping stuff that may be assisting you in your own job hunts. You know, that's the classic one.

**[1:35:52] Speaker A:** um you know, you build a little uh CRM for yourself or something and you make it as beautiful as you can. You make it as performant as you can. You really care about it and you deploy it somewhere that people can click through it and actually view it and and fiddle around with it and go, "Wow, okay, this this kid knows what he's doing and he's doing it all with agents." That is what I'd say. And it is very possible to demonstrate that and demonstrate huge amounts of work. You just have to care about the strategic layout.

**[1:36:18] Speaker B:** Okay. So you would say would you say that anyone needs to learn a specific programming language right now?

**[1:36:27] Speaker A:** Nah. Uh programming languages like you know that's tactical stuff right

**[1:36:32] Speaker B:** you know actually getting good at a programming language you know that's you know it's it's important to be able to read it to understand what module boundaries are but you can just get agents to just teach you about it and to teach you about it in pseudo code. What I would recommend is start um start working through some of these classic books, you know, like a Michael Feathers book or something. Actually buy the book and start obviously it's going to be pretty dense, right? There's going to be words in there that you don't understand, but then use the teach skill or something. So, it pulls that down information for you so you can start actually going, "Oh, I see how I would apply this in real life." You know, this book is from 2003 and I I think it was wrapped in plastic in on my like bookshelf or something and I just thought, oh, like I've been prompting agents to design good code bases, but this

**[1:37:22] Speaker B:** guy was doing that before there were even agents, right? He's been writing how to what a good codebase is. And so I pulled it down and I just I couldn't believe what I was reading because it just felt so relevant to what I was looking at. and I was he was able to put into words the stuff that I sort of felt and I just started plugging that stuff into agents and that's how improved codebase architecture came about. Um so care about it read books about it use the teach skill to get your way there and that's how to do it.

**[1:38:00] Speaker A:** What other books should people read? Philosophy of Software Design by John Asterout. Pragmatic Programmer by David Thomas and Andrew Hunt. Um Michael Feathers is good. Refactoring by um what's his name? Martin Fowler. Uh Extreme Programming by Kemp Beck. Those are probably the big ones.

**[1:38:18] Speaker B:** Wow. And so would you say that people should read these to become effective at AI programming?

**[1:38:26] Speaker A:** Yeah. Uh if you actually do the reading, it puts you way ahead of everybody else in the field. genuinely like um so yeah definitely I I think I do think that experience is the only way to you know get there but

**[1:38:40] Speaker B:** it really helps when you have the experience and you have the words to explain that experience because I think like just understanding the language and the categories of things and like okay this is more important than this is that's what strategic programming is all about. It's all about finding balance between lots of different things that are all competing. You know, like, okay, I want my agents to ship features really well, and so I'm going to write 4,000 tests for them. Oh, but those 4,000 tests are actually slowing things down because they actually make the agent run really slowly. How do we winnow those down? How do we put those in a CI so that it can rely on them later? How do we shard them so that they've got, you know, running in four different um nodes instead of just one? You know, all of that that might sound confusing and complicated, but all of those are just words and you just learn the words and then you prompt the agent and then the agent can care about it.

**[1:39:33] Speaker B:** So, what you're doing is you're just giving the agent permission to care about the strategic layer and you're learning the words in order to do that.

**[1:39:40] Speaker A:** Okay, that makes sense. And it makes me wonder and I know you don't you're not in the job market, you can't really look into the future, but how effective right now are computer science degrees? I would ask how effective have they ever been actually because I I didn't get a CS degree, right? I got a drama degree, you know, I was a voice coach for six years and I just taught myself this stuff in like 2015 and started moving over.

**[1:40:04] Speaker B:** Wow.

**[1:40:04] Speaker A:** Um so yeah, I don't know. I don't know if that they've ever been that effective. Um the the issue is people who care and people who don't.

**[1:40:13] Speaker B:** That's interesting. And I I'm sure many people will be watching this and they're in a computer science degree. Um, what would you tell them?

**[1:40:22] Speaker A:** Care,

**[1:40:25] Speaker B:** you know, just just care about the the stuff you're shipping. Care about your users, care about the other devs on your team, even though they're agents, and care to learn more, care to be curious, and yeah, uh, enjoy because it is fun.

**[1:40:42] Speaker B:** And this is so fascinating because like it's fun to talk with someone who I didn't know you didn't have a competi degree because that's that's even more interesting. You're selftaught and I I think that's been the best way to learn anything for a while now. AI has made that even more obvious. Um for you if you were to hire a developer to join your team, should you need one? Actually, that's probably a two-part question. What would make you need one? Why would you need one? And what would you look for? what would they what skills would they need to have that would impress you?

**[1:41:14] Speaker A:** Um I mean I I hate to harp on this again but it is it is that strategic thinking right it is the environment it is the all of that and using the right language and caring about the right things. Um, for me, I do think there are bottlenecks all over the process still, right? This is not just um, you can't just infinitely accelerate and just like, you know, one person can ship 2,500 PRs a month, but if you have two people doing that, that's still 5,000 PRs a month. You know what I mean? That's still doubling the amount of work as long as both of them are enabled and both of them can work on cool stuff. And honestly, the the thing that really differentiates good products these days is not the amount of tokens that have been spent on them, but the amount of attention that has been given to the product, the amount of use

**[1:42:02] Speaker A:** that it's had, and the the smart things people observe about the product in order to make it better. So, it's the testing and the QA and the planning and figuring out strategically what needs to be done next to improve the product. How and noticing problems and and essentially product management and product design and that is something you need a human for, you know, or you need a human at least to tell an agent to care about it, you know. So yeah, that's what I'd say is that people now are all about directing agents and using their attention and their care to make the agents care about the right things.

**[1:42:41] Speaker B:** Okay. And it sounds

**[1:42:42] Speaker A:** the word care about a thousand times and I wasn't planning to. I think I've just found a new word that I like. So

**[1:42:47] Speaker B:** yeah. Yeah. I think uh and I think that is important because as we've kind of noticed uh through this, you can't just go in and just write code. You can't just go in and go, I'm going to make this thing work. You have to really care about what it's going to be. You have to think about it's it's like thinking about a child, like what do I want you to be? What how what can I expose you to? What are the standards I'm going to set for you? What's the rules for life I'm going to give you? Um that's interesting. Uh now I'm curious how much of this strategic programming um how to use AI agents and I'm going to allow you to shill your course a bit here because I I I love your course. How much of that is in the courses you create right now?

**[1:43:29] Speaker A:** Yeah, that's like I'm saying all this stuff matters and as I'm saying it, I'm trying to find ways to teach people about it. You know, I'm saying software fundamentals still matter and so people's follow-up is okay, what software fundamentals, how do I learn them, how do I apply them? And so I've got a course coming out in November. Um I haven't released this information, but it's coming out November 9th. is like a two-week cohort course that's just timed perfectly so that um I go on paternity leave like right afterwards and uh so stressing trying to get it done and all of that is about using my skills sure but skills are essentially just pointers to a process and the process I'm trying to teach is that you need to understand how to improve your agents environment. It's essentially the the end point is where you create a software factory that does a lot of this stuff for you.

**[1:44:19] Speaker A:** So a lot of the caring is sort of automated in these cron jobs in these routines that automatically try to make your agent and its environment better. As I was saying it's sort of like you know ideally the harness would improve the environment as you go and that's what we're trying to get to by the end of the course. Interesting. And I I've I just heard the term software factory for the first time last week and I know it's been thrown around for a minute. What exactly is that? Well, on the AI coding dictionary, we have a definition for a software factory. There is a definition for that. Um, and it's essentially I I won't pull it up, but what it does is if you imagine that producing work involves several points at which the human needs to interact with the work as it's being done.

**[1:45:12] Speaker A:** So, it might be that you need to tell the agent to do something. That's the first point. Then you might do a grilling session and you might um approve the plan. That's the next point. Then it might go all the way through until the work needs to be merged. Now what a software factory does is it tries to take the human out of more points in that process. So it might be that instead of you um needing to uh initiate the work, it might be that there's some trigger that happens. Let's say a new issue is created on your repo that pings down to an agent and the agent decides whether to initiate some work based on that. Or it might be there's a slow database warning in your um in your service that checks your database that again goes down to an agent. The agent decides whether to um proceed with that.

**[1:46:00] Speaker A:** And then you might have ones where okay that might not even need a human in there all the way up to human review. But maybe you don't do human review for things. Maybe you use that oneway two-way door thing and actually only one-way doors need a human review and the agent just goes and merges it itself. So the software factory is basically just taking humans out of more points so that you can accelerate the development of software more. And the issue with that is that the more you accelerate it, you need breaks as well. You need to be able to pull the software factory back so it doesn't just become a slob cannon. which again is where the strategic layer, the thinking about the environment really makes a big difference.

**[1:46:41] Speaker B:** Okay. And that that sounds great. Um but it also sounds really hard to do.

**[1:46:48] Speaker A:** Yeah. Yeah, I think so. I think um there are you're basically having to plug together a bunch of services in order to do it. I think as um the tools and the harnesses improve and make those things easier then you know you know like people are obsessed with like loop engineering like

**[1:47:07] Speaker B:** um few months ago or whatever this is basically loop engineering what you're doing is you know a loop is one way to do it where you just schedule the agent to just like pull the GitHub issues and just sort of initiate work on its own. Um but you can have multiple different ways of doing it essentially. So this is just loop engineering by another name essentially and it's it's very exciting and it means that you can churn out a ton of work and really improve the quality of what you're working on. Uh and that's what software factory is.

**[1:47:34] Speaker A:** Interesting. Okay.

**[1:47:35] Speaker A:** And then you I'm curious about how you approach so like for like right right now if I went to your course website is that a platform or is that something you guys designed?

**[1:47:46] Speaker B:** Yeah, that's something we built from scratch. Um I work with a team called badass.dev. dev and they work with a few course creators and they uh build this uh course platform from scratch basically.

**[1:47:58] Speaker A:** Oh dang, that's pretty cool. So you're not you're not running the AI coding for that right now?

**[1:48:03] Speaker B:** Uh no. What are some do you have any projects you're working on right now?

**[1:48:08] Speaker A:** Uh the open source stuff?

**[1:48:11] Speaker B:** No, just S castle. just um trying to get this course built and trying to uh yeah ship this video editor that's uh always always constantly improving.

**[1:48:21] Speaker A:** Okay. Okay. I can't resist. Tell me about this video editor. I I've seen you post about it a few times and I'm like that looks interesting. Okay. He's he's having it create demos for him before he records it. That's interesting. So what is this thing?

**[1:48:36] Speaker B:** Oh, it's it's outrageous. So it's uh it is it is outrageous. It's uh uh what it is. It came down to this idea that I hate editing video. And so what I wanted was I wanted to as I recorded, I would essentially leave a little gap and then it would cut that and that would go be transcribed automatically and just appear as a clip in the finished editor essentially. So there's no editing. So I edit as I record. And from there that developed into, okay, I need like a I use a lot of diagrams in my setup. I'm going to build like a custom diagram playground as well that links to the clip so I can see from the clip which diagram I was viewing that so I can go back in time and just edit it and stuff. And then maybe I Oh, yeah, Elgato teleprompter looks quite nice.

**[1:49:22] Speaker B:** Maybe I need a teleprompter, too. Um, oh, maybe I can customize the teleprompter based on what I'm seeing. Oh, maybe I can get an agent to write scripts. Maybe I can get an agent to write animatics as well. Opus 5.5 looks really good with actually building out um custom videos for you. So why don't I watch the video I'm about to record before I record the video. That seems good. And then from there I you know it just grows and grows and grows and like and now like every edit I make get automatically synced to my course platform. Um I have you know version history. I have linting. I have uh AI writing. Like it's just a a ridiculous wonderful project. And it's it's open source too. So, it's in course video manager.

**[1:49:59] Speaker A:** We're 2,500 commits deep now.

**[1:50:02] Speaker B:** Um, and it's just all in here, you know. So, if you want to uh use this as

**[1:50:06] Speaker A:** like I I don't take um pull requests and um like I don't even take issues on this actually. Uh but if you want to just have a look at it, it's there.

**[1:50:14] Speaker B:** Yeah, I'll take a look. And I I I do something not quite as streamlined as you, but I do um have it to where when I finish recording, my AI has been trained enough back and forth with me to where it knows how to edit me. It knows what kind of cuts I like. It knows that when I cuz I I I've been doing this for a long time. I used to edit my own stuff. Now I have editors. So like when I say something, I'll freeze so I can remember what to say again and we don't have to do a weird cut and then I'll keep talking. Um so it knows to watch for that. So when I finish recording, I'll just tell, hey, go go go to the place we where we have our files recorded, offload it, ingest it, and what that means is it will um transcribe it.

**[1:50:54] Speaker B:** It'll use the Gemini video API to watch it so we know exactly what's happening. And then um it will start to actually produce an edit, and it will edit it to like a very clean draft. We coded our own frame to IO. I'll watch it to make sure the story is right and type and then it will export an XML for Adobe Premiere where my editors just open up and there's the draft ready to go and they can make it look pretty. Um, it's it's very cool, but I want to get some more where you are. That sounds very interesting. Uh, it's just so great. It's so great. Um, yeah. I mean, it's, you know, it's there if you want to have a have a play around with it. Um I I just wanted a project that I knew that I would constantly use and constantly update and like so it's just always in the back of my head that okay I'm going to work on this going to

**[1:51:39] Speaker B:** work on this and I've you know I've got agents right now like playing around with it improving the environments that the code operates in. This is my main playground really for trying out my ideas.

**[1:51:48] Speaker A:** Now you you mentioned that you have AI scripting.

**[1:51:53] Speaker B:** How do you feel about that? Do do you do you uh speak word for word from what the AI scripts for you?

**[1:52:00] Speaker A:** No, I mean I did a drama degree, right? So like I'm good at improvising words and I just use the script as like a uh it has like commands that I can copy and paste in order to set up the environment and stuff and like go to the right commit in the the history for the project I'm working on. Um so mostly it's just a guide essentially. So I'm always improvising what I'm saying.

**[1:52:21] Speaker B:** Interesting. So I I mean I create courses as well. So I'm I'm I'm very curious about your process. Uh is AI pretty much part of every process of your course creation from like ideation to to episode or um video management and all that? So, well, one thing I do and one thing uh that I I actually recommend to anyone who has an audience, who has people pinging them all the time is I have a a personal wiki which is for my audience. And every 3 hours or so, I have a chron job that um looks at all my tweets people have sent me, all my mentions, uh all my Discord messages, all my Slack messages, my Gmail, basically every sort of input I can find and then writes that or sort of ingests it into uh Carpathy style LLM wiki. So that means that I can go into this, it's just a repository, it's private obviously, and I can just ask it, hey, what is my audience interested in?

**[1:53:17] Speaker B:** Right? what um questions do they have about these skills? And from there, I can create learning goals from that. So, things that people are interested in learning. From there, I have to actually get off AI. I can't use it for this next bit because it's too hard. I print off those learning goals onto these little car bits of card, right? Oh, I love

**[1:53:36] Speaker A:** And I I like rearrange them physically in space until I realize, okay, this feels like a lesson. This feels like a lesson. This feels like a lesson. figure out that can take a couple of hours actually just off computer off AI um just for one section and my courses often have eight sections. So and from there I go back and plug that back in so it turns into lessons and turns into videos and then I start writing the scripts and getting agents to dry run it as well. I create these animatics and then I'm ready to record. So you know it it can be months planning a course. It really can. It's very very slow.

**[1:54:13] Speaker B:** That's fascinating. So, I mean, two things that just jump out at me. First, the the wiki idea is such a good idea. Um, I'll probably steal that. Uh, the second one is uh that you have to go off offline to do this kind of thinking, which like I've got pen and paper and this is I find the best thinking happens with this. And I do use AI quite a bit to bounce ideas off of and like try to form an idea more, but it's it's those very human moments where I'm disconnected that things the magic happens. So I'm curious how often do you do you go back to that kind of thing where you're disconnected? It's mostly on tasks where there is a lot of information and I need to keep it all in my head at the same time because if I'm like planning if I am like talking to an agent and we're

**[1:55:02] Speaker B:** having a back and forth about a plan and maybe shaping the plan in certain ways then it is going to write a ton of stuff right in response to me and I lose so much time by trying to get over that communication gap right constantly trying to go okay what do you mean And and in doing that, I lose context, right? I lose information that I could if I just slowed down and I just kept everything in my head at a speed that works for me. L, you know, writing stuff on pen and paper. It sort of slows you down so that you can consider things at the right speed. It's it's me paced, right? It's paced at a human speed. Whereas agents just work too fast for that. So for specifically planning, that's what I have to do. And I've not found a better way to do that with agents.

**[1:55:50] Speaker A:** That it's it's interesting you mentioned it that way. When you're talking to an agent, you're like trying to bounce an idea off of it or just like try to do anything.

**[1:55:57] Speaker B:** It does feel too fast and you're it'll say a bunch of stuff and it's so dense you're like

**[1:56:03] Speaker A:** or too slow as well, right? Or you're just waiting for a response for like 2 minutes and you think, "Oh, I just check Twitter." And then half an hour later you go, "Oh, what did the agent say?" You know?

**[1:56:10] Speaker B:** Right. Oh, yeah. Yeah. Like like 7 7 o'clock at night and you're like, "Oh, I would did ask that question earlier. at night and I don't even care about that anymore.

**[1:56:19] Speaker A:** Exactly. You just got to get out of the conversation. Just keep it in your own head for a while and then I usually just brain dump it back to the agent. Um just, you know, use whisper flow, dictate out a ton of stuff and then um then it just pulls it into its own structure and its own data and then I just usually chuck the cards away because I don't don't need to go back to paper there because for small edits, for little stuff, once you've got the main structure, AI is really good. Do you use AI in a way to where because I know we've been looking at coding agents and and getting the coding agents to know your repos and your code, but do you use anything for your life? Do you have like a Hermes agent or any kind of agent that like has the context of you?

**[1:56:58] Speaker B:** Um, yes. This audience wiki has is sort of a bit of a blend of like me plus my audience, right? Because those things are often closer than you think. And so, yeah, I I have that repo sort of serves as like my home base for all of my agents. And so I have like a daily standup with my agents where I say, "Okay, what tasks need to be done today?" Um, I have a like a pixel watch that I dictate stuff into and that goes on my to-do like an agent triage to-do list and the agent then pulls it into um it was like uh deciding every minute of the day for me like scheduling out all that stuff. And I have like a little um little thing in front of me. This is called a terminal that basically Yeah, they're kind of they're all right.

**[1:57:40] Speaker B:** I don't know if they're any good, but I've got two of them actually, one downstairs and one upstairs. And uh I was just sort of ignoring it. So, I'm I'm still trying to find the right uh interface for the agent to help me run my life, you know, but it's a it's a me problem, not not an agent problem. The agents are really good at it.

**[1:57:58] Speaker A:** I find the same thing. I'm I'm trying to figure out the best way to like like help me schedule my day or help me do this and help me work with my team and help it's it's I don't think anyone's quite solved it yet. Well, it's really hard to figure out.

**[1:58:09] Speaker B:** No. And I think it's actually much harder than coding.

**[1:58:13] Speaker A:** Actually using it for knowledge work is much harder than coding because coding is so verifiable, right? You can use these automated checks to actually make sure that the thing you're doing is correct, that you have high quality on the output. But with knowledge work, with planning a course, how do you how do you know that you've built a better course than you did two months ago? You know, it's really hard. There's no way to verify that. How do you know that this video script is better than um your previous one? So, yeah, I think knowledge work is really difficult, way harder than people think it is. And I think we're going to be hitting that over the next few years as we try to force AI into all of these holes.

**[1:58:52] Speaker B:** And I love that this entire call you everything coding related you're like it's easier than you think with knowledge work you're like it's actually harder than people realize. Yeah, maybe I'm wrong there today. Maybe it's just because I know coding more than knowledge work. Maybe.

**[1:59:08] Speaker A:** No, I think I think you're right though. It's that very very distinct point you made is that coding is verifiable and that you can learn it and it's it's deterministic and you can test it and like you you know it's good, it works or

**[1:59:19] Speaker B:** I mean that's that's why agents are amazing at math problems and can solve math problems way better than humans because every part of it is verifiable. All the inputs are text and all the outputs are text. But it's also why they still can't draw hands, right? Because like it's just different inputs than they're used to, right? They can't write a convincing tweet that we don't know is is AI, right? Because that is just a much harder job because it's so so much less verifiable.

**[1:59:47] Speaker A:** And it's something I don't even really care the AI can do. I think there's there's human things that I want to keep human that just make us who we are. And communication is like one of those things that make us who we are.

**[1:59:57] Speaker B:** Absolutely. Yeah. I play a ton of board games. Um keep agents out of my board games. I don't want to see any AI art. I don't want to hear any AI music. I don't want to uh I get a thousand AI tweets a day and I hate them, you know.

**[2:00:10] Speaker A:** Yeah. Yeah. I think we feel the same way.

**[2:00:12] Speaker B:** Yes. Absolutely.

**[2:00:13] Speaker B:** Well, we are near the Actually, no, we are at the end of time. Um tell me where can people find you and with your courses where should they start?

**[2:00:22] Speaker A:** Go to aihero.dev. It's the place. Um find my skills. Uh install my skills, enjoy them. Um, if you have any questions, go to the Discord, find me on Twitter. Um, you know, I'm pretty active in all those places and I'm on YouTube as well. Um, recently crossed 400,000 subscribers, which I'm very pleased about. Congrats.

**[2:00:38] Speaker B:** And, uh, yeah, look me up. I'm there.

**[2:00:41] Speaker A:** Do you uh do you have like a wait list for your new course?

**[2:00:45] Speaker B:** Uh, there's a newsletter. Um, but yeah, sign up and I'll see you there.

**[2:00:49] Speaker A:** Cool. Awesome. Well, Matt, this has been so fun and informative and you've given me so many ideas. Thank you for taking the time to not only teach me but my audience. This has been very very cool.

**[2:01:00] Speaker B:** Appreciate it, pal.

**[2:01:01] Speaker A:** Hey, made it to the end of the podcast. At the end of my videos, I like to pray for you, my audience. Kind of weird, I know, but just go with it. You're not here for um I mean, you are here for a reason. It's not an accident. And yeah, let's just go with it. Uh I put it at the end, so you have the option to just, you know, duck out. The information has already been given, but if you want to chill out and stay here with me right now, I'd like to pray for you and your life and your family. Ready? 1 2 3 pray. Uh God, I thank you for the person on the other side of this screen, this camera. I thank you for them, who they are. And um I thank you that they stuck to the end of this and that they are learning about coding and and um technology and just all this AI stuff, which can be stressful, but also is very life-giving if

**[2:01:45] Speaker A:** we approach it the right way. So God, I ask in your name that you shift any anxiety, any stress uh about AI or the future, about jobs. I I ask that you would just flip that switch in their brain to be joyful and excited and let them be at peace about it and just give them energy and and give them ideas and a path forward. If they're looking for a job right now, I pray you provide that job. If they're looking to start a company, give them that idea and the and the steps forward. Bless them right now. Bless them and their family. Watch over their families. Um give them peace and joy in their lives right now. And help them to take the knowledge from this video and apply it well. I ask this in your name, Jesus. Amen. Thank you for letting me do that.

**[2:02:33] Speaker A:** I'll catch you guys next time.
