3 ms·
...or no UX, use these systems in the backend with well crafted prompts and abstract the need to instruct LLMs away from the user?
by cloudking 2y ago
...or no UX, use these systems in the backend with well crafted prompts and abstract the need to instruct LLMs away from the user?
- blharr 2y agoI believe what you are describing is exactly the type of UX that the parent comment may have been calling for
- cloudking 2y agoMakes sense, my biggest takeaway from observing folks in many different roles interact with LLMs is this: they simply don't know how to prompt effectively. There is no problem with the chat UX, if you know the right techniques to get optimal output, but writing effective prompts is a technical skill similar to programming - most folks that interact with computers are not highly technical. If we design software powered by LLMs understanding that effective prompting is a skill most users don't have, then we should build UX that abstracts prompting away. Of course there are going to be use cases where a user needs to provide input to the LLM, but that UX also can be assistive and require minimal cognitive overhead (e.g less raw text prompt input, more clicks on buttons/forms etc to a backend prompt builder).