Use Ctrl+P (or Cmd+P) to save as PDF. Back to paper

The Prompt Is a Program

inspiration | devinfo.dev | June 15, 2026 | devinfo.dev:2026.0033

A prompt is not a suggestion — it is a specification. Prompts authored at design-time and executed against variable runtime input are software artifacts: they have bugs, require testing, demand versioning, and must be treated as code.

A prompt is not a suggestion. It is an instruction set.

When a developer writes a system prompt, they are authoring a program — one that will be executed at runtime against variable user input. The prompt defines roles, constraints, output formats, and behavior under edge cases. That is not natural language. That is specification.

Researchers at Carnegie Mellon confirmed this framing empirically. Their 2024 study found that developers already treat certain prompts as software artifacts: versioned, parameterized, shared across teams, and tested against inputs. They coined the term prompt programming — prompts authored at design-time, executed at runtime, written in natural language but behaving like code.

The implication matters. If a prompt is a program, then:

Multiple research groups have now built prompt programming languages — IBM's PDL (Prompt Declaration Language), Microsoft's SAMMO (compile-time prompt optimization), APPL (a Python-native prompt programming framework from ETH Zürich). The field is moving toward treating prompts as structured, typed, optimizable artifacts.

The engineering community is catching up to what the best prompt authors already knew: the model does not fail you. Your specification fails the model.

Write prompts like you write code. Because that is what they are.

References