Harper Reed

tom@tomrochette.com (Tom Rochette) — Thu, 24 Sep 2026 00:00:00 +0000

Harper Reed is a Chicago technologist and entrepreneur (CTO of Obama’s 2012 campaign, former CTO of Threadless, founder of Modest, now CEO of 2389.ai) who writes about shipping software with LLMs at harper.blog. Facts below verified as of 2026-09-24.

His essay “My LLM codegen workflow atm” became the reference spec-first codegen workflow that Hacker News threads cite as best practice, and its boundary is that it is one person’s fast-aging loop, dated on purpose.

What it is
#

A personal blog running about 24 years, roughly 1444 posts at about 1.04 posts per week on average, split into long-form posts, near-daily short notes, and a Now page. The signature piece (2025-02-16) lays out a three-file greenfield workflow: brainstorm a spec with a one-question-at-a-time prompt, have a reasoning model turn spec.md into a prompt_plan.md and todo.md, then execute prompt by prompt with Claude or Aider while tests gate each step, plus a repomix-based context loop for existing codebases. The follow-ups generalize it: “An LLM Codegen Hero’s Journey” maps the nine-step adoption ladder from autocomplete to full agents, and “Basic Claude Code” ports the workflow to Claude Code with TDD as the anti-hallucination device (“The robots LOVE TDD”). Everything ships with the actual prompts inline, and posts carry his “written 98% by a human” disclosure.

Status
#

Active and still iterating in public. As of 2026-09-24 the homepage leads with “Why Don’t My Agents Break Containment?” (2026-09-22), an agent-containment experiment out of his 2389.ai research, with recent long-form posts in January, March, August, and September 2026 and near-daily notes. He is CEO of 2389.ai, where his whole team adopted the Claude Code workflow, and his history page records the arc: CTO of Obama for America from April 2011, Modest sold to PayPal in 2015, 2389 started in 2024. The workflow post’s footprint is verifiable on Hacker News: commenters in the Kiro IDE launch, the Claude 4, and the GitHub Copilot Coding Agent threads point to it as the popular workflow, one calling it “basically best practice today” (as of 2026-09-24). He also translates major posts into Japanese, Spanish, Korean, and Chinese.

Strengths
#

Concreteness: the prompts, the three files, and the exact execution loop are all in the post, and the workflow is tool-agnostic (it outlived his own Aider phase).
Practitioner credibility at scale: many shipped side products, a C interpreter built with Claude Code in about an hour, and a whole team running the process.
Calibrated humility: he dates his own advice (“this is working well NOW, it will probably not work in 2 weeks”) and updated it within weeks when Claude Code shipped.
The follow-ups cover the two gaps most workflow posts leave: how beginners climb to agentic coding, and how a team adopts it through pilots, rotation, and documentation.

Cautions
#

Shelf life is short by his own admission: the original post was Aider-centric, Claude Code landed eight days later, and his current work has moved on to agent containment experiments.
Greenfield and small-team skew: the multiplayer problem (“the bots collide, the merges are horrific”) is named, not solved.
Skeptics exist in the same threads that praise him: one engineer reports never succeeding at building a complete feature or prototype with the technique (visible in the HN results as of 2026-09-24).
The signal is buried in a personal blog: profanity, photography, and a high-volume notes stream mean RSS or targeted visits beat casual scrolling.

Compared to
#

Simon Willison: both practitioner bloggers, but Willison tracks the whole tool-and-security landscape while Reed commits to one opinionated workflow; take breadth from Willison, a starting loop from Reed.
Hamel Husain: Husain covers the evaluation side of LLM systems, Reed covers the generation loop; pair them when your question shifts from “how do I generate” to “how do I know it works”.
Chip Huyen: Huyen’s systems-level ML engineering framing versus Reed’s single-developer daily loop; Huyen for organizations, Reed for the individual.

Bottom line
#

Recommended for developers starting out with agentic codegen who need a concrete, proven workflow to run and mutate, and for leads designing a first team pilot. Not for readers wanting evaluation methodology, organization-level platform strategy, or advice stable enough to survive the next model release.

Changes
#

2026-09-24 - Created.

References
#

https://harper.blog/2025/02/16/my-llm-codegen-workflow-atm/ - the reference workflow post: spec.md, prompt_plan.md, todo.md, and both execution loops
https://harper.blog/ - the blog home: current posts (through 2026-09-22), the notes stream, RSS, and translations
https://harper.blog/about/ - the blogging record: about 24 years, about 1444 posts, about 1.04 posts per week
https://harperreed.com/ - credentials and timeline: Obama 2012 campaign CTO, Threadless, Modest to PayPal, 2389.ai
https://harper.blog/2025/04/17/an-llm-codegen-heros-journey/ - the adoption-ladder follow-up
https://harper.blog/2025/05/08/basic-claude-code/ - the Claude Code port and team adoption
https://harper.blog/2025/04/10/waterfall-in-15-minutes-or-your-money-back/ - the micro-waterfall framing and team pilot advice
https://harper.blog/2026/09/22/break-away/ - the current agent-containment work
https://hn.algolia.com/api/v1/search?query=harper%20reed%20llm%20codegen&hitsPerPage=8 - third-party HN evidence: cited as best practice across Kiro, Claude 4, and Copilot Coding Agent threads, plus one skeptic (as of 2026-09-24)

spec-first on tomrochette.com

Harper Reed

What it is
#

Status
#

Strengths
#

Cautions
#

Compared to
#

Bottom line
#

Top 5 recommended reading
#

Changes
#

See also
#

References
#

spec-first on tomrochette.com

Harper Reed

What it is #

Status #

Strengths #

Cautions #

Compared to #

Bottom line #

Top 5 recommended reading #

Changes #

See also #

References #

What it is
#

Status
#

Strengths
#

Cautions
#

Compared to
#

Bottom line
#

Top 5 recommended reading
#

Changes
#

See also
#

References
#