2 ms·
Right but that's like showing the compiled binary but not the source. With claude code prompt and config is everything.
by jaggederest 1y ago
Right but that's like showing the compiled binary but not the source. With claude code prompt and config is everything.
- globular-toast 1y agoThis is the saddest part of this whole thing for me. You consider the prompts and config to be the real source code, but those are just completely lost into the ether. Even if you saved the prompts you can't reproduce their effects. 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.
- jaggederest 1y agoI have repos on github. I show the code. 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.