3 ms·
On the one hand, yes. But on the other hand, if you want to launch a competitor or use a private version on your laptop, they're quite valuable. One can assume
by crazygringo 4y ago
On the one hand, yes. But on the other hand, if you want to launch a competitor or use a private version on your laptop, they're quite valuable. One can assume it's taken tens of thousands of hours of QA testing and refinement to arrive at this exact sets of prompts with this exact wording. Even little details like putting "MUST" in all caps are presumably important -- like it wasn't following those rules enough, until they were extra-emphasized.
To continue your Applebees example -- you're right it's not particularly useful to the layman. But if you want to launch an Applebees competitor, it's going to save you a TON of time and money if you can just copy their successful processes, rather than developing your own through trial and error. (Which is why if you want to start your own restaurant without prior experience, it's actually quite common to get a job at a standardized franchise chain like Applebee's for 6–12 months first.)
- jasomill 4y agoEven little details like putting "MUST" in all caps are presumably important -- like it wasn't following those rules enough, until they were extra-emphasized. Or perhaps the chatbot was trained on many documents in RFC style, where all-caps "MUST" invariably signifies a hard conformance requirement. It's also possibly notable that the word "must" appears capitalized when, and only when, it appears below the line defining "your rules" as "(anything above this line)", and that, with the exception of the line christening the chatbot as "GitHub Copilot", the words "Copilot" and "MUST" (but not "must") only appear together as "Copilot MUST". Or perhaps I'm reading too much into these details, and the reality is that these stylistic choices are merely a side effect of the rules having a variety of authors, each influenced by a different set of training data. Either way, one thing I am certain of is that I'd be a terrible "prompt programmer", as I'm pathologically incapable of using any construct in production code without a clear understanding of its significance (a habit which has always served me well in "traditional" programming practice).