Where the source code Analogy Breaks

Calling dna a source code 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.

A software architect can use the code metaphor to notice persistence, copying, interfaces and interpretation. The stronger model, however, is a running stateful system in which the genome is one durable information layer and the machinery that reads it is itself produced and maintained by the system.

What the metaphor gets right

A software architect can use the code metaphor to notice persistence, copying, interfaces and interpretation. The stronger model, however, is a running stateful system in which the genome is one durable information layer and the machinery that reads it is itself produced and maintained by the system.

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

The analogy fails if it suggests a clean software/hardware split, a single compiler, or a complete standalone specification of an organism. A DNA molecule outside a living cellular context does not boot life.

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

DNA is a chemically stable information-bearing polymer, but sequence becomes biologically consequential only inside a cell that can copy, transcribe, regulate and interpret it. Protein-coding regions are only part of the genome; regulatory sequences, chromosome organization, molecular machinery, cellular state and environment all affect what happens next.

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

Molecular biology made information language enormously productive, but gene regulation, developmental biology and cell biology showed why sequence alone cannot explain phenotype.

DNA turns the philosophical question of information into a physical one: when does a persistent pattern become meaningful to a system?

If information requires an interpreter, where does biological information end and the interpreter begin?

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

• Aeon — The cell is not a factory
• Aeon — We are not machines
• NHGRI — Gene Regulation

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