Skip to main content

Are LLMs training us?

Almost every discussion about using LLMs seems to eventually leads to people mentioning they ways they've adjusted their writing style, prompting style and expectations to get the most out of their LLM.

So it makes me wonder if the LLMs training us as we are training them as there is plenty of precedent for new communications media creating new rules for communication. 

From smileys to emoji


Back in college when I was just starting to use email to contact people I noticed that sometimes people used smileys at the end of a subject or at the end of an email to suggest that something was being said in as a joke. These were sometimes modified with other ascii characters. An O to suggest a halo when you claim you're innocent or an & replacing the ) to suggest you're tongue tied. Eventually, smileys would be added to subjects or to the first line of an email as a hint that there would be something funny in the email. Smileys became a new form of punctuation that were only used in email and chat communication. I don't think I ever saw them in print.

Then emoji came along. At first, people used them exactly how smileys were used, as punctuation. But then they started to be used as adjectives and adverbs. Sending someone a chat message of "Let's meet up" could be followed a few different ways
  • Let's meet up πŸ•ΊπŸΈ
  • Let's meet up ☕️ πŸ₯―
  • Let's meet up 🍿πŸŽ₯
In each case, the emoji are used as part of the message to express, in a collection of images, what might have taken a many more words. And it isn't hard to see those eventually evolve into just sending the emoji when you have a relationship where a lot of the context could be gathered from the last exchange you had.
  • πŸ•ΊπŸΈ
  • ☕️ πŸ₯―
  • 🍿πŸŽ₯

So how are people communicating with LLMs?

LLM power users all have their own way of building prompts that seem to converge on a basic format.
  1. Act as a or You are a to set how the LLM should respond
  2. Build/Construct/Create/Reply statement that describes the basic expectation
    1. Refinements as positive or negative restrictions
    2. Details and edge cases
    3. Rules if this is to be a draft or template for manual refinement
    4. Acceptance criterias, must mention energy use as example
  3. Output expectations 
    1. Size and scope
    2. Tone and voice, either argument for or balanced discussion
Common variations seem to be breaking the request into a chain of related refinements, what I describe as Improv coding as they coincidentally follow the basic rules of Improv, embracing Yes, And and making statements. All of these show up in more modern guides to writing better prompts. 

This looks to me like a natural language variation of a 4GL and it seems like a natural refinement of the first guide on prompting I read a few year back. Its largely an organic response to what works from using LLMs. So, did the LLMs train us to be better prompters?









Comments

Popular posts from this blog

Capturing text from any Mac Application into Emacs org-mode with Automator and org-protocol

After decades of using vi and Vim I switched to  Spacemacs  which is an amazing vi keystroke emulation layer running on Emacs and configured with an amazing set of preconfigured layers for different tasks. I decided to give it a try after seeing Org-Mode in action and seeing it was a nice taking system with integrations with almost anything imaginable. A few weeks ago I found out about org-protocol and followed this post  by Jethro on using a bookmarket to capture from the Web to Emacs.  This page assumes a few things You use Emacs on a Mac You are using org and understand how to use capture and capture templates. You need to yank text from random apps into Emacs You don't need to be using Spacemacs and this should work with any install of Emacs that supports org, org-capture and org-protocol. Creating Automator Action Start Automator. It's this icon. I'm guessing many people have had this for years and have never used it.  Open it and pick Quick Action Grab the...

Halloween Candy Distribution Robot Chute

I am not a hardware guy and my Brooklyn apartment lacks true workshop space but we were able to put together a reasonably well done candy chute robot able to deliver candy directly into Trick-or-Treat's candy bags.  My wife wanted the robot to blink lights and wave an arm. I decided to use a servo motor driven by a Raspberry pi pico running MicroPython. The pico and MicroPython were chosen because I had them already from prior projects with my son.  Legos, chopsticks and leftover screws. Only the best. Cardboard, aluminum foil and Tupperware to protect the electronics. Those are the bags of candy and we managed to go through all of the candy by dark. This is what it looked like up on our balcony. How do you get the candy down to the trick-or-treaters? A dryer duct. Last time we used plastic sheeting and zip ties. The $25 to get a duct was worth it. We tested it with fun sized chocolate, smarties, double bubble gum, skittles and m&ms. The bagged candy, skittles and M...

LinkedIn should have an introduction feature

I have been spending more time on LinkedIn the past couple of months and every time I want to facilitate an introduction between people I find myself thinking there should be a better way to do it. It's somewhat annoying that a platform for networking lacks a way to link people in.   Right now, LinkedIn lets you message a person and include in that message, a third person's contact. This would be ok as an introduction but it lacks what I think are two important features that should be part of LinkedIn's communication options-protection of the privacy and seeking the consent of the two people being introduced.  As an example, let's say I wanted to introduce a student I know named Adam to a business strategist who is looking for a part time worker. We'll call him Bob . I know Bob will find Adam to be the perfect fit-a motivated communications student at a local school who is looking for a part time summer gig. Starting from Bob's profile, I would pick the more op...