frame candidate goes to: this-edition V villager
The deployment gap is a handover, and the prototype is the best brief
The step from a prototype to a tool people rely on is not a place to stop but a handover from explorers to villagers and town planners; what someone built for themselves says what they want better than any document.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published the answer to HBR's deployment gap (newsroom)
- The citizen developer is good news the prototype is the best brief (newsroom)
- Go slow to go fast a worked handover with real numbers (newsroom)
What it answers in the 2018 book
- Legacy Applications answered outline, Concepts
- Refactoring answered outline, Life Patterns
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, Design, the design canon and Christopher Alexander: the villager's and town planner's craft, Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called.
Node idea:the-handover in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.