Vibe coding lets users design and build their own software, upending the user-centred design paradigm that has held since 1947.

Added to korrents 6 Sept 2026 · How quotes work · Something wrong? Tell us

Where this collides

• In tension with

  Vibe coding is fine for short-term work but not for anything meant to last longer than a tub of yogurt; time saved is not strength gained.

  Nielsen treats vibe coding as the end of the user-centred design paradigm, because the user and the designer become the same person. Chimero says it is fine for work not meant to outlast a tub of yogurt, and that time saved is not strength gained. A paradigm shift and a disposable convenience are very different readings of the same practice.

Shared subject first, then similar wording. They may agree or disagree.

• Deciding what software should do and why is still a human job: vibe coding changes the implementation phase far more than the planning phase. JNJakob Nielsen7 Mar 2025designvibe coding
• Designers should be designing right at the boundary of the current model, hoping the next one solves it; understanding what is possible and pushing the edges even if you get stuck is probably a good place to be right now. BLBrian Lovin14 Apr 2026designvibe coding
• Making coding easy makes design more critical, not less: when anyone can produce working features, the quality of the experience is what sets products apart. JNJakob Nielsen7 Mar 2025designvibe coding
• Mockups existed because coding was hard; now designers can skip static mockups and go straight to building a UI that works. JNJakob Nielsen7 Mar 2025designvibe coding
• A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break. SYSteve Yegge11 Mar 2026vibe coding

On the map

Open the map on its own page