More Than the Answer

Early in my IT career, I worked with a guy who had developed a very complex database design.
I needed to understand it. He didn’t have much time to teach it to me, so I started digging into it myself.

I read everything I could find. I’d learn something, go back to the design, understand a little more, find something else I didn’t understand and go back to the books.

Eventually, something changed.

I wasn’t just following his design anymore. I understood why it worked. I could question parts of it, contribute ideas and eventually work with it at the same level he could.

But something else happened too.

He recognized that I understood what he had built. I respected what he knew. He respected what I had learned. We started bouncing ideas off each other and actively helping one another.

I started with one objective: understand the database design.

I got considerably more than that.

I’ve been thinking about that experience as AI makes knowledge dramatically easier to access.

Today, I could probably go through much of that same learning process faster. I could ask AI to explain a concept I didn’t understand, challenge it with questions, dig deeper into one part of the design and keep going until the pieces started fitting together.

That’s an extraordinary advantage.

But it also makes an important distinction easier to overlook.

Knowledge and understanding aren’t the same thing.

We can know the facts, know the terminology and know enough to have a conversation about a subject without really understanding how the pieces fit together or why they work the way they do.

Not everything requires deep understanding. Sometimes we just need an answer.

AI can give us the knowledge. But when it matters, we still have to do the work of understanding it.

– John