Vibe Coding

Building software (and increasingly, whole projects) by describing intent in natural language and letting AI generate and iterate — "speaking things into existence." Mentioned in both ingested sources.

The idea

Ethan Mollick uses "vibe coding" for how AI "changes how programmers allocate time and effort," and "vibework" for the broader pattern: cross-functional teams (engineers + subject-matter + marketing experts) "independently build projects in days that would have taken months of coordination" — by speaking things into existence rather than hand-building them (Making AI Work — Leadership, Lab, and Crowd).

Dan Shipper / Every note the limits of the naive version: they "haven't ditched SaaS products in favor of vibe-coded apps" — i.e. vibe coding reallocates work but doesn't (yet) replace robust software wholesale (The AI Daily Brief — Why Agents Still Need Humans).

Connections

• Leadership, Lab, and Crowd — "vibework" in cross-functional teams is one of Mollick's "radical new approaches to work."
• The Human Sandwich — vibe coding is human-frames / AI-executes in the coding domain.
• Codex, Claude Code — the harnesses through which vibe coding actually happens.
• The Bottleneck Shift — when coding is cheap, "understanding what to build" becomes the constraint.

Sources

• Making AI Work — Leadership, Lab, and Crowd — "vibework" / "speaking things into existence."
• The AI Daily Brief — Why Agents Still Need Humans — "vibe-coded apps" (its limits).