WWII Stories: The Computing War Eighty Years Ago (Part 1)

If you've seen The Imitation Game, you probably remember this picture.

England. Bletchley Park. A group of eccentrics. A young mathematician named Turing. A huge machine. And a line that has since been turned into almost a myth:

Breaking Enigma changed World War II.

That's true, of course. The problem is that it only tells the second half of the story.

Because before Turing walked into Bletchley Park, before the more famous British "bomb" started humming, before Britain turned codebreaking into a full national project, someone had already pushed that door open a crack.

And it wasn't the British.

It was the Poles.

The same Poland that in the autumn of 1939 was caught between Germany and the Soviet Union, torn apart within a few weeks, and often written about since as a tragic supporting character.

But if we're talking not about the front lines but about codebreaking, intelligence and information warfare, Poland was no supporting character at all. It was the lead of the prequel.

───

I. What the Germans really had to fear was more than tanks

Most people, when they talk about WWII, think of blitzkrieg, tanks, and how fast the German army advanced.

Those things are all true. But if you look at it from the Allied point of view at the time, you realize the most frightening thing about the Germans may not have been steel or aircraft. It was their communication system.

Simply put, in the most dangerous years of the war, the German advantage was that they believed every word they sent could not be understood by anyone else.

That was a disaster waiting to happen.

Because in war, the most expensive thing has never been a tank or an aircraft. The most expensive thing is a wrong decision.

Take the Battle of the Atlantic. Britain, an island nation, survived on sea transport. If German submarines worked out the routes of your convoys, you didn't just lose a few ships. You lost the nation's lifeline.

Take the North African front. Why did Rommel struggle more and more as the fighting went on? For a simple reason: fuel shortages. But then, why did his fuel ships keep running into the British "by coincidence"? Was it really just luck for the British navy? Of course not.

Then there's the Normandy landing. Why did the Allies dare to gamble so much? How could they be sure the Germans had been misled by false intelligence? It wasn't because they were gambling. It was because they had really started to see the German cards.

So breaking Enigma looked on the surface like cryptography, but in reality it was a fight over the most expensive thing in war:

Information advantage.

Whoever can read the enemy's communications avoids the most costly mistakes. And whoever avoids mistakes can put money, ships, fuel, time and troops where they matter most.

So what's truly terrifying about Enigma isn't that "it was a cipher machine." It's that it was the lock on the outside of the Third Reich's nervous system.

───

II. Why Enigma was so terrifying

Many people today know the name Enigma. But if you think of it only as "an old cipher machine," you're underestimating it.

What made it truly frightening wasn't just its complexity. It was how cleverly it was designed.

On the surface, it was very simple. You pressed a letter, say A, and the machine lit up another letter, say X. You wrote down X and sent it. On the other end, a machine set up the same way would take X and turn it back into A.

Sounds like a children's cipher game, right? The problem is that it doesn't work that way inside.

Inside, there were rotors, a reflector, and a plugboard. Every time you pressed a key, the internal structure moved. In other words, the same input did not always produce the same output.

Press A today and you get X. Press A a second later and it may no longer be X.

What does that mean?

It means Enigma wasn't a lock. It was a lock that changed its own combination every time you pressed a key.

Even more vicious, the Germans had a very harsh rule:

Every day at midnight, the whole army changed its settings.

That created a truly hopeless situation.

You spent a lot of effort finally finding some pattern. At twelve o'clock, it's all void. Yesterday's clues couldn't be carried over, and yesterday's work couldn't be reused. The next morning, you woke up to face a fresh maze.

So the most terrifying thing about Enigma wasn't just "too many combinations." It was that it made traditional codebreaking methods almost completely useless.

Guessing words wasn't enough. Language intuition wasn't enough. Yesterday's experience wasn't enough either.

It didn't just give you a headache. It drove you to despair.

───

III. The English and French did get clues first, but still couldn't break it

Here's a particularly dramatic detail.

The first to get hold of material related to the German cipher system was not Poland. French intelligence had obtained important information about Enigma through spies quite early on.

The British and French also didn't hold back. They brought in many of the smartest people they could find: cryptographers, linguists, classicists, and even people who were very good at spotting patterns.

On paper, that lineup was already strong. But after studying it for a long time, they reached a very discouraging conclusion:

It's too hard. It's almost impossible.

What was the problem?

It wasn't that they weren't clever. It was that they were looking at the wrong problem.

They treated Enigma as a language problem. They tried to find words in the letters, sentences in the words, and patterns in the sentences.

But the person who first saw through the problem realized something crucial:

This isn't a language problem. It's a math problem.

That person was the Polish mathematician Marian Rejewski.

───

IV. Why Poland was the one to see it first

There's a cruel reality behind this too.

The British and French could afford to study failure. Poland couldn't.

Britain was across the Channel. France, however weak, still had a buffer. They were certainly afraid of Germany, but they weren't yet at the point where "if we can't crack this today, we'll be conquered tomorrow."

Poland was different. Poland sat right on Germany's border. For Poland, not understanding what the Germans were saying was not an academic regret. It was a matter of life and death.

Poland had no right to trial and error. It couldn't afford to spend too long on the wrong method, the way Britain and France could.

So the Polish cipher bureau made a crucial decision:

If the linguists can't do it, switch to mathematicians.

So they recruited three young men:

• Marian Rejewski • Jerzy Różycki • Henryk Zygalski

These three would later become the names that most deserve to be remembered from the prehistory of the codebreaking war.

───

V. Rejewski's real greatness was admitting everyone had been asking the wrong question

What made Rejewski remarkable was not that he was "a little smarter." It was that he made a crucial reversal first.

Others saw gibberish. He saw structure.

Others were still guessing words. He had already started looking at the permutations, cycles and mappings between letters.

To him, Enigma was not German, not a message, not a sentence. It was a system that could be described mathematically.

That step was enormously important.

Because many problems that look unsolvable aren't without answers. They just have answers that you can't reach because you're asking the wrong questions.

The experts from Britain and France were still "reading letters." Rejewski had started "reading the machine."

He was the first to realize:

Enigma couldn't be solved by people slowly guessing. It had to be modeled, reverse-engineered, and handled by machines.

From that moment on, everything changed.

───

VI. Before Turing's "Bombe," Poland had already built its own "bomb"

Later, when people talk about The Imitation Game, they remember Turing and Britain's "Bombe."

But earlier, the Poles had already built their own Bomba.

It wasn't a general-purpose computer by today's standards. But it was already very close to what we'd understand as a special-purpose computing machine.

It existed for one purpose:

To hand off the combinations that a human brain could never test by hand to a machine.

This matters a great deal.

Because it shows the Poles didn't just understand the problem "in theory." They had already started turning it into an engineering problem.

In other words, the Poles not only understood the question first. They also realized early on:

A problem of this scale can't be solved by intelligence alone. You need machines too.

Put simply, they had already caught the scent of the computing war.

And this is exactly what makes the Polish story so tragic. They understood it too early, but their country was not strong enough to carry the path all the way through.

───

VII. The real cruelty: they were close to success, while the country was close to collapse

If the story stopped here, it would already be legendary enough. But the most painful part of Poland's history is what came afterward.

In 1938 and 1939, Germany upgraded Enigma. The complexity went up.

Poland naturally tried to keep up. The problem wasn't that they couldn't. The problem was that they couldn't sustain it.

It's like a small team that got the algorithm right and bet on the right technical path, but when it came to the stage of building machines, scaling up and investing continuously, the cash flow ran out.

They had already found the answer. But the country was almost gone.

That is the most painful part of this story. It wasn't a lack of skill. It was a lack of national strength.

举