vibe
As 'vibe coding' matured, developers learned a hard lesson about which step gets skipped when people rush straight to writing code with AI.
Experienced practitioners recommend building a spec first — writing down and agreeing on exactly what should be built before generating any code with AI — because vibe coding's biggest failure mode is discovering, only after a lot of code already exists, that everyone had a different idea of what 'done' meant.
A company logo or a launch-party plan are unrelated deliverables that have nothing to do with defining software requirements; they're distractors meant to sound superficially plausible while missing the actual point about clarifying what to build.
'Spec-driven' development flips the traditional bottleneck: once AI can generate code extremely fast, the slow part of a project stops being typing and becomes deciding precisely what you want — which is really the same shift that happened whenever any tool made execution dramatically cheaper and put more weight on planning and design.
vibe
Which accelerator?What is it?Where have experienced teams shifted the weight?What's this state called, by analogy with technical debt?What does the assigned AI do?Who was it?Which one?Its name?What's the second generation called?What is it?Which of these is NOT a prompt-to-app service?What is the classic trap of vibe coding?Quration — Quration AIQ