Transcript
The boring state of artificial intelligence
Synthetic voices · A dialogue adaptation of this article, not a verbatim reading.
01A bet at work
Narrator: A colleague bet I'd fall for the AI hype within six months. Slightly delusional colleague. I responded with a blog post. Several thousand words. He probably just wanted to finish his lunch.
Maya: Was a simple 'no' available?
Narrator: Apparently not. I'm Khalil. This is Maya. And we're going back to April seventeenth, twenty twenty-three, when I wrote The boring state of artificial intelligence.
Maya: Back to those models, those experiments. I want that on the record before you start predicting the future.
Narrator: Fair. I'd been working in data science and engineering for about six years. Enough to have questions. Also enough to get very attached to my own answers. You'll hear some of that.
Maya: All right. Let's see what annoyed you enough to interrupt lunch.
This part of the article02The hype
Narrator: First diagnosis: Wikipedia scientist syndrome. You read two articles, develop three opinions, and suddenly you're qualified to supervise the future of civilization.
Maya: Only two articles? I've been overtraining.
Narrator: Reading matters. But reading about painting doesn't teach your hand to paint. You have to draw, fail, notice why, and try again. The problem gets louder when shallow certainty comes with a very large audience.
Maya: Have you tried the thing before explaining it to everyone?
Narrator: That would help. Then there's the other habit: a demo works, and suddenly we're discussing sentience. Flying cars! The end of work! Meanwhile, my actual car is still in traffic.
Maya: And your own certainty?
Narrator: Oh, inspect mine too. I have several thousand words of evidence. Take the opinions with salt. Keep a glass of water nearby.
This part of the article03What is AI?
Narrator: Let's give ourselves something small enough to understand. In this article, I'm mostly talking about neural networks. Under suitable conditions, they're universal approximators. That's the universal approximation theorem, with foundational work by George Cybenko, and by Kurt Hornik, Maxwell Stinchcombe and Halbert White, in 1989. Definitely not something I came up with.
Maya: That's it? The robot uprising is a function?
Narrator: With suitable activation functions and enough capacity, a network can approximate continuous functions on a closed, bounded domain as closely as we like. That doesn't guarantee training will find the right answer. Start with inputs and outputs: the network learns a relationship between them. We'll try it with two numbers in a minute.
Maya: Good, because universal sounds suspiciously like it comes with a lifetime warranty.
Narrator: No warranty. And for the art discussion, I'm mostly looking at two-dimensional images. Otherwise we'll still be here tomorrow.
This part of the article04The artist
Narrator: Let's start with art. My three ingredients were technical skill, creativity, and control. Technical skill includes lighting, color, composition, form, and anatomy. All the quiet decisions that make an image work.
Maya: I know where this is going. Hands.
Narrator: Hands. Beautiful portrait, lovely light, one finger doing something deeply independent. That's all anyone sees. Now, an artist can distort anatomy deliberately. But knowing what you're changing makes a difference.
Maya: You can break the rules on purpose. You still need to know where they were.
Narrator: Look at Michelangelo's anatomical studies in the article. There's so much patient observation there. That's the part I wanted to talk about: all the work behind being able to choose what goes on the page.
This part of the article05Creativity and control
Maya: Technical skill is one ingredient. What do creativity and control add?
Narrator: Creativity brings your imagination and your taste. Control lets you put them into the image. Move the light a little. Change the posture. Make the room feel uncomfortable, although nothing obviously terrible is happening.
Maya: So a happy accident is welcome. It just shouldn't be the entire management team.
Narrator: Look at Piotr Jablonski's work here, then Alfred Broge's Morning Sunlight. One feels unsettling. The other gives you this quiet, sunlit room. The lighting and composition help create those feelings.
Maya: One makes you admire the light. The other makes you check whether something is standing behind you.
Narrator: And they get there by choosing what matters in each picture. Which makes grading the machine a little awkward.
This part of the article06Evaluating Midjourney
Narrator: Could Midjourney be an artist? My article initially says yes, and then spends quite a while arguing with itself. What impressed me was the lighting, color, and composition of its images.
Maya: You wrote both sides of the argument? Efficient.
Narrator: I guessed at parts of the training process too: curated images, loss functions. Guesses. I didn't have access to Midjourney's internals. What I could see was lovely lighting alongside anatomy and structure that sometimes fell apart.
Maya: And imagination? Surely artists also learn from things they've seen.
Narrator: They do. I described that as a visual library. Artists study animals, objects, light, and scenery, then combine and transform what they've learned. An image model has an enormous collection of learned visual patterns to work with.
Maya: Then I'm still stuck on intention. Who decides what the picture is trying to do?
Narrator: The person using it brings that intention. I could see a remarkable tool for trying out ideas. Calling the model itself an artist, with a purpose of its own... that's where I hesitated. Other people can reasonably draw that line elsewhere.
This part of the article07Artistic choices
Narrator: Look at Nathan Fawkes. He can simplify structure and give all that attention to color and light. Steve Huston might put anatomy and gesture at the center. You don't have to demonstrate every skill in every painting.
Maya: So your three-ingredient recipe isn't a spreadsheet for giving paintings a performance review.
Narrator: Please don't give paintings quarterly targets. The point is choice. An artist can leave a detail out because it doesn't serve the work. That differs from losing the detail because the system didn't hold it together.
Maya: Okay, I see what you're getting at. Did you choose to leave it out, or could you not make it work?
Narrator: That's what I wanted to ask. A beautiful result alone doesn't answer it. Now, about intelligence. Surely we'll agree on that in thirty seconds.
Maya: I'll cancel my afternoon.
This part of the article08Sparks of AGI?
Narrator: The essay responds to Sparks of Artificial General Intelligence, the early GPT-four experiments. Instead of treating intelligence as one agreed score, I proposed a working definition: using existing information in new ways, and extending what we know.
Maya: Your working definition. I'm keeping a pencil next to it.
Narrator: Please do. Think about fire. You notice it. Then you learn to control it, cook with it, use it for something you couldn't do before. That's the kind of step I was interested in.
Maya: Humanity: sees a dangerous burning object, asks whether dinner could be improved.
Narrator: Dinner is a strong research incentive. The diagram here draws possible information as a big space, human knowledge as a region inside it, and individuals as little dots. It's a sketch to think with. I haven't measured anybody's brain.
Maya: So show me a small version. What does learning actually look like?
This part of the article09A simple neural network
Narrator: Let's build the world's least threatening AI. Two numbers go in. Their sum comes out. At first, the network's adjustable weights aren't set to produce the answer we want.
Maya: Two numbers. Good. I can supervise.
Narrator: We supply examples with known answers. The network makes a prediction. A loss function measures how far that prediction is from the target. Training adjusts the weights to reduce that error across the examples.
Maya: So 'loss' is just a measure of the mistake. Nobody inside the laptop is having a bad day.
Narrator: Correct. Now ask it to multiply. We trained this little setup for addition; multiplication wasn't part of the job. We need to specify the operation and train for that too. Doing well on our examples doesn't promise it will handle every new input.
Maya: I may have promoted it too early.
Narrator: Universal approximation tells us what suitable networks can represent under certain assumptions. It doesn't promise that this network, with this training, learns the right thing. Also, I got bored of drawing the diagrams at this point. The next one exists in spirit.
This part of the article10A calculator that talks
Narrator: Now we change the interface. Instead of entering two numbers, we ask, could you please add twelve and thirty-five? The answer comes back as a sentence. Forty-seven, with excellent manners.
Maya: Does saying please improve the arithmetic?
Narrator: It improves the atmosphere. My argument was that a language interface is useful even without treating it as proof of general intelligence. You can bring summarization, translation, classification, and other tasks behind the same conversational doorway.
Maya: I'd still use that. I spend half my day finding the right menu.
Narrator: Me too. That's useful. Then there's the confident wrong answer. I suggested interference inside networks as an explanation in the essay, but that was an intuition. It doesn't explain every hallucination.
Maya: Let's give the very polite calculator a calculation.
This part of the article11Let’s try some arithmetic
Narrator: The screenshots here are from the March twenty-third version of ChatGPT in twenty twenty-three. I gave it a long decimal addition problem. It got the result wrong. Then I simplified the operation and tried again in a fresh session.
Maya: Go on. Did it get the answer?
Narrator: It got it wrong. Confidently. The screenshots have the exact decimals; I'll spare you the audio version of a bank statement. I tried a simpler operation as well. Still, the explanation sounded much better than the arithmetic.
Maya: But a wrong answer doesn't tell you, by itself, why the model was wrong.
Narrator: Right. I blamed things like overfitting and limited reasoning. A few screenshots don't establish those causes. What we can do is check the answer, change the problem, and see whether it still works.
Maya: Please check before the bow. The bow makes it worse.
This part of the article12A banana, a guitar, and a Strogbunroftak
Narrator: Next, a nose, a guitar, a banana, a chinchilla, and a Strogbunroftak. I asked a stacking question. The reply wandered into ethics, banana-related insects, and concern for a creature whose name I'd made up.
Maya: Ooh. What's a Strogbunroftak?
Narrator: I made it up.
Maya: And it was worried about it? That's rather sweet.
Narrator: Sweet, yes. Useful... less so. It had filled in a whole situation I hadn't described. My question got buried under advice about that invented situation.
Maya: It could have asked me what the word meant. I'd quite like to know too.
Narrator: A small 'I don't know' would have saved everyone a lot of banana-related concern.
This part of the article13Predicting the next word
Narrator: Underneath this conversation is next-token prediction. A token is a chunk of text, sometimes a word, sometimes part of one. The model generates a continuation from the context, then continues from that larger context.
Maya: It's choosing what could come next. Where does checking the facts happen?
Narrator: That prediction alone isn't a fact check. The training text includes reliable claims, mistakes, opinions, all sorts. You can get a very convincing continuation that's false. That's what my simplified examples were trying to show.
Maya: And there's more to the finished chatbot than that one step, of course.
Narrator: Yes. The original article says so too. Then it brings back my Wikipedia scientist joke. I seem to have learned one pattern particularly well.
Maya: At least you remembered your source.
This part of the article14The age problem
Narrator: Next came a father-and-son age problem. The initial answer looked impressive. So naturally I declared humanity doomed, then made the question a little more complicated.
Maya: Before lunch again?
Narrator: The later answers were less convincing. I tried a fresh session too. The screenshots matter because the argument isn't just that the text sounds intelligent. It's whether the relationships in the problem stay consistent when the setup changes.
Maya: Change one condition. See if the family ages still make sense. I can follow that test.
Narrator: And keep the conclusion tied to the test. I was broader, and more skeptical, in the article. Those screenshots tell us what that version did on those questions. They can't answer for every future model.
This part of the article15The information domain
Narrator: This leads to the information domain. With a narrow model, its boundaries are obvious: it summarizes text, for example. With a chatbot that answers almost anything, the boundary is harder to see.
Maya: You can ask it almost anything. It's hard to tell when you've walked past what it can handle.
Narrator: Yes. I called that its information domain. I was trying to distinguish combining patterns it had learned from extending knowledge. The image styles and the little arithmetic network were my way into that question.
Maya: But you can't find the exact boundary from those few examples.
Narrator: No. And when I wrote that models could 'never' do certain things, I went further than those examples justified. Give them a new situation. See what transfers. That's a question we can test.
Maya: I'd keep 'never' in pencil too. We're getting through a lot of pencils.
This part of the article16Cats and chocolate
Narrator: To explore combining ideas, I asked for a poem about two things I love: cats and chocolate. I expected charm. I received something considerably darker.
Maya: Oh no. Cats and chocolate. I can already hear the warning.
Narrator: I wasn't giving chocolate to a cat! I wanted a poem. But the answer seemed to follow that familiar warning instead of the mood I was asking for.
Maya: It found the association. Missed the occasion.
Narrator: Then I went back to fire. Suppose a model only had information from before we discovered it. Could it reach cooking? I didn't run that experiment; I was asking where a new discovery comes from. How far can combining what you know take you?
Maya: For the next poem, could we try cats and fish? Give the poor thing a chance.
This part of the article17Outside the dataset
Narrator: The stakes become less funny outside the dataset. A driving system trained in one setting may struggle with different roads and habits. A face-recognition system can perform unevenly when its data represents some people much better than others.
Maya: Which people and situations did the examples leave out?
Narrator: That's the question. I also pushed back on 'humans use eyes, so cameras are enough to drive like a human.' That skips a lot. I wanted the discussion to take perception and other sources of information seriously.
Maya: Then test the actual car, in the actual conditions. The analogy won't drive it home.
Narrator: And ask who carries the cost when it fails. A system working beautifully for one group tells you very little about someone the evaluation left out. That deserves time and careful testing.
This part of the article18A tool to augment us
Maya: I have to ask. Is there anything here you actually like?
Narrator: Yes! Terrible news for my title. Tell a computer what you need, in normal language, and have it help you do it. Less time remembering which application hides the button.
Maya: You'd miss hunting through six menus?
Narrator: I'd recover. There are plenty of repetitive jobs I'd happily hand over. Doing them isn't what makes me intelligent, or makes the work meaningful. I'd rather spend that time making something I care about.
Maya: And changing people's jobs still has consequences. Even when the tool is useful.
Narrator: Of course. I want useful tools and an honest conversation about what changes. That's where I was trying to get, underneath all the complaining.
This part of the article19Conclusion
Narrator: I ended up imagining an operating system you could talk to. Describe what you need, have it work across the applications. That was one direction I was excited about.
Maya: Plus a few predictions. You did have room left on the internet.
Narrator: A few. I questioned scale alone as a route to intelligence, wondered about Epic Games and three-dimensional generation, and pointed to AlphaTensor, AlphaCode, and Segment Anything. Those were things I wanted to watch in April twenty twenty-three.
Maya: We'll leave the predictions as you wrote them. No quietly correcting the exam after getting it back.
Narrator: Agreed. Which leaves the goat playing a guitar at the end. An impressive performance. Quite a lot still to ask before declaring it a musician.
Maya: Let it finish the solo first.
Narrator: Fair. Thanks for spending the time with us. The original experiments and images are there if you want a closer look. And if you disagree, pick a particular claim. That's where the interesting conversation starts.
Maya: One particular claim, then. Did your colleague win the bet?
Narrator: I didn't put the result in the article. After all those words... I left out the result.
This part of the article20Until next time
Narrator: Thanks for listening. Follow along for more articles, experiments, and things that worked on my machine.
Maya: Some of them might even work on yours.
Narrator: No promises. Have a lovely day. Go make something.
Maya: Preferably a cup of tea first. Bye!