Yeah, the people I interact with at work often output similar gibberish when they solve coding tasks. For example, the people who solved the coding task of integrating with the telecoms industry and packaging that up as a REST api called the gateway they built a “twilio”, which as far as I can tell is a nonsense word. :)
More seriously, I think this is a theory of mind issue—the models assume you’ve actually read everything they’ve written (and if you have, their terminology makes sense). Unfortunately those same models often become dirty rotten cheaters who only pretend to have done the thing if they’re confident you haven’t read what they’ve written, so giving the advance instruction of “always provide only the executive summary” doesn’t work how you would hope it would.
Yeah, the people I interact with at work often output similar gibberish when they solve coding tasks. For example, the people who solved the coding task of integrating with the telecoms industry and packaging that up as a REST api called the gateway they built a “twilio”, which as far as I can tell is a nonsense word. :)
More seriously, I think this is a theory of mind issue—the models assume you’ve actually read everything they’ve written (and if you have, their terminology makes sense). Unfortunately those same models often become dirty rotten cheaters who only pretend to have done the thing if they’re confident you haven’t read what they’ve written, so giving the advance instruction of “always provide only the executive summary” doesn’t work how you would hope it would.