A poem with a program inside
A self-copying program does more than print or display words: it contains instructions that make a copy of its own code and arrange for that copy to run. In the early experiment described here, a poem served as the program’s harmless, visible face. The important test was not the verse itself, but whether the code could reproduce and continue elsewhere.
Copying is only one step
For a program to spread, it needs a route to another machine and a way to start there. A copy might travel across a connected system, but it cannot act on a computer that never receives or runs it. That distinction helps explain why self-copying code is a demonstration of a capability, not proof that every such program is dangerous.
A worm is a program that spreads from one computer to another without needing to be manually copied each time. The same basic copying mechanism can be used for an experiment or for unwanted spread; what it does after arriving, and whether it has permission to run, make a crucial difference.
The lesson behind the verse
Putting the experiment inside a poem made the mechanism easier to notice without making the demonstration itself a destructive attack. It also exposed a lasting tension in computing: code can carry both a message and instructions for what to do next. The memorable twist is that the poem was not merely about copying—it was part of a program that could make copying happen.






