> "Ask" it about [...] sound plausible. Yeah, that's because the API is /completions not /answers. We, as devs, need to know what we can do with text completi

> "Ask" it about [...] sound plausible. Yeah, that's because the API is /completions not /answers. We, as devs, need to know what we can do with text completion and what it's not good for. > But for anything that's hard and matters, it's a parlor trick unfit for use. Sure, you can't just ask it to synthesize a new drug and cite relevant sources. But you can ask it to take a text like "the guy with the red house rides a bike, ... who has solar panels?" and spit out a testable proof if your language of choice. Sure, you then have to pass that to Wolfram, or Heroku, but so? You can have it summarize a list of product differences, but focusing only on physical UI issues, and making it clear to only summarize, not extrapolate, from the sources you provide. You can have it take unclear and incorrectly written free-form user input and select from a list of intentions, what the user most-likely wants to do and write an explanatory log-line, or flagging a user for more direct QA oversight and maybe help.