Using the Virten Prompt Library and Daydal Sidekick AI To Update A Complex Codebase II

Using the Virten Prompt Library and Daydal Sidekick AI To Update A Complex Codebase II 00:00:01    Hello, Terren here, founder of Virten.app and the Virten prompt library. And this episode is a continuation of the previous episode where we updated the category pages to mesh with the new updated and reorganized categories in the data files. Now, I had the process went well in the previous video, and it seemed we only had the one bug with the wrong title. It turns out that's not the case. For some reason, the AI did not get the idea that it needed to also create and update the hyperlinks to point to the 00:00:42    actual data files. This happens sometimes where the AI does the job at a very superficial level and you get this sort of unexpected result. Sometimes it looks like a bug or a big problem. So one has to stay sharp and on top of their game and first verify whether you gave the AI full and complete instructions to really thoroughly do the job. And what was missing must have been an instruction to update all of the hyperlinks. Also, when I imported the document from free datal, uh, I ought to have taken the time, but 00:01:27    for the sake of the video, I just used the document immediately. Should have taken the time to update and master the document. So, here's that document again, which is now mastered. I went over it for 20 minutes to make sure it was all in line, that each of the hyperlinks here had the correct name um rather than something that datig. So now we're simply in this video going to perform sort of the second iteration of this update giving the AI information that we know is more perfect for the job. So let's get that done. 00:02:43    So I'm telling it more thoroughly. You must update the hyperlinks themselves and the text of the button link. We hit them with the code name implementation prompt so it understands what's going on and our communication can be stable between the AI and myself as the developer. We'll send that off and run the second iteration of this update to our codebase. All right, so the AI went with its first response. These things can be fickle sometimes and it doesn't follow the order perfectly by informing me 00:03:27    there's more to do. So I'll just have to give it the continue order anyhow. All right. So, it performed the next step of the implementation without a hitch, produced the correct final technical document, and now our four files that we're interested in updating have been updated. Let's update our application in our GitHub client and push that into our preview environment. Let's push that. All right. So now the application has successfully built over at our web host and we can now refresh our browser 00:04:46    and see the updates. I'll hit the control F5 to make sure we get a fresh view. This hyperlink was successfully updated in its label to general use A. That's perfect. Now let's click each link and see whether it works. So, we have bugs to work on chat instructions page. We'll make our bug log here while we test. factor this code works. Those are working. The next category. Okay. found another hyperlink that it failed to update. There's no good explanation for why. So far so good. All right. Fun and marketing has 00:06:42    failed. And which was that? Explore and research. see fun and offbeat is here and fun and marketing's users guide filled out. So we have to go through to iterate a third time. I'm going to tell it to specifically review the data folder for the locations appropriate hyperlinks. update the hyperlinks you failed to uh to correctly implement links listed which failed. find where appropriate data file target. Okay. Always drop uh code name in there. All right. So, this turns out to be one of those what is the AI doing? 00:08:27    Why is it not updating the hyperlinks? Why is it making up new names instead of following the instructions? The kind of situation where since I know we made one mistake at the beginning, which was we gave it u we gave it this document in the previous episode before we mastered the document and made sure it was all perfect how we wanted it. Now that the document is perfect how we want it, what we're going to do in the next episode is start again with a new development session, create roll back to our 00:09:04    previous fork or pick up from our previous branch, create a new fork and do this job from from scratch with these improved materials and let's see how that goes. So this is Taran. If this video is helpful or you're looking at that Vertton prompt library, it's very helpful as well to your coding, then please like and subscribe. Check out the product. launch.vertton.app is the place to go to read more information. If you'd like to use free datal1.Virten.app, that could be a big help as a sidekick AI.