[btrettel]

> maybe you don't have the necessary perspective to understand what you're asking for.

I disagree. Thinking about this more, I can give an example from my time working as a patent examiner at the USPTO. We were required to include detailed search logs, which were primarily autogenerated using the USPTO's internal search tools. Basically, every query I made was listed. Often this was hundreds of queries for a particular application. You could also add manual entries. Looking at other examiners' search logs was absolutely useful to learn good queries, and I believe primary examiners checked the search logs to evaluate the quality of the search before posting office actions (primary examiners had to review the work of junior examiners like myself). With the right tools, this is useful and not burdensome, I think. Like prompts, this doesn't include the full story (the search results are obviously important too but excluded from the logs), but that doesn't stop the search logs from being useful.

> You might as well ask for a record of the conversations between two engineers while code was being written.

No, that's not typically logged, so it would be very burdensome. LLM prompts and responses, if not automatically logged, can easily be automatically logged.

[selridge]

> LLM prompts and responses, if not automatically logged, can easily be automatically logged.

What will you do with what you’ve logged? Where is “the prompt” when the chat is a chat? What prompt “made” the software?

If you’re assuming that it is prompt > generation > release, that’s not a correct model at all. The model is *much* closer to conversations between engineers which you’ve indicated would be burdensome to log and noisy to review.

[btrettel]

> What will you do with what you’ve logged?

Could be a wide variety of things. I'd be interested in how rigorously a software was developed, or if I can learn any prompting tricks.

> Where is “the prompt” when the chat is a chat?

> The model is much closer to conversations between engineers which you’ve indicated would be burdensome to log and noisy to review.

I disagree. Yes, prompts build on responses to past prompts, and prompts alone are not the full story. But exactly the same thing is true at the USPTO if you replace "prompts" with "search queries" and no one is claiming that their autogenerated search logs are burdensome.

Also, the burden in actual conversations would come from the fact that such conversations are often not recorded in the first place. And now that I think about it, some organizations do record many meetings, so it might be easier than I'm thinking.

> What prompt “made” the software?

All of them.