Is it possible to view the prompt history? I’ve had extreme levels of productivity and would love to list out how I’ve been using it generally for an article like this but it would be incredibly impractical to log it on the side.
Personally, I'm less sold on tracking prompts as being valuable both for production cases (imo if a human should read it, a human should have wrote/fully edited it applies to commits/PRs/docs etc) and for vibe cases where the prompts are more transitory
I feel like the results I get are qualitatively superior to anything I've seen anyone I've worked with produce. The fact that it's a lot faster is just gravy on top.
Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code.
So, no, prompts are not source code, that's why I ask for people to just show the code they are producing and nobody ever does.
I also make my design documents (roughly the prompts generated by the prompts) into committed markdown documents. So I show the second-tier prompts at least, you could consider those an intermediate language representation if you like.
> Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code.
I usually try to commit the initial prompts and adjustments. I don't commit trivial things like "That's not quite right, try doing X again" or "Just run the entire test suite"
> So, no, prompts are not source code
Hard disagree, but that's fine.