But that is like save feelings instead of raw data.

Prompts are subjetive, models can build different thing every time the "read" the instructions.

That doesn't fit with assembler - high level language analogy.

Reply to this note

Please Login to reply.

Discussion

That's kinda the point. Things change. Prompts allow us to define the requirements without holding is into specific framework versions. As things evolve, the result of the prompt must be different.

In other words, there is no point in keeping code because you have to maintain it.

Now i see.

Hodling the idea. But not strict rules.

But how you save prompts?

I mean, the construction of a product take a lot of prompts and try and error.

What do you save?

Basically everything. You can to keep refining your prompt, which will become massive over time.