Urgent.News

What's breaking now, across thousands of outlets.

AI

How to talk about "AI" without adding to the anthropomorphization

Very good to use for documentation of systems and tasks Comments

Our recent op-ed for Tech Policy Press highlighted the need to reevaluate the language we use when discussing AI technologies. Anthropomorphizing language, which imbues computer systems with human-like qualities, can hinder clear communication about the actual capabilities and limitations of AI. To tackle this issue, our research has focused on three key steps: identifying various forms of anthropomorphizing language, categorizing them, and proposing de-anthropomorphized alternatives.

De-anthropomorphizing language emphasizes the functionality and purpose of computer systems, rather than attributing human-like characteristics or emotions to them. By describing algorithms as performing calculations or other operations and highlighting the role of people using the systems, we can foster clearer discussions about the actual impact of AI technologies.

Examples of de-anthropomorphized language include "artificial intelligence" replaced with "probabilistic automation," "image recognition" with "image labeling," and "chatbots" with "conversation simulators."

In addition to these language changes, it is essential to recognize that AI systems do not possess emotions or consciousness. Phrases that suggest AI has feelings or experiences should be avoided, as they can obscure the limitations and potential risks associated with these technologies. The term "AI agent" should also be replaced with "probabilistic, unverified software manipulator," which better reflects the nature of these systems and their limitations.

By adopting these de-anthropomorphized language practices, we can promote more accurate and productive conversations about AI technologies, their capabilities, and their limitations.

Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at buttondown.com →

More in AI

The Leftover Hard Parts

Some time ago, I asked an AI to write a fairly boring piece of code. It did a pretty good job. I changed a few things, ran the tests, and voila: I was looking at something that probably would have…

  • AI-assisted coding generates nearly complete code, but leaves hidden "leftover hard part".
  • Developers must investigate and understand remaining 10% of AI-generated code.
  • AI shifts responsibility to developers, who must make trade-offs and communicate decisions.

AI Is Making Code Cheap. Verification Is Becoming the Expensive Part

Anthropic published a post about their CI infrastructure that I keep coming back to. The headline number is that Claude writes 80% of their code. That's the part everyone quoted.

  • AI generates 80% of code but verification becomes expensive
  • Test suite shifts from gate to signal in development loop
  • Quality responsibility moves up stack, AI tests must be high-quality

More from Tuesday 22 September →