Agentic programming changes the phenomenological experience of coding — from craftsman to orchestrator¶
Insight: Agentic coding tools fundamentally reshape what programmers perceive as salient — shifting from code-level optimization to architectural intent and agent evaluation. Drawing on Fred Brooks's essential vs. accidental complexity distinction, LLMs excel at reducing accidental complexity (syntax, boilerplate) but cannot address essential complexity (conceptual design work). Deep thinking and systems reasoning become more critical, not less, as agents handle implementation.
Detail: Voisen (Design Engineering lead at Adobe) borrows Venkatesh Rao's "oozification" concept to describe the shift from structured, rule-heavy programming to fluid, less-constrained systems — moving from "a man-made, plantation forest" to "a swamp." The programmer's role blurs from coder into "orchestrator, delegator, babysitter, designer, reviewer." Using Jakob von Uexküll's concept of umwelt (an organism's perceptual world), he argues agentic tools fundamentally reshape what programmers perceive as salient. Paradoxically, agents can improve flow state by handling lookup tasks and boilerplate, keeping developers in high-level conceptual space. The transition is irreversible in commercial contexts.
Sources
- Sean Voisen — "Programming in the swamp" (2026-02-12)
Related: craft-matters-counterpoint-vibe-coding in design-engineering.md — CONTRASTS