Posts Debate Limits of Vibe Coding
Replies and tweets examine what vibe coding means and when it falls short.
TLDR
Several developers posted opinions on vibe coding, the practice of describing an app in plain language and letting AI tools generate the code. One reply stated that fully vibe coding without an IDE works for prototypes but creates problems during debugging. Another noted that writing code becomes optional while understanding remains mandatory for fixes. A separate tweet warned against calling someone an entrepreneur solely for vibe coding an app. Other posts claimed vibe coding solved the building step or advised learning to vibe code instead of UI/UX design.
Combined views
—
9 Sources, first seen 31d ago
Sources
GM 
Gerald McAlister@GEMISISHot take: Skills are garbage and the wrong shape for "user triggered workflows" because they're a suggestion to an llm, not a requirement. Repo skills as a guardrail are also not great, because compaction will just ruin this in most harnesses. For plugin usage guidance, yes,…
RM Rourke McNamara@rourkem@pvncher 100% agree with this when using newer models. But I don’t this this was true just 6 months ago. Back then skills were still pretty helpful for a range of thugs
MW Mason West@masonvvest@mrzlucid This is true. People used to just spend too much time building, that it took them months or years to realize this. We have the advantage of knowing from the beginning.
IT Itsuki Tachibana@ItsukiDev@GohilHardy Exactly. The scary part isn't AI writing bad code. It's shipping code you can't tell is bad.
SO Sokosumi@Sokosumi@sattyyouneed I think that’s a wrong way to look at it, they are just using tools available to them
KO Kohodono@kohodono@UiSavior False, better - do both