gen-z-developers.sgit.ai → The graph → Ideas → Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called

claim accepted goes to: this-edition E explorer

Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called

The entrepreneurs the book is for are developers: they code with agents. What people call vibe coding is exploration, and the word should say so; the explorer builds to find out, and what the exploration produces is the brief for the version other people rely on. A founder needs both halves: the exploring and the handover.

Decided by. Dinis, in Gen ZX Developers, adopted as the frame of rc2 (decision 015)

Where it comes from

What it answers in the 2018 book

Where it goes

Chapter Explorer coding, not vibe coding, and the handover, part The frame (drafting); topic Explorers, villagers and town planners (Wardley's frame).

Other ideas proposed for the same chapter: Explorer coding: what people call vibe coding, done as exploring, The deployment gap is a handover, and the prototype is the best brief, Design, the design canon and Christopher Alexander: the villager's and town planner's craft, A villager move: no new features while you move, or nobody can tell which change broke what, 'Nobody knows how it is built' is fixable: make the agents leave a record, a mandate, a memory and a graph, The bonus test: if nobody will put their name or their bonus on it in production, it is not ready to be in line, An explorer-coded app is a brief, not a product: not ready to be in line, and the further towards commodity the fewer agents in line, Every product needs an explorer version, with paid conversions to a villager product and a town planner one.

Node idea:explorer-coding-not-vibe-coding in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.