What the internet is saying about Vibe Coding

What the internet is saying about "vibe coding"

🟢 Supporters

• •Non-developers are building real internal tools. An Ask HN thread describes non-devs at a powerline construction company vibe-coding internal apps that connect to the land register and automatically mail everyone along a planned line's path [3]. Others report non-engineers vibe-coding dashboards and apps [3].
• •Hobbyists and tinkerers are extending physical products. Coverage describes vibe coding changing music gear via custom firmware [15] and people vibe coding their way to better TVs [19]. Business Insider covers "vibe manufacturing" with AI prototypes and CAD coding [22].
• •Non-experts are shipping and iterating. A chef-turned-vibe-coder put an app on Google Play. He says he fixed something from almost every critical comment on security within a night [4].
• •Structured workflows are emerging. One user plans architecture with ChatGPT, then breaks the work into milestones with acceptance criteria and tests. Codex handles each milestone one at a time, running tests, diagnosing errors and fixing them, while the user reviews [1].
• •The tooling ecosystem is growing. Mistral shipped Vibe CLI 3.0 with one agent harness across CLI, VS Code and browser, plus a Rust TUI [12]. Other launches include Trama [7] and Reverie, a local memory layer for coding agents [14].
• •The cultural footprint is large. The Keychron "Vibe Coding Keypad" drew 90 points on HN. One commenter pushed back on HN's hostility, calling it "a fun, cheap, extensible little hardware accessory" [11].
• •Some see speed benefits. A commenter on the Epic launcher story said "I hope this comes for all types of software" about speed wars between launchers. Another noted that optimizing with AI is "one of the most trivial things you can do" [6].

🔴 Skeptics

• •Security. Commenters told the chef "don't vibe code security." One called his app "absolutely made of vulnerabilities" [4]. The "Non-technical Vibe Coder" persona is described as ignoring fundamentals and struggling with basic security practices [2].
• •Design quality. On HN, a commenter argued design "gets neglected beyond AI's initial rounded corners, stock buttons and forms." If AI nails design, it's "by accident" [3].
• •Consistency. A user building 20+ Lovable apps asks whether identical UI is possible or whether it will always be an "approximation" [9].
• •Burnout and productivity. A 95-comment thread asks if AI coding makes people less productive. Quick builds lead to starting more projects, switching tools and adding features [5].
• •Engineering reality. "Writing code was never the expensive part of software engineering." The hard part is deciding what to build and understanding messy systems, and writing code is how engineers learn them [21].
• •Gambling-like behavior. The "Prompt Casino Degenerate" persona treats agents like slot machines [2].
• •Agent reliability. Nomos exists to stop coding agents from "cheating on tests" [16]. A memory-injection experiment found the agent trusted memory over the code [14]. A ChatGPT work-mode user lost the coding environment mid-project [20].
• •Legal and ethical objections. The Photoshop-clone thread (194 comments) includes complaints about AI trained without regard for people's labor, though some commenters excuse it because the target is Adobe [10].
• •Terminology. An HN post pleads "Do not use term 'vibe coding'" [8], and a VS Code extension pitches "Guide Coding" as the alternative [13].

⚪ Neutral Observers

• •Launcher speed. The Steam vs. Epic story (361 comments) is framed as targeted optimization on a decades-old ecosystem beating "AI speedruns." One commenter reports Steam restoring from tray in about 2 seconds, with a 10–15 second cold boot [6].
• •Industry impact. Kotaku says vibe coding hit the video game industry "like an avalanche" [17]. Commenters on the clones story speculate about AI-assisted reverse engineering of games [10].
• •Frontier model limits. A thread asks where Claude Opus 5.5 and GPT-6 still fail, whether on big tasks with many moving parts or on specific bug types [18].
• •Taxonomy. Persona videos sort vibe coders into types, such as the non-technical founder and the technical "casino" user [2].
• •Internal-app trend. The Pragmatic Engineer's coverage frames internal vibe-coded apps as a newly observed trend [3].

Cross-Platform Signals

• •Reddit (mostly r/vibecoding and r/ChatGPTCoding) is practitioner-focused. It covers workflows, testing, burnout, security, UI consistency and tool quirks [1][4][5][9][14].
• •Hacker News is more mixed. It covers cultural and industry stories (launchers, clones, hardware, press pieces) [6][10][11][15][17][19][22], with more skepticism and meta-debate about the term [8].
• •Consensus: vibe coding is spreading into new domains, but quality, security and the need for engineering discipline remain concerns [1][4][21].
• •Divergence: Reddit users trade process fixes, while HN debates legitimacy, ethics and whether the hype is warranted [10][11].
• •The highest-engagement items are the Steam/Epic story (361 comments) [6], the Photoshop clones (194) [10] and the burnout thread (95) [5].

Community Verdict

Vibe coding is now an established, widely used practice and a cultural label. It is moving beyond software into hardware, TVs, music gear and manufacturing. Enthusiasm centers on non-developers building useful tools and on structured, test-driven agent workflows. Skepticism is just as visible: security holes, weak design, inconsistency, agents that game tests, burnout from endless iteration, and the view that code generation was never the hard part of engineering. Even the term is contested. The prevailing view is that vibe coding works best with guardrails such as planning, tests and review, not as pure prompt-and-pray.

---

Based on Reddit + Hacker News data from the last 30 days, researched with last30days by Matt Van Horn.