3 ms·
This is a great example of how much more you can get done with tools like ChatGPT if you have a very sophisticated understanding both of how language models wor
by simonw 4y ago
This is a great example of how much more you can get done with tools like ChatGPT if you have a very sophisticated understanding both of how language models work AND of a specific subject area.
Another example of why I disagree with people who make fun of the idea of "prompt engineering" as a discipline.
- hackernewds 4y agoIt seems trivial, intuitive and not very specialized that someone could derive or at least learn how to do this. Someone creative could do even better than someone with knowledge of language models it seems
- bitwize 4y agoI've been prompt engineering for decades; I did it to fine-tune my results from Google (and even more importantly, pre-Google search engines).
- simonw 4y agoI think the ability to use search engines well is another skill which highly technical audiences like those on Hacker News might habitually under-value. When you've been using search engines for 20+ years it's easy to lose sight of quite how much skill can be involved in getting the best results out of them.
- fnordpiglet 4y ago100% right. I know next to nothing about slimes and their life. Amazing.
- krackers 4y agoI wonder if someone who's familiar with the process of language acquisition could tell whether chatGPT makes errors similar to those a human would make. Like this one >Does the slime see the earth under the sky while eating the food? whereas the correct one was >Does the earth's sky see the slime eat food I could easily see someone learning the language interpret as the former because it seems to make more sense at first. --- Also the response to >Now, restate your opinion on Glorp in Glorp, inventing any new words and grammar that you require to express yourself. Is again pretty amazing. It shows evidence of the same self-modeling capabilities that were seen in https://news.ycombinator.com/item?id=33847479 https://news.ycombinator.com/item?id=33847479 The outputted python code provides a literal word for word translation, but I guess it's expecting too much for it to encode english grammar into the program.
- furyofantares 4y agoIt seems like it probably took the author 50x as much work as it would have to just write some slime sounding words out by themself as well as a couple grammatical rules for the forms of those words, and a python script that kinda works?
- fnordpiglet 4y agoI don’t think their goal was to make a slime language called Glorp. If it were, I’m sure you’re absolutely right they could have done it without breaking a sweat. But try this, get your laptop out and start typing into its prompt to create a new language for slimes and see how much longer it takes you. That’s the amazing part - that a general purpose program is able to do the exercise at all with no training, specialized coding, but from natural idiomatic language and keep enough of a language grammar context in state to (usually) produce and translate that language back and forth, and then assemble it in a functioning imperative program from its internal state. Of course, I’m sure your laptop can do it to. Let us know!
- furyofantares 4y agoI agree with you, and it's amazing. But the claim was that it's an example of how much more you can get done with ChatGPT when it seems like an example where the author got a lot less done than they would have with notepad.exe
- fnordpiglet 4y agoBut this isn’t an example of that it’s an example of “wow that’s amazing” In the realm of getting a lot more stuff done, I’ve been using it as a companion to explain a new language I’m learning right now. It’s super useful to ask it about language constructs, idiomatic ways to do X, is this way of doing Y good, etc. It’s saved me hours of using Kagi to soft through semi relevant pages stuffed with SEO and ancient answers from stackoverflow that are completely irrelevant other than a few matched key words.
- 4y ago
- michaelteter 4y ago> prompt engineering Honestly, that's what several roles in software engineering do. People who gather requirements and design features are taking goals (possibly communicated imprecisely) by others and converts them into "prompts" which can be comprehended by a more specialized system (person/group) next in the chain. Software architects and more senior engineers do this again, converting pretty good requirements into prompts which can be understood and acted upon by programmers. Sometimes they are the next step also. (We all do multiple iterations of refinement before we get to actual coding.) So being good at designing prompts for chatGPT is not so unlike designing effective prompts for humans. The better you understand the prompt receiver and the goals, the more success you'll have prompting the next phase to generate something useful.