[Don Joe]

"Who comes up with these names? Come on, say what you mean."

Frankly, I wish for a return to the good old days where a code name meant something nothing. The software companies "get it". The purpose of a code name is to leave the enemy guessing. For example, Windows 95's code name was "Chicago". VB 1.0 was "Thunder", the Pro component kit was "Rawhide", VB-DOS was "Esch" (and the Pro version was "Escher"). An effective code name has no meaning at all, has no connection to what's going on, etc.

Ideally, they'd have given this mission a name like "Operation Pinecone" or "Operation Shingle". It would ID the task to those involved in the planning and delivery, but tell the enemy absolutely nothing.

Of course, we're in an age that's much more PR-driven than we were 60 years ago, oh well.

[Abn1508]

You've obviously never heard of "Operation Olympus."

[Great Wombat]

Quite a good thought, but to be honest, OVERLORD and TORCH (two WWII invasions, both called D-Day today) to me sound non-meaningless. Operation Overlord is an excellent name, I do not know why we switched to two name Op codes. We will name the war later ("Remember the time the US killed everyone in Iraq's army and sold the rest of the population into bondage, sowed the land with salt and paved over Baghdad? That was a hoot.") But for now, let us be content to have a little laugh.

--Wombat