Lazar Jovanovic: commitment

Transcript context

…Oh my God. Everything you share is so interesting. I want to keep digging. So just to reflect back the sequence, and then I want to follow up with another question. The sequence you go through when you get stuck, which is going to happen to everyone. One, is just ask the tool to try to fix it. And oftentimes, it's telling you, "Something is wrong. Can I fix it for you?" And you're like, "Please fix." Sometimes that'll work. Two, is work on adding more debugging messages to the console log. And this advice, I love of just ask it to add more debugging lines to its own console log to help see what's going on. And then you can ask it, "Okay, now that you're looking, look at all the output of your console log, see if you can help find the problem." And then step three is go to Codex, which is so funny. And I hear this a lot, that Codex is the most elite engineer as an AI. Karpathy tweeted this once that... And we had the head of Codex on the podcast too, by the way, that he's like, "Anytime I have the most gnarly bug, I just go to Codex, let it run for half an hour, and it solves it unlike any other tool out there." And so it makes sense that that's where you go. So the idea here is you point Codex to your code, you show all the console output logs, tell it what the problem is and just have it go figure it out. Sweet. And then this final step is so great, and this is where I want to go, which you use this as a learning opportunity so that next time, you solve the problem more quickly or avoid it completely. So what you do there is you ask the agent, "Okay, here's what happened. What can I do? What could I have said? How could I have prompted you better to have gotten this immediately solved?" Yeah. And then even deeper than that is like, once you go through this conversation, you're like, "Okay, let me eliminate myself again completely out of the equation because I won't remember to prompt you better two days from now. " Put this into rules, put this what we just learned into Rules.md, because I'm making you read the rules every time anyways, so you might as well just record it there. So I'm not going to prompt you better. You're just going to learn that I'm stupid and you're going to prompt yourself better. Right? Again, just eliminate yourself and move the context, you solve 99% of the problems with AI today. So idea here is help it build its own brain and rules and way of thinking based on problems you run into. So great. Okay. So I want to come back to this point you've made a couple of times, which is so interesting. This idea that you watch the output of the agent to learn what is going on. There's something I've seen other people. Ben Tossell, who I think is at factory now, shared this recently. He's also basically vibe coding all the time. He was brilliant to no code tools before, and now he's all about vibe coding. Basically, he's learning how coding works and learning how systems work by watching the agent output. And this connects to something Michael Truell shared, the CEO of Cursor. He was on the podcast. He had this vision of Cursor becoming basically what comes after code. What's the layer that we are adding on top of code where people don't need to worry about code anymore? And at that point, it was like a year ago that we chatted and it feels like this is the layer, is the agent conversation of what it's thinking, and then what you tell it back. So essentially, it's English in a conversation, which is like, it's not even pseudocode. It's interesting that that's where it feels like things are heading. The layer over code, just its thinking and your conversation with it.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.