Vibe coding vs AI-assisted engineering is the critical distinction¶
Insight: Conflating vibe coding with AI-assisted engineering is dangerous — it devalues engineering discipline and gives newcomers a false picture. Vibe coding means fully giving in to creative flow, accepting AI output without deep review — ideal for prototypes and learning. AI-assisted engineering uses AI as a force multiplier within structured development (TDD, code reviews, technical design docs). The 30% speed increase in professional settings comes from augmenting a solid process, not abandoning it. Maggie Appleton (via Steve Krouse) frames it as a continuous spectrum: "vibe code = legacy code = code nobody understands."
Detail: Osmani identifies three community personas: "Vibe Coders" (embrace AI flow), "Rodeo Cowboys" (old cowboy coding rebranded), and "Prisoners" (forced to use AI by management). The consensus middle-ground is pragmatic: vibe coding is a sandbox for creativity, but scaling demands engineering. Key quote: "Use AI like a junior dev: helpful, but never unsupervised." Appleton notes that no professional developers sit at the all-vibes end of the spectrum. She personally grapples with how much understanding to hand over to Cursor or Claude Code, noting it's always easier to YOLO it — "an impulse I have to actively keep in check."
Sources
Related: existing entry "AI coding quality is a skill issue" in external/claude-code.md — COMPLEMENTS