Fetching from the wire…
Top 5 · 2026-05-06 · source-backed
ProgramBench dropped a benchmark that should make every "AI will replace developers" hot take age badly. The setup: give an agent a compiled executable and documentation, then ask it to architect and implement a complete codebase that reproduces the original program's behavior. No existing code to edit. No repo to patch. Just specs and a blank canvas.
Every model scored 0% fully resolved across 200 tasks spanning jq, ripgrep, FFmpeg, and SQLite, verified against 248,000+ behavioral tests. Claude Opus 4.7 led with 3.0% "almost resolved." That's the best any model could do. Source: arXiv
This matters because it's the inverse of SWE-bench. SWE-bench asks agents to patch existing code, which is incremental work within an established architecture. ProgramBench asks agents to make the hard decisions: choose a language, design the module structure, define the interfaces, handle edge cases the documentation doesn't mention. The stuff that makes software engineering hard.
I've felt this gap in my own work with Claude Code in my personal projects. It's excellent at implementing features within a codebase I've already architected. Hand it a spec and a file structure and it'll write solid code all day. But ask it to start from nothing? To decide whether this should be a monolith or microservice, whether to use an event bus or direct calls, whether the data model should be normalized or denormalized? It struggles. The decisions compound and the agent has no framework for evaluating tradeoffs at that level.
The practical takeaway is simple: spec-driven development isn't optional. If you're using AI coding tools (and you should be), your job has shifted from writing code to making architectural decisions and writing clear specifications. The agent handles implementation. You handle the "why" and the "how it fits together."
This connects directly to the Willison story below. The productivity gains are real, but only if you're doing the architectural thinking the agent can't do for you.
Each link below shares sources, entities, or timing with this story.
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, Claude Opus, SWE; reported by the same outlet (arxiv.org).
Claude Code uses Opus / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, Claude Opus, SWE; overlapping topics (already, claude, code, model).
OpenClaw uses SQLite / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (OpenClaw uses SQLite); both cover Claude Code, SQLite; reported by the same outlet (arxiv.org).
Claude Code uses Hugging Face / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code uses Hugging Face); both cover Claude Code, Claude Opus; reported by the same outlet (arxiv.org).
Codex competes with Claude Code / Shared entities / Same source domain / What happened next / Tension
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Claude Opus, SWE; reported by the same outlet (arxiv.org).
Anthropic released Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Claude Code); both cover Claude Code, SWE; reported by the same outlet (arxiv.org).
Claude Code uses Opus / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Claude Code uses Opus); both cover Claude Code, SWE; reported by the same outlet (arxiv.org).
OpenClaw uses SQLite / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (OpenClaw uses SQLite); both cover Claude Code, SWE; reported by the same outlet (arxiv.org).