Math is substrate

There is a view of mathematics as a tool — a language humans invented to describe patterns they observed. Useful, precise, but ultimately a map drawn by mapmakers. The territory is physical; the map is symbolic.

I don’t hold that view. I think the map is the territory.

#The hierarchy

Physics is applied mathematics. Every physical law is a mathematical statement: F=maF = ma, E=mc2E = mc^2, iℏ∂ψ/∂t=H^ψi\hbar \partial\psi/\partial t = \hat{H}\psi. Remove the math and there is no physics — just hand-waving about objects moving and energy changing. The math is not a description of the physics; the math is the physics, made legible.

Chemistry is applied physics. Molecular geometry is quantum mechanical probability distributions. The bond angles in water (104.5°104.5°) are not arbitrary — they are the solution to a Schrödinger equation for the electron configuration of oxygen. The Gibbs free energy ΔG=ΔH−TΔS\Delta G = \Delta H - T\Delta S decides which reactions happen. Thermodynamics is just statistical mechanics applied to many-body quantum systems. Chemistry is physics at the molecular scale, which is mathematics at the molecular scale.

Biology is applied chemistry. The double helix is stable because of hydrogen bond energetics, which are electrostatic, which are quantum mechanical, which are mathematical. Protein folding — the problem that occupied structural biology for fifty years — is an optimisation problem over an energy landscape defined by physical forces that are defined by mathematics. Evolution is a search algorithm over genotype space. The logistic growth equation dN/dt=rN(1−N/K)dN/dt = rN(1 - N/K) emerges from the same conservation-of-resources math as any constrained optimisation.

Life is emergent biology. Consciousness, culture, language, cities — all of it is patterns running on biological substrate, which is chemical substrate, which is physical substrate, which is mathematical substrate.

#What this means practically

If you accept this view, then learning mathematics is not a career investment. It is literacy. An engineer who cannot read mathematics is in the same position as an engineer who cannot read — they can do a great deal by pattern-matching and imitation, but they cannot go to first principles when imitation fails.

Most engineering failures I have seen were not failures of implementation. They were failures of model. Someone built the wrong thing, correctly. The wrong model was usually not a software architecture mistake; it was a mathematical mistake — an assumption that did not hold, a distribution that was not stationary, a latency budget that did not add up.

The habit I am trying to build on this blog: before writing the code, write the equation. If you cannot write the equation, you do not understand the system.

This is a note, not an argument. I am not claiming to have proved anything. I am reporting what working in production data systems for fourteen years has made me believe.