The computer that guided Apollo to the Moon had less memory than the notice that tells you a website uses cookies. By any modern measure it was almost nothing — a few tens of thousands of words of storage, a processor slower than a musical greeting card. And it flew human beings a quarter of a million miles to another world and back. The constraint wasn’t the obstacle. In a way, it was the point.
The Apollo Guidance Computer was built when every byte was expensive and physically heavy, so its software had to be ruthlessly small. There was no room for anything inessential. The team, led by Margaret Hamilton, couldn’t paper over a weak design with more memory or a faster chip, because there was none to be had. Everything had to be understood, justified, and made to fit.
That discipline proved its worth in the most famous minutes of the program. During the final descent of Apollo 11, the computer began flashing alarms — it was being asked to do more at once than it could handle, overloaded by data flooding in. A lesser design might have frozen, and the landing with it.
But the software had been built for exactly this. It was designed to know which of its tasks mattered most, shed the ones that didn’t, and keep the critical work running. Faced with too much to do, it dropped the inessential and held onto the landing. The astronauts continued down and touched the surface. The overload was survived not by raw power but by a design that had decided, in advance, what it could afford to lose.
It’s tempting to read this as a story about how far we’ve come — look how little they had, and look what they did with it. But the more useful reading runs the other way. They did it because they had so little. Scarcity forced a clarity that abundance rarely does: every line earned its place, the priorities were explicit, and the whole system was small enough to be fully understood by the people responsible for it.
Modern software almost never works under that pressure. Memory is vast and cheap, so bloat carries no immediate cost, and complexity piles up because nothing forces it out. The Apollo computer is a reminder that limits aren’t only something to overcome. Often they’re what make the work good.
We try to build that way on purpose — small enough to understand completely, with every part earning its place. More about how we work →