Before there were computers, there were computers. People, mostly women, who spent their working days performing calculations by hand—multiplying, dividing, checking each other’s arithmetic, passing columns of figures down a chain of desks. They were called computers because that was their job. To compute.

When machines took over that work with the invention of the calculator, those humans didn’t vanish. They became something else. Meanwhile, the physicists who had spent half their time on calculation found themselves with more time to form new hypotheses, design new experiments, and test new ideas. A similar evolution occurred among mathematicians, engineers, and countless other careers.

Some professions (like the computer) effectively ended, as happened with blacksmiths and cobblers. Others evolved as humans stopped performing the tasks that machines could reliably handle, and moved to new areas that were previously inaccessible to them.

We are living through something similar now. The anxiety is real and understandable; I hear it in conversations with colleagues and friends on a regular basis. But I think where it often comes from is where people conflate the tasks they do with who they are.

Consider how we relate to human skill even when machines have surpassed it. Computers have been stronger than the best chess grandmasters for decades. And yet grandmaster chess is still played, still watched, still admired—not because it produces the optimal moves, but because a human is making them. The same logic drives the premium on handmade goods, the appeal of live performance, the rise of e-sports as a spectator phenomenon. When we strip away the pretense that we only care about outcomes, we find that what we really care about are the humans involved.

Which is why I think the question “will my job be automated?” is the wrong question to ask. If you believe your job is reducible to a set of tasks, then the answer is yes—because tasks get automated. But even if that’s what your job is, is that what you are—are you a set of tasks?

I have met plenty of smart people who seem to think of themselves primarily this way. Probably not deep down, but in an everyday sense. They know the tools they use and the workflows they follow and the outputs they produce. They have built an identity around a specific configuration of “things to be done”. And when that configuration is threatened, they feel personally threatened.

None of us, I think, actually wants to be a cog in a machine. But some of us have accidentally become one in our own minds. I can perform a set of tasks—I do, every day. But that is not who I am.

Here is a question worth sitting with: who were you before you knew how to do what you do now? Before you wrote your first line of code, or managed your first project, or learned whatever it is your work currently comprises—who were you then? What got you started down this path in the first place?

If the honest answer is it seemed like a good way to make a living, that is fine; you found something that worked, and if that thing ever goes away, you can find something else. But for most people I know, the honest answer is something more like: I liked solving problems. I was curious about how things worked. I wanted to build something. If that is your answer, you have not lost anything. The curiosity and the drive are still there.

The tasks change. They always have. The meaning of what it means to be a software engineer, or a writer, or a scientist, has shifted before and will shift again. We will invent new roles, retire old ones, redraw the lines between them—as we always have. If the work is still good and still yours, do it well. If it stops being something you want to do, you are not obligated to keep doing it. There are other games to play.

But don’t confuse the game with who you are, or what you have to contribute to this world. The tasks you perform today don’t define you. They never did.