Why are executives enamored with AI, but ICs aren't?

Original Article ↗ Hacker News Discussion ↗

Premise: Are ICs less enamored than executives?

  • Many commenters dispute the premise: lots of ICs are excited about AI; lots of executives are skeptical or just following hype.
  • Surveys and anecdotes cited in the thread suggest high AI adoption among developers, though not universal.
  • Others say enthusiasm is heavily role‑, domain‑, and skill‑dependent (e.g., web vs. systems, data vs. embedded).

Executives’ motivations and perceptions

  • Execs are seen as viewing AI as a way to:
    • Reduce headcount and labor costs.
    • Turn “expensive engineering work” into cheaper, more interchangeable output.
    • Confirm an existing worldview that work is a commodity and value lies in orchestration/strategy.
  • Strong FOMO: betting on AI is career‑safe; ignoring it and losing to competitors is not.
  • AI demos and simple side projects lead some leaders to wildly overestimate capabilities (“vibe coding” → assume anything is easy).
  • Some execs apply AI to their own tasks (communication, reports, slideware) and infer it can replace all knowledge work.

IC experiences and attitudes

  • Many ICs use AI daily for: boilerplate, debugging, exploring unfamiliar stacks, quick prototypes, semantic search, and tests.
  • Others avoid it, especially in low‑level/systems work, citing hallucinations and domain‑specific issues.
  • Some enjoy coding and don’t want to outsource the “fun” parts; others revel in speedups that remove drudgery.

Code quality, limitations, and failure modes

  • Repeated reports of “slop”: plausible but brittle code, hallucinated APIs, shallow tests, defensive over‑engineering, and poor long‑term evolvability.
  • Strong consensus that unsupervised AI code/agents don’t converge on robust architectures for larger projects.
  • Some claim they barely read AI‑generated code; others warn this is reckless and leads to unmaintainable systems.

Impact on work, jobs, and power dynamics

  • IC concerns: higher expectations without more pay, loss of bargaining power, and explicit plans to cut staff.
  • Executives/owners expected to capture most productivity gains; historical productivity–wage decoupling is invoked.
  • Some frame this as classic capital vs. labor / “means of production” conflict; others push back on simplistic Marxian readings.

Broader themes and uncertainties

  • AI tools both commoditize routine coding and increase leverage for strong engineers.
  • Long‑term effects on roles, pay, and required skills (specification, critical thinking, validation) remain unclear.