Watch on YouTubeSpecifications align different parts of a system toward a shared intention.
Prompts are early specifications that guide AI models toward common intentions and values.
Anyone who writes a specification, including a PM, lawmaker, engineer, or marketer, is acting as a programmer.
Sean Grove presents specifications as a common way to align people and machines. Programmers use code specifications to align silicon. Product managers use product specifications to align teams, while lawmakers use legal specifications to align humans. He places prompts in the same family, calling them a sort of protospecification that directs AI models toward shared intentions and values. Grove says specifications let teams ship faster and safer, and that everyone can contribute to them. His final point changes who counts as a programmer: the person writing the specification may be a product manager, lawmaker, engineer, or marketer. The talk gives a broad definition of programming based on expressing intent and directing a system, rather than on writing code alone.
Grove says the idea applies across technical and social systems. Programmers align silicon through code specifications. Product managers align teams through product specifications. Lawmakers align humans through legal specifications. In each case, the specification gives a group or machine a common direction. The examples move from hardware to organizations to society, showing how broadly Grove uses the term.
Grove calls a prompt a sort of "protospecification." When someone writes a prompt, they are trying to align an AI model with a shared set of intentions and values. This places ordinary interaction with an AI model inside the same general activity as programming, product planning, and lawmaking. The specification may be incomplete or early, but it still expresses what the model should work toward.
Grove says that people in the room are spec authors whether they realize it or not. The role does not belong only to engineers. Product managers, lawmakers, marketers, and other contributors can write specifications that direct systems or teams. This gives specification writing a broader meaning than a technical document produced by a software team.
Grove states that specs let people ship faster and safer. He does not explain a process or give measurements in this short talk. His claim is that a shared specification helps align the work before or during delivery, while still allowing everyone to contribute. The benefit applies to the wider group of people who write and use specs.
Grove closes by saying that whoever writes the spec is now the programmer. He names a PM, a lawmaker, an engineer, and a marketer as possible authors. His definition focuses on directing a system through stated intentions and values. Writing the instruction that aligns the system is enough to place someone in the programmer role, even when that person does not write conventional code.
"And whoever writes the spec, be it a PM, a lawmaker, an engineer, a marketer, is now the programmer."00:47