Dan Shipper

But it's not like there are those little tricks that are...

you know, uh, like I'll pay you $2,000 or whatever and that, that you don't have to do anymore to get better results.

And they'll probably, there will probably always be like certain things you can do to like make it better.

But the big thing is, um, knowing how to manage the model, knowing how to ask for what you want and know if you're getting it back.

And that's like kind of prompt engineering, but it's very, um,

it's very specific to your workflow and what you want and the, and the, and the kind of thing that you're doing.

And so I think it's prompt engineering is like maybe like writing.

You can like, you write in all these different circumstances and you can get better at writing, but like we're really talking about specific things that you're trying to get done, you know?

Yeah.

Um, so I,

I don't expect people will study prompt engineering, but I expect that they will know some basics about certain little tricks, but mostly how to do it well for their specific use cases.

Do you feel like you really don't understand it?

I still don't, but that's because I hired someone who understands it.

Somebody knows.

That's how I would modify this.

We had a little bit of a retro at every about this whole thing, and when we launch something,

Sometimes we label it as an experiment and it's okay for it to be a little rough around the edges, but if we're really launching something, we want it to be good.

And also, on the other hand, when we launch something, I don't want to have to be up all night seven days in a row trying to fix it for my own health.

No, yeah, for real.

So what I've realized is we need a buddy system where if I'm doing this, I need someone else who knows the code base and knows a little bit about it to...