The Hardware Is the Software
Step back from these comparisons and a broad pattern appears. In outline, a brain does what a computer does. It takes in information, stores some of it, retrieves it later, and uses it to produce an output: a decision, a movement, a memory brought to mind. Described that way, the comparison holds up well.
But in one place it breaks down completely, and that place is close to the whole architecture. Every ordinary computer ever built, from the first room-sized machines to the phone in your pocket, keeps two things physically apart: a memory, where data and instructions sit, and a processor, where the computing happens. Every operation means shuttling information between the two: fetch something from memory, hand it to the processor, send the result back, fetch the next thing. Computer scientists call this the von Neumann bottleneck, and it's a real cost; much of a computer's time and energy goes into moving data around rather than computing with it.
The brain isn't organized that way, and the difference runs deeper than where things sit. In a computer, hardware and software are separate. The chip stays the same; the program can be swapped out for a completely different one without changing a single transistor. A brain has no such separation. As neuroscientists like to put it, in the brain the hardware is the software. What a brain "runs" isn't a file of instructions sitting on top of unchanging tissue. It's a particular pattern of physical connections, and changing what the brain does means physically changing the brain: growing a connection, strengthening one, weakening or pruning another. Learning isn't installing a program. It's remodeling the machine.
That fusion goes all the way down. A synapse, the physical junction between two neurons, does both jobs in the same place at the same time. Its strength stores what has been learned, and that same strength sets how much one neuron's signal affects the next, which is the computation itself. The brain has no bottleneck to pay for, because it never split the two jobs between two places.
Which brings us back to instinct. If the brain doesn't run on separate software, then an instinct can't be written into it the way a line of code is written into a program. There's no text file in the skull waiting to be read. For an instinct to exist, something has to be physically built: cells of particular kinds, in particular places, connected to particular other cells. Coding an instinct isn't writing. It's construction.
Last revised 2026-11-18