Ask HN: Why is the HN crowd so anti-AI?

Hacker News Discussion ↗

Overall sentiment & HN dynamics

  • Many argue HN is not “anti‑AI” but divided, with loud minorities on both extremes and lots of ambivalent or mixed users in between.
  • Several note that perceptions are skewed by negativity bias and selection effects: people who dislike AI or hype post and upvote more, while people happily using it often just work.
  • Comparisons are made to the crypto boom: HN is broadly anti‑hype and anti‑grift, not uniquely anti‑AI.

AI coding: benefits and real wins

  • Many experienced developers say LLMs are “power tools” that:
    • Speed up boilerplate, tests, refactors, API-glue, and small utilities.
    • Enable solo devs and non‑experts to ship prototypes and niche tools quickly.
    • Help with debugging, reading docs, reasoning about trade‑offs, and cross‑domain synthesis (e.g., medical self‑advocacy, research, health tracking).
  • Reported productivity gains are often ~20–40%, not the marketed “10x,” and depend heavily on operator skill and problem type.

AI coding: quality, maintenance, and “slop”

  • Strong concern that AI encourages “vibe‑coding”:
    • Huge, inconsistent, duplicated, poorly designed codebases that work initially but are fragile and hard to evolve.
    • Agentic workflows that respond to problems by emitting more code, not better design.
  • Maintainability matters: code is described as a liability, not just a means to an end; elegance is tied to understanding, performance, security, and long‑term cost.
  • SREs and senior engineers report being forced to maintain AI‑generated systems that ignore conventions, lack tests, and break platform assumptions.

Labor, careers, and culture

  • Many see AI as accelerating job displacement and wage pressure, especially for average developers and junior talent; parallels drawn to weavers vs. power looms and offshoring of skilled manufacturing.
  • There is resentment that tech once “disrupted others’ jobs” but now threatens its own.
  • Some emphasize the loss of craft: coding as an enjoyable, identity‑defining activity replaced by prompt‑wrangling and reviewing slop.

Societal, ethical, and structural concerns

  • Worries extend beyond code:
    • Misinformation, deepfakes, spam, enshittified AI support and UX.
    • Data center energy/water use, centralization of power and knowledge in a few US‑based corporations.
    • Erosion of skills and “cognitive surrender” as people outsource thinking.
    • Exploitation of training data, IP, and user content without compensation.

Nuanced positions

  • Many self‑describe as “pro‑tool, anti‑hype”: AI is impressive and useful in narrow, supervised contexts, but not a replacement for human reasoning, system design, or responsibility.
  • A recurring theme: the core question is not “AI good or bad?” but “Where is it appropriate, what are its intrinsic limitations, and who bears the externalities?”