When vibe coding gets you 90 percent of the way there but the last 10 percent keeps breaking, how do you diagnose the real problem instead of endlessly prompting?

48:35Next one comes in from Josh Kaufman in Pittsburgh, Pennsylvania. when vibe coding gets you 90 of the way there but the last 10 keeps breaking how do you diagnose the real problem instead of end instead of endlessly prompting john wallace is going to take a swing at this one john it really comes down to are you logging are you giving your ai

48:58context to what the problem is and then before you you get to the actual like problem that's going on? What are you trying to solve? And this were, I guess, prompt engineering, but really, it's just like writing and stating a problem sentence and what the expected outcome is and making sure that you're asking, right, your AI agent, is this the best way to solve this?

49:25Why are we running into this issue? Do we have some sort of larger architecture issue that we should be addressing? And then breaking down the problem from there. If you just keep in a loop in the same session asking the same agent, it's insanity. You're literally just repeating yourself over and over again. It's a complete waste of time. It's a good opportunity to go to a new session,

49:48use a different agent, and ask these questions of like, hey, this seems to be brittle in my app. Why does this keep happening? And then understand architecturally, because it's just trying to get you to do the fastest answer. That's literally all it's programmed to do. Give me an answer that's fast. Give me the dopamine. and let's create this addiction loop so we can then move on to the next feature.

50:10The next feature, it's not asking, am I building the best app possible? Am I addressing this architecturally where this is something that will withstand pressure and usage? You'll see me like in the pre-show, it was just like clicking a button 20 times and clicking back and forth between my screen share and myself. I just want to make sure that there's no sort of fragility in those little things.

50:31and even then I decided to close something on my machine and ended up crashing core video so guess what I get to do after this I'm gonna go figure out why that happened but I'm not gonna like if it doesn't get it the first time I'm not gonna be like no try again like I'm gonna try okay what context do we need

50:47what else do we need log do we need to record something you know provide more context of what was exactly happening at the same time maybe a system profile my machine so like an event logs like all these things play into solving problems problems quickly. It all comes down to can I give the right context so it has the right information so it can solve the problem.

51:07Jackson Safir. Yeah. So, just like John said, you ask it to do logging. So, whatever things going on in your code, it actually do logs them to a file or a console so that the agent can can read them what's going on and which stuff at what part of code we are getting this issue what's the log look like what has happened behind the scenes it can actually look into it so I

51:35actually in my workflow I actually ask it to do regular unit tests and stuff so it can actually write tests that can individually test the component, its road, is it functional, is it going to blow up when we open up. So it actually writes the test and runs the test. So also if something comes up like an issue or a bug or a crash, I actually ask it to

52:07check the logs and fix it itself. So the recent app that I built, something called AudioMetrix, that is actually entirely unit tested by the agent itself. It actually wrote some scripts to even have my mouse clicks automated. So it actually opens up the app GUI and it actually clicks the buttons and opens the dialogs and things, scrolls over the UI and it actually does stuff, does actions, take