Google Stitch dropped Figma's stock 12% in two days. The market read that as proof that meaningful design work is being automated. It is not. What Stitch and every comparable tool produces is executable prototypes, not production code. A VeraCode study from October 2025 confirmed that LLM-generated code has not improved in security at the same rate it has improved in functional output. Senior engineers are already reporting what Fast Company called a 'vibe coding hangover' when inheriting AI-generated codebases. The term 'vibe coding,' coined by Andrej Karpathy in February 2025 for throwaway weekend projects, has been promoted by Collins Dictionary to Word of the Year. The word traveled faster than its meaning.
The author's core argument is structural, not semantic. Renaming the activity 'vibe prototyping' is more honest, but it does not fix what is actually broken. What broke is the chain of authority between reasoning and trust. Teams now require something interactive before they believe progress is happening. Visible behavior has replaced invisible structure as evidence of work. Designers in Figma rehearsed this misunderstanding for years, producing prototypes that look complete because they move convincingly, while every element still had to be rebuilt in production. Vibe coding is that same logic scaled up, with the added danger that the output sounds like infrastructure because the word 'coding' is in the name.
The piece is worth reading in full because it does not stop at the terminology critique. It identifies an authority problem that better tools will not solve. The argument traces how the industry has always renamed activities upward, from templates to frameworks, from wireframes to experience architecture, and explains why 'vibe coding' fits that tradition precisely. The closing section proposes a deliberate separation between the prototype and the decision, which is where the practical argument begins. That is the part most editors and leads will need.
[READ ORIGINAL →]