در حال بارگذاری ...

Using Claude to Interview0:08

Now, this next technique is very cool. If you're using Claude and you're planning out a new feature, you can actually have it interview you for the purposes of building up a plan. And I bet if you do, you'll get much better results. Let show you, let's bring up the terminal boot up, Claude. And let's say have a look at my video pipeline. This handles the process of preparing and uploading all new course episodes,

This handles the process of preparing and uploading all new course episodes, but at now I want a dashboard so that I can visualize the progress. So I want you to take a look at that directory review how it works, and then I want you to interview me using the Ask user question tool. This is a special tool that comes with Claude. Uh, sometimes it will do this automatically, but here we're going to be explicit that we want it

Uh, sometimes it will do this automatically, but here we're going to be explicit that we want it to ask us questions before it works on the plan to make a plan. I'll hit shift tab to confirm that we're in plan mode, and here we go. All right, so I'll explore your pipeline to understand how it works. And yeah, while it's exploring, I'll show you a couple things real quick.

Reviewing Pipeline Structure1:12

And yeah, while it's exploring, I'll show you a couple things real quick. I have these Worker Bee classes, uh, so you can see the API, it's video work and release, and we have all of these different implementations that are responsible for uploading to S3. Uh, optimizing the audio, transcoding it, um, moving it to Vimeo, creating transcripts, all of that stuff. There's actually a number of things that need to happen. If I take a look, here are some of them. So we edit.

There's actually a number of things that need to happen. If I take a look, here are some of them. So we edit. That's like an AI generation task. Uh, we, we have a reset, we have transcoding, we have uploading, and yeah, I just think of these as worker bees. Each of them has one little task that it's responsible for. So we're gonna create a dashboard to visualize all of this. All right, here we go. So real quick, you can see it's scanned everything.

Answering Interview Questions1:53

All right, here we go. So real quick, you can see it's scanned everything. It figured out the general pipeline flow, and now it's gonna start interviewing me before it works on the plan. All right, what's the primary view? You want a series level overview showing all pending series and their overall progress, or a detailed episode by episode view. So do we want overview detail or actually I want both.

or a detailed episode by episode view. So do we want overview detail or actually I want both. So yes, should the dashboard update automatically or require a manual refresh? Let's do actually deferred props. Do you wanna take action from the dashboard or just view status? I definitely need to be able to take action. For example, if I decide a video should be marked as free, I should be able to check a button there

For example, if I decide a video should be marked as free, I should be able to check a button there and then it will update to the DB full control. Next, where should this dashboard live? Do we want a standalone page? Yes, we're gonna do admin slash pipeline. And yeah, you get the idea. So I can submit these answers and now we can use that to construct the plan. And again, without taking that step, uh,

Why Interviews Improve Plans2:47

and now we can use that to construct the plan. And again, without taking that step, uh, sometimes it's just gonna fill in the gaps. It's gonna guess on your behalf. And if, if you, if you are not meticulous about reviewing these plans, then sometimes a lot of work will happen. Uh, just for you to find out that you don't like what it did. Oh, a few more. How should the pipeline stages be visualized for each episode?

Oh, a few more. How should the pipeline stages be visualized for each episode? Progress bar? What actions do we need? Uh, do we want reset? Do we want retry, edit metadata? All of the above. Should the dashboard show historical completed series, or only active ones? Um, recent history. All right, here we go. And now we can see the full plan, and it's not worth going over in detail, but yeah, it is going to be significantly more in depth

and it's not worth going over in detail, but yeah, it is going to be significantly more in depth and thoughtful as a result of doing that interview. And that's the key thing when you're working on a new feature, especially feature where it's not fully thought out yet. It would be very, very helpful to ask the agent to interview you for the purposes of fleshing out the plan, and then you can get started.

and then you can get started.

دوست دارید گاهی خبرهای Laracasts را ایمیل کنیم؟