EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2026

Huzzah bets persistent pseudocode, not chat prompts, is the right interface for AI coding

Huzzah is an experimental editor where developers edit persistent pseudocode and an AI regenerates only the code affected by each save.

Huzzah

The betThat persistent, declarative pseudocode edited by the developer, with an AI regenerating only code affected by each diff, beats long natural-language prompts.Building

What the business is

Huzzah is an open-source, experimental code editor in which the developer authors .hz pseudocode files describing the software; saving a file sends the diff to an LLM, which regenerates the affected source code while the pseudocode persists as living documentation.

How it started

Daniel Vaughn, a software engineer, worked almost exclusively with coding agents from January 2026 and by August felt utterly fatigued by writing longform English for every change. His critique: agent prompts are long-form, imperative and transient, so no reliable record of intent survives, and beyond some complexity the agents begin confusing themselves. Huzzah inverts the workflow: you write a fizz_buzz.hz pseudocode file in whatever style feels natural, save it, and the editor diffs the file and uses the change as the prompt.

What happened

On save Huzzah captures the pseudocode diff and sends it to the model so only the affected source is regenerated, not whole files; the pseudocode persists as versioned documentation and can be written language-agnostically. The prototype runs on Node.js 22.19+, uses the multi-provider Pi framework (Anthropic, OpenAI, Google, Azure, Amazon Bedrock), and includes semantic highlighting and local JavaScript execution in Web Workers. Vaughn lists caveats himself: the approach is unproven at scale and better for new codebases, cross-file dependencies are hard to express, and LSP-style features are missing.

No ending yet — it is still running.

Background

Huzzah is an experimental, open-source editor by solo developer Daniel Vaughn that proposes a different paradigm for coding with AI: instead of typing long natural-language prompts into a chat, the developer authors persistent .hz pseudocode files that describe the software, and saving a file triggers the AI to regenerate the source code affected by that change.

Vaughn arrived at the idea through fatigue. He worked almost exclusively with coding agents from January 2026, and by August he was sick of writing longform English for every change, while feeling he had lost insight and control over the code. He argues prompts are long-form, imperative and transient: there is no reliable record of human intent, instructions repeat and burn tokens, and much natural language exists for social reasons rather than information.

The workflow keeps the prompt as the artifact: writing fizz_buzz.hz as a terse pseudocode outline, saving it to generate real code, then editing the file again when the logic changes. Huzzah diffs the pseudocode and uses that diff as the prompt, so only affected source code is regenerated and the pseudocode persists as developer documentation. The prototype runs on Node.js 22.19+, supports multiple model providers through the Pi framework, and includes semantic highlighting and local JavaScript execution.

The Show HN on August 20, 2026 drew 384 points and 209 comments. Discussion mixed enthusiasm with skepticism: critics asked whether precise pseudocode recreates spec-driven development or really wants a compiler, and whether the fatigue came from long prompts or from outsourcing thinking itself. Huzzah was explicitly early-stage, with about 158 GitHub stars and 7 forks counted at launch and Vaughn asking people to try it and report back.

What has to be true

  • Coding-agent chats discard the prompt after each change, so the developer re-explains intent repeatedly and no durable record of why the code exists survives.
  • Pseudocode forces the developer to design the shape of the code and stays readable by humans, turning the instruction itself into living documentation.
  • Diffing the pseudocode file scopes the AI to the affected code instead of regenerating whole files, which cuts token waste and review burden.
  • A terse declarative format suits developers who know what they want, leaving natural language only for people lacking domain expertise.

What can be applied

When the model writes the code, the developer intent still needs a durable home: persistent pseudocode that doubles as documentation beats re-explaining everything to a chat.

Aftermath

As of September 5, 2026 Huzzah was still a building-stage experiment: source on GitHub (danielvaughn/hz), a prototype with setup instructions, and Vaughn actively soliciting feedback. The conversation it started on Hacker News continued past launch, with commenters debating whether the paradigm is a genuine new authoring model or a reinvention of spec-driven development, and Vaughn responding about the tradeoffs he already acknowledged, including scale, legacy codebases and missing LSP features.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases