The birth of Automatically Programmed Tools
Today in the history of programming
In the popular history of programming, the story usually jumps from early business languages to operating systems and then straight to the web. February 25, 1959 is a reminder that one of the most important programming revolutions happened somewhere else: on the factory floor. On this day, MIT demonstrated APT, Automatically Programmed Tools, an English like programming language designed to generate instructions for numerically controlled machine tools.
That sounds niche until you notice what it really represents. APT turned geometry into code and code into motion. It was a language whose output was not a printed report or a number in memory, but a cutting path through metal. The famous anecdote from the time is almost too perfect: the Computer History Museum notes that a New Yorker article described the Air Force announcing a machine that could receive instructions in English, figure out how to make what was wanted, teach other machines how to make it, and that day it made an ashtray.
APT mattered because it created a new pattern that is now everywhere: a domain specific language that compiles high level intent into low level control. Today we take this pattern for granted in compilers, shader languages, SQL, and modern ML graph compilers. In 1959, APT was doing it with parts, tools, and tolerances. It also helped cement the idea that programming is not only about computing results, it is also about controlling physical processes.
You can draw a straight line from APT to modern CAD CAM workflows. The human specifies geometry and constraints, the system computes a toolpath, and a postprocessor emits machine specific commands. That layering is basically a compiler toolchain, except the target is a machine controller and the bugs can snap tools, scrap parts, or worse. This is one reason manufacturing software has always been a high stakes branch of programming: the runtime is reality.
If you want a clean lesson for today, it is that some of the most consequential programming history is not about screens, apps, or networks. It is about translation. APT was an early proof that code could be a bridge between human intent and the physical world, and that bridge would go on to shape automation, robotics, aerospace manufacturing, and the entire idea of software defined production.
https://www.computerhistory.org/tdih/february/25/
https://www.acm.org/education/otd-in-computing-history