Epilogue

What Comes After the Answer

A learner pulls out a chair for someone joining a shared library table, with the prairie beyond.

My dad didn’t need ChatGPT to become interested in the geology of North Dakota. He was already fascinated by the glaciers that shaped the land he farmed and left behind the rocks he had to pull out of the ground. When I called him in 2023, I was excited about a new way he could explore something he already cared about. The technology was new. His curiosity wasn’t.

Looking back across these essays, I realize how often I’ve returned to some version of that conversation. Someone has a question, an idea, or a frustration. A tool makes something possible that wasn’t possible for them before. They try it, and for a moment, their understanding of what they can do expands. I felt that when I heard my old lyrics become a song. I felt it when I started describing websites and watching them take shape. Those moments are still exciting to me. I don’t want to become so accustomed to them that I forget what they felt like.

But the moment when something becomes possible is only the beginning of the story. Hearing a song doesn’t settle what AI means for the musicians whose work helped make that technology possible. Generating a website doesn’t tell us whether anyone needs it. Getting an answer doesn’t tell us whether we should believe it. The first impressive result gives us something to work with. What happens afterward asks more of us.

That’s where my thinking has changed most. In the earlier essays, I was often making the case for access: give people these tools, help them understand how to use them, and imagine what they might accomplish. I still believe in that opportunity. However, teaching alongside faculty and talking with students have made me much more interested in the distance between producing something and understanding what you’ve produced.

The student who wanted to help her mother run a hairstyling business brought that distance into focus. She could start building almost immediately. Yet the most useful thing I could suggest was a conversation with her mom. How did she actually manage appointments? What frustrated her? Why hadn’t she adopted one of the services that already existed? The answers could change the entire project. They might even reveal that a new application wasn’t needed. That would be a discovery worth making, too.

I think this is one of the stranger lessons of learning with increasingly capable machines. They can make it easier to skip the very experiences that would help us become more capable ourselves. We can get the report without reading the sources, build the prototype without understanding the problem, or produce a convincing explanation of something we still couldn’t explain to another person. The result can look finished while our understanding has barely begun.

So, what would I want you to carry out of this book? A willingness to stay involved. Follow the source. Listen to the song. Watch someone try the thing you made. Ask why the result surprised you, and give yourself permission to change your mind. Over time, those experiences give you something that another generated answer cannot hand you fully formed: a sense of what matters, what works, and what deserves more attention.

That applies to my writing, too. You’ve read essays in which I sound certain that an enormous change is coming, and others in which I’m trying to figure out what happened in a classroom. I’ve followed forecasts that are difficult to assess and tools that made a possibility feel real in a matter of minutes. Bringing those experiences together hasn’t given me a final answer about where AI is going. It has made me more aware of how much depends on the questions we ask and the evidence we’re willing to take seriously, including evidence that complicates a story we want to believe.

I remain excited about what these systems could help people do. I’m also concerned about who gets displaced, whose work gets used, who has a say, and what happens when powerful systems are deployed before their consequences are understood. Learning to use AI well doesn’t resolve those questions. A workshop cannot repair a broken career ladder, and a better prompt cannot substitute for public accountability. Schools, libraries, employers, governments, and the companies building these systems all have responsibilities that reach beyond an individual’s ability to keep up.

This is why I keep coming back to libraries. When I write about an imagination lab or an intelligent university, I’m thinking about the person who wouldn’t otherwise have access to the tools, the guidance, or even the invitation to try. I benefited from people who put computers in a small North Dakota school and decided that kids like me should learn to use them. At the time, I mostly wanted to blow up my Kid Pix drawing with the dynamite eraser. I didn’t understand the opportunity being placed in front of me. Someone else had to imagine that first.

Today, I want more people to have that chance. An educator or librarian may be the person who helps a student recognize an interest as something worth pursuing. A colleague may show someone a different way to approach a task. A friend may listen to an idea long enough for it to become clearer. These encounters are easy to overlook when the conversation is dominated by model releases, investment announcements, and predictions about the end of work. Yet they shape what people believe they are allowed to attempt.

If you’re learning on your own, your starting point doesn’t have to impress anyone. You can investigate a place you’ve always wondered about, make something that amuses your friends, or return to an interest you put aside years ago. A song doesn’t need to become a hit to matter to the person who wanted to hear it. A project doesn’t need to become a startup to teach you something. Give yourself enough room to explore before deciding what the experience has to become.

And if you’re helping others learn, leave that room for them, too. I went into teaching AI fluency expecting to spend more time explaining the tools. The students helped me see how much of the work involved listening, asking questions, and figuring out the next step together. I expect they’ll keep changing my mind. Being their guide doesn’t require me to know the ending of every project before they begin.

My dad wanted to understand the ground beneath his feet. I wanted to hear a song I thought I would never hear. A student wanted to help her mother. These are modest beginnings compared with the futures promised in the headlines, but they give those futures a place to meet an actual human life. That’s where I want to leave you: with something you care enough about to explore, and a reason to stay with it after the first answer appears. Find out what it takes. See what you learn. And when someone else wonders whether any of this could be for them, make room beside you.