
LESSON 4
Computers You Can Talk to
Developed by Carl T. Bergstrom and Jevin D. West



Apple Computer (1984)
Apple Computer (1984)
The Macintosh 128K introduced both the mouse and the graphical user interface (GUI) to mass-market computing.
These developments shattered what was then a steep learning curve for computer users.

Before 1984, humans had to communicate with computers in ways that were easy for computers. Programmers and computer users had to adapt their thinking to the machines.
To tell the computer what to do, you had type instructions into a terminal shell.
Users struggled to memorize scores of arcane command and cryptic option flags.
And to keep track of the files on their computers, they had to learn their way around a file tree that there was no way to see.
A UNIX terminal shell
A UNIX terminal shell
The Macintosh 128K reversed that script, allowing humans to communicate with computers in ways that were easier for humans. Learning to work with a graphical user interface wasn't as easy as using plain English to tell the computer what to do, but it was a lot easier than learning to do everything in a terminal shell. It was a compromise of sorts, a middle ground that made computing easier for people by asking a computers to do a bit more.
Giving the computer instructions became as simple as navigating intuitive menus using a mouse, and filling out well-prompted dialog boxes.
And users could now find files by navigating a metaphorical desktop, replete with file drawers, folders, and documents.
The devices we all use today still rely on these basic design metaphors.
The early MacOS desktop
The early MacOS desktop
Large Language Models may propel a similar revolution.
If graphical user interfaces allowed people and computers to meet in the middle, large language models have the potential to bring computers all the way over to our side and let us communicate with them in the way we find most natural: with everyday language.

Let me explain with a story.
My first encounter with a home computer took place in 1979. I was eight years old.
Through a school loan program, my friend Nicholas had borrowed a Commodore PET computer for the weekend. First thing Saturday morning I went to his house to check it out.
Nicholas suggested that we write a game together.
"What do you want to write?"
I was sick of losing quarters at the arcade:
"Let's write Space Invaders, but the aliens don't shoot back!"
Nicolas looked at me with a mixture of exasperation and pity. He tried to explain that this wasn’t the sort of program you could just sit down and write in BASIC, but I didn’t understand.
“Why can’t you just tell it to play space invaders but turn off the shooting?”
What I didn't get at the time was that you couldn't just talk to a computer in natural language. You had to learn to speak its language—and that was really hard.
And for the subsequent forty-some years of my life, that has just been how things are.
Wikimedia Commons
Wikimedia Commons
Atari
Atari
I had to wait nearly half a century, but with the help of an LLM, I can finally have my game of Space Invaders That Don't Shoot Back.

I went to ChatGPT and explained, in plain English, what I wanted.
ChatGPT query 1/3/2025
ChatGPT query 1/3/2025
ChatGPT parses my request, and writes computer code for me.
With a bit of prompting, it even creates images of the space invaders and the player's rocket.
ChatGPT query 1/3/2025
ChatGPT query 1/3/2025
Here's video of us playing the game that ChatGPT wrote for me. Press ►.
PRINCIPLE
Large language models make computing radically more accessible, by allowing untrained users to converse with the machine in their own natural language. Look for places where that ability solves real problems.
DISCUSSION
Large language models make it possible for us to communicate with computers in our natural language instead of learning languages that work for them. What does this allow you to do, right now, you couldn’t do before? What could it make possible in the relatively near future?

VIDEO
Are LLMs as big as the Apple Macintosh revolution—or bigger yet?