Where the random code change Analogy Breaks

Calling mutation a random code change is useful for about five minutes. The comparison can expose structure that ordinary language hides. The problem begins when the comparison stops behaving like a tool and starts behaving like a claim about what the thing literally is.

The code-change analogy highlights persistence, copying errors, repair and robustness. It also reminds engineers that a system's future depends partly on how variation is introduced and tolerated.

What the metaphor gets right

The code-change analogy highlights persistence, copying errors, repair and robustness. It also reminds engineers that a system's future depends partly on how variation is introduced and tolerated.

This is why engineering metaphors are so attractive. They compress a complicated relationship into something we can manipulate mentally. In the best case, the metaphor produces predictions and sharper questions.

What it smuggles in

Software bugs violate an intended specification. Evolution has no fixed specification, and mutation is not merely damage; variation is also raw material for population change.

Engineering words often carry hidden assumptions: a designer, a specification, modular ownership, explicit goals, a stable machine underneath the program. Those assumptions must be tested rather than inherited.

Return to the physical story

Mutations are changes in genetic material produced by physical and biochemical processes. They are not generated because an organism needs a particular adaptation, and their effects depend on genomic position, background and environment.

Once the mechanism is back in view, the analogy can be kept on a short leash. We can state which relation is genuinely similar and which difference would make the analogy generate a wrong prediction.

My three tests for a metaphor

1. What mechanism does this comparison help me see?
2. Which engineering assumption does the natural system not share?
3. What would I predict incorrectly if I took the comparison literally?

The third test is the most important. An analogy that cannot fail is decoration, not explanation.

Beyond the borrowed language

Mutation became central to evolutionary theory when genetics was integrated with natural selection in the modern synthesis.

Mutation makes contingency unavoidable: every lineage carries a history of events that did not have to happen exactly that way.

How much identity depends on preserving information, and how much depends on allowing it to change?

A good metaphor should eventually make itself less necessary. It gets us close enough to the real system that we can see where the scaffolding ends.

Reading trail

• Darwin Online — On the Origin of Species
• Aeon — We are not machines

These links are starting points for the scientific and historical ideas. The systems interpretation, analogies and conclusions here are my own.