Will vibe coding end like the maker movement?

Original Article ↗ Hacker News Discussion ↗

What vibe coding is “for” (novelty, sharing, status)

  • Many see publicized vibe-coded projects as shallow “virtue signaling” or attention-seeking: low effort, high bragging.
  • Others argue it’s mostly genuine excitement and the shock of “I can make this in a weekend now,” analogous to early photography or film, when people shared mundane content because the medium itself was new.
  • There’s tension between people who value effort (“marathon vs 100m jog”) and those who care only about usefulness of the result, regardless of how hard it was to build.
  • Some note hiring incentives (“do you have a GitHub?”) push people to publish anything that looks impressive on a CV.

Comparison to the Maker Movement and 3D printing

  • Strong disagreement on the premise that the maker movement “ended”: many describe thriving communities, better tools (Bambu, cheap CNCs/lasers), and lots of real-world projects; what died was the media hype and some corporate efforts (e.g. Maker Faire, MakerBot).
  • Several recall early 2010s hype that 3D printing would reshape manufacturing, create micro-factories in every city, and “bring manufacturing back”; that never materialized at scale, but it did massively democratize prototyping and certain niches.
  • One framing: cheap tools commoditized prototyping and made the underlying industrial base (e.g. Shenzhen) more valuable. Analogously, AI may commoditize app prototypes while value accrues to model owners and infra providers, not vibe coders.

Capabilities, quality, and maintenance

  • Enthusiasts claim current LLMs already let them:
    • Rapidly build embedded projects (ESP32, RP2040, PIO/RMT), web and mobile apps, mods, and internal tools.
    • Fix real bugs in large codebases and contribute upstream.
    • Clear long-standing “back burner” tasks and explore more ambitious ideas.
  • Skeptics counter that:
    • Most vibe-coded code is unmaintainable “slop” that quickly becomes a liability; serious teams often rewrite AI PoCs for production.
    • Agents get “easy” things (regex, boilerplate) ~95% right, but the remaining 5% in auth, state, or concurrency can mean silent data corruption and security holes.
    • Without tests and human judgment, LLM-driven changes are unstable; agents currently require stricter guardrails than humans to avoid chaos.
  • There’s concern that skipping the “two years of useless Arduino projects” phase erodes deep judgment; others respond that LLMs can increase hands‑on learning if used interactively, not as a black box.

Democratization vs expertise

  • Many see vibe coding as empowering domain experts and hobbyists who previously couldn’t ship software, similar to Micropython/ESPHome lowering barriers in hardware.
  • Counterpoint: non‑engineers shipping code they don’t understand (or using LLMs for electronics, chemistry, DIY) can be dangerous; hallucinated advice in physical domains might start fires or cause injuries.
  • Some predict domain experts will launch successful apps then hit a wall when maintenance and scaling demand real engineering; “talent debt” shows up later.

Economic and cultural implications

  • Debate over impact on jobs: from “30% productivity gain → big layoffs” to “we’ve had many such gains before; demand and scope will just expand.”
  • Many agree software and coding themselves are weaker moats than assumed; most businesses care about meeting needs, not beautiful code.
  • Vibe coding is framed as part of a larger commoditization: more people can implement, so the bottleneck shifts to domain understanding, system design, and long‑term reliability.
  • Some emphasize that, like maker culture, the healthiest use of these tools is as a playground: permission to “fuck around,” not just a pressure to monetize every project.