I'm OK being left behind, thanks

Original Article ↗ Hacker News Discussion ↗

Early Adoption vs Waiting

  • Many agree you don’t need to be an early adopter of every trend; waiting for tools and practices to stabilize is rational.
  • Others argue that being early on some things (web, mobile, neural nets, Bitcoin, cloud) did confer big benefits, while early bets on duds (metaverse, NFTs, some JS tooling) did not.
  • Several point out that you can’t be early on everything; selectively placing a few risky bets while mostly waiting is framed as the realistic strategy.

AI Coding Tools: Productivity and Limits

  • Supporters report significant productivity gains (often 2–5x, occasionally more) in prototyping, boilerplate, debugging, and “I’ll-fix-this-someday” tasks.
  • Critics say end‑to‑end productivity hasn’t clearly improved: LLMs hallucinate, produce bloated or wrong code, and require time to explain tasks, review output, and debug.
  • There’s wide variance by domain: routine CRUD, config, and simple web apps benefit most; complex, niche, or research‑y work often doesn’t.
  • Some see AI coding as a separate skill (prompting, scaffolding, tests, agent orchestration) that is tiring and fragile; others say the basic skill is easy and “occult prompt engineering” was overhyped.

Comparison with Crypto/Bitcoin and Other Hype Cycles

  • Many compare AI FOMO rhetoric (“you’ll be left behind”) to crypto and NFTs marketing.
  • Bitcoin: some say it “won” as an asset and made early holders rich; others say it mostly powers speculation, scams, and sanctions evasion and did not become everyday money.
  • Consensus: crypto largely didn’t change normal work; AI already changes daily workflows for some, so the analogy is imperfect but the FOMO tactics feel similar.

Jobs, Skills, and “Being Left Behind”

  • Fear: AI plus layoffs and a weak market could permanently shrink software jobs, especially for juniors; some older devs feel their careers are being rug‑pulled.
  • Counterpoint: most people lose jobs for macro reasons they can’t control; chasing every fad out of fear is also unhealthy.
  • Many argue it’s not “use AI or be replaced by AI” so much as “be replaced by someone using AI,” especially where companies explicitly require it.

Management Mandates and Metrics

  • Multiple commenters report companies mandating AI tools (e.g., IDE assistants, agentic systems) and tracking usage, sometimes tying it to performance.
  • Engineers resent being forced to use a metered, non‑deterministic tool, comparing it to being ordered to use a specific editor or “ask a slot machine to code.”
  • Some managers say they only require periodic experimentation; others admit strong top‑down pressure driven by executive FOMO and investor narratives.