Lore

Vibe Coding

A "shoot and forget," one-shot prompting mentality where an AI coding agent's output is accepted as-is, with no repeatable review or scoping process. Also called "VIP coding" in this source. Framed as the anti-pattern that AI-Native Developer Workflow and its layers (Specification-Driven Development, Context Engineering, Loop Engineering, Graph Engineering) are designed to replace.

Failure mode

A vague, unsupervised prompt forces the agent to silently fill in unstated assumptions about scope and stack. Demonstrated live: an unsupervised agent given a vague prompt built an entirely different, unrelated tool than intended.

One-Shot Prompting as Diagnostic

One-shot prompting — submitting a single vague instruction to a coding agent with no further guidance — is vibe coding in its rawest form. Used deliberately, though, it becomes a diagnostic rather than a habit: run the vague prompt first, before any spec work, and watch which assumptions the agent silently fills in on its own (stack, scope, data model, edge cases). "It cannot read my mind, right?" — the gap between what it assumed and what was actually wanted is exactly what Specification-Driven Development and Context Engineering exist to close, so one-shotting first makes the cost of skipping them visible before committing to a full spec pass.

Demonstrated Ambiguity Drift

Demonstrated Ambiguity Drift

A live demonstration shows an unsupervised agent given a vague request to build a feedback tool instead build a wholly unrelated "Python CLI for tracking weekly project health." This is presented as concrete, replicable evidence — not just an assertion — that vague, one-shot vibe-coding prompts let the agent's own assumptions silently steer the implementation away from what was asked, motivating the layered Specification-Driven Development / Context Engineering / Loop Engineering / Graph Engineering process instead.

Executives (and Kids) Returning to Code via AI

Facebook once required designers to pass a technical/programming interview loop, and later dropped the requirement because it made hiring too hard. Adam Mosseri — after roughly 10 years away from writing code, and by his own account never a great engineer — says AI tools have him programming again. As a personal example, he and his 10-year-old built a 19-level, 8-bit-style platformer (Super Mario–styled, with an in-game skins/weapons store) using Claude Code; an attempt six months earlier with older models 'totally didn't work.'