I think I'm with the majority of commenters here in thinking this would just wind up being clutter. Markdown might now generate code, but it isn't user facing and doesn't get shipped (I don't want to install a library and have a tonne of prompt text unnecessarily downloaded). I also don't really want to be on the hook for maintaining my co-workers past prompts etc.
For people who like this idea, or do something similar, how do you make use of prompts used to create code checked into your codebase?
I can see it valuable at the review stage, but if I was trying to trace-back a regression to a previous commit, I feel like I already have enough noise without this attached.
benrutter · · focus · HN ↗
For people who like this idea, or do something similar, how do you make use of prompts used to create code checked into your codebase?
I can see it valuable at the review stage, but if I was trying to trace-back a regression to a previous commit, I feel like I already have enough noise without this attached.
akazantsev · · focus · HN ↗
Any prompt-storing/sharing ideas floating around hit the same wall - they assume the text will be in English. It won't.