Huzzah: keep the plan
beside the program.
You return to a small app weeks later and wonder why it behaves that way. Daniel Vaughn’s experimental editor, Huzzah, keeps a human-written description alongside generated source code. That source is the program text a computer runs. The description records what the person wanted it to do. [21] [22]
Write the behavior in your own shorthand
Huzzah uses pseudocode: readable steps that describe behavior rather than the exact syntax of a programming language. Vaughn’s August account describes saving changes to that description as the next instruction to the model. The description is meant to remain available after a chat has moved on. [21]
An example to imagine
For a pocket sky viewer, write “click a star to save a note.” Revise it to “click a star to compare it with the previous selection.” That purpose now calls for remembering two selections and displaying a comparison. You can inspect whether the changed program matches the changed intention. This is our example, rather than a Huzzah test.