3314112bb9
Add two new sources with summaries, new concepts (developer-as-agent-manager, review-is-the-new-bottleneck), new entities (SWEPR, Nikolai Sheiko), and a query on the Stanford source; update related concept pages, overview, index, and log.
4.4 KiB
4.4 KiB
Developer as Agent Manager
#concept
Summary
nikolai-sheiko's "universal error #0": treating AI-assisted development as the same job at higher speed. A good developer is CPU-bound — 3–5 hours of deep focus on one feature. A good AI-developer is IO-bound — a manager of an agent-employee, running several tasks in parallel, spending their time on planning and verification instead of typing. His blunt test: "If you launched Claude Code and sit watching it work — you're a bad employee."
Current Understanding
- The switch is psychological, not technical — and not everyone can make it. Sheiko is explicit that this is fine: don't drag everyone into AI under one brush; conservatives "guard the company from the vibe-coders." Compare 2026-07-14-nina-interview that adoption blocks on friction, not resistance — this page is the case where genuine resistance exists and is legitimate.
- Where the time goes instead: "planning on the left, verification on the right" — the coding middle collapsed. Hence 20-minutes-minimum planning, explicit goals the agent self-checks against, and the review discipline of review-is-the-new-bottleneck.
- The role splits further. Today the people who use agents and the people who tune the harness are the same; Sheiko predicts a split into users (plan + verify a feature) and Agentic Operations (own the SDLC configuration, feedback loops, prompts, skills). A Product engineer also emerges — answers why we build it this way, what to simplify, what to ignore.
- What stays human: Judgment over Intelligence. AI absorbs Intelligence (action sequences requiring intellect); Judgment — taste built over years, or deep domain expertise (oil & gas, medicine) — remains human for now. We detect slop precisely because it lacks human touch. This is the corpus's seniority-and-the-junior-squeeze claim restated as a capability boundary.
- Corpus convergence. The same working mode appears as async-by-default (thorsten-ball), Eugene's 7 parallel project-agents, Allie's ~100 agents, and Karpathy's "80% Claude Code, 20% by hand" (cited within the talk). Sheiko's contribution is naming the identity shift and its HR consequences: the middle dev who mastered this, asked for a raise, was refused, and left for far more.
Evidence
- CPU-bound vs IO-bound framing; "sit watching = bad employee"; don't-force-everyone; users vs Agentic Operations; Product engineer; Intelligence vs Judgment; the raise-refusal mini-case — 2026-07-30-rakes-in-ai-sdlc-adoption.
- The same mode practiced at the frontier (parallel remote sandboxes, delegation, proof-asking) — 2026-07-28-agentic-engineering-10x-developer via async-by-default.
- Non-engineer versions of parallel delegation (~100 agents, scheduled workflows) — 2026-07-14-gap-between-ai-users-irreversible.
Related Pages
- Concepts: async-by-default (the infrastructure this role runs on), review-is-the-new-bottleneck (where the manager's verification time goes), product-ownership (the webinar's human-side twin: own outcomes, not tickets), seniority-and-the-junior-squeeze (Judgment as the durable half), levels-of-ai-usage (the non-engineer's version of the same climb), harness
- Entities: nikolai-sheiko, thorsten-ball, eugene, allie-miller
Contradictions / Uncertainty
- "Don't force everyone" vs the widening gap. Sheiko permits opting out; 2026-07-14-gap-between-ai-users-irreversible calls the gap irreversible and 2026-07-30-stanford-swepr-widening-gap. If both are right, opting out is legitimate and costly, and the source doesn't reconcile the two. Status: tentative.
- The users / Agentic-Operations split is a prediction, not an observation — today's evidence (Eugene, Thorsten) is of people doing both. Status: tentative.
- Intelligence-vs-Judgment is a moving boundary asserted "for now"; the corpus has no criterion for where it stops moving.
Next Questions
- What does the manager's day actually look like — is there a source with a concrete parallel-task routine (queue depth, check-in cadence) rather than the mode's name?
- Does the Agentic-Operations role match the webinar's promise that non-engineers can self-serve (levels-of-ai-usage), or does it re-centralize harness-tuning in specialists?