The Imitation Game

I watched The Imitation Game on a cold Saturday evening in a cinema that was nearly empty by the time the credits appeared.

I had spent much of the day at a computer, which should have made codebreaking an unattractive choice for entertainment. Instead, the darkness of the cinema separated computing from work. No editor, compiler or unfinished task was waiting. There was only a story about people trying to make a machine do something that seemed to require human intelligence.

I already knew Alan Turing’s name.

That was part of the problem.

In computer science, some names are repeated so often that they stop sounding like names. Turing machine. Turing test. Computability. The surname becomes technical vocabulary.

The film returned a person to the word.

I do not treat it as a documentary. Historical films compress, combine and rearrange events. The point that stayed with me was less factual than psychological.

Difficult work can be lonely long before it becomes important.

There is a romantic story of invention in which the brilliant idea arrives, the inventor recognizes it, and history eventually catches up. Real technical work contains longer periods when nobody knows whether the idea will work. The machine looks useless. The experiment fails. Colleagues lose patience. Another week of effort cannot be justified with certainty.

I recognize a tiny version of this feeling in programming.

You can spend an afternoon repairing something invisible. At the end, the software appears exactly as it did in the morning except one rare failure no longer occurs.

Nobody notices.

The absence of the problem is the result.

Wartime cryptanalysis belongs to another moral and historical scale, but the shape of patience is recognizable.

The film also made secrecy feel strange. Modern technical culture usually rewards visibility. Publish the code, write the paper, present the result, attach names to achievements.

At Bletchley Park, success often had to remain hidden in order to remain useful.

Imagine solving something important and understanding that recognition would damage the work.

That is an unfamiliar form of accomplishment.

Turing’s later treatment by the society he helped serve prevents the story from remaining comfortably about computing. A society can depend on a person’s mind while refusing to accept the person who owns it.

That contradiction stayed with me longer than the machinery.

We teach technical history as a sequence of achievements because courses require structure. A theorem, a model, a machine, a language.

Human lives resist that organization.

After leaving the cinema, I walked for a while before going home. I remember thinking about names in textbooks.

A name printed beside a theorem looks settled, as if history has completed the account.

Sometimes the surname survives more comfortably than the person ever lived.

After the film, “Turing” sounded less like terminology to me.