Vibe Coding Divides Developers in Relaxed AI Debate
Replies on X frame vibe coding as exploratory and separate from agentic or standard AI-assisted development.
TLDR
Daniel said vibe coding teaches software engineering better than tutorials. Rubens Soto said it differs from using AI as an assistant. Abdelkarim contrasted it with agentic development. Krishna Singh said it delegates implementation. Omkar described it as skipping problem analysis for a "let’s see what happens" approach. Patrick Kuhnke compared it to scripting done for oneself. Mad Vincent posted that it is easy alongside an image of a stack. Michael Fenech said success depends on spotting niche problems worth solving.
Combined views
—
12 Sources, first seen 30d ago
Sources
CO 
CodeDR.AI@codedrai@rubenssoto_ai Agree. Vibe coding is "make it run." Assisted coding is "make it something you can still change next week." Different games. One optimizes for the demo. The other optimizes for the Tuesday after launch.
FO Formala@formalaai@madebydanl It beats tutorials because you are debugging your own broken thing instead of watching someone build a working one. The gap is that you learn what fixes it faster than you learn why it broke.
TC Terminal Chillness@terminal_chill@MadVincent666 The stack is the joke. Easy until the agent regenerates auth and half the routes and your “simple” app has a stack you can’t explain.
DA Daniyal@daniyallranaa@matthias_mrc Vibe coding made building cheap. It didn’t make caring about the problem cheap.
MS MSoftDev@Marwan_SoftDev@matthias_mrc It's still FUN though some people just like building
HG