I'm 60 years old. Claude Code killed a passion

Hacker News Discussion ↗

Journey vs destination; identity and motivation

  • Many distinguish between enjoying coding as a journey (puzzle‑solving, craftsmanship, mastery) vs enjoying the destination (a working product).
  • Those who love the journey often feel AI removes the most satisfying part: thinking through problems, designing systems, and writing code by hand.
  • Some say what’s really shaken is identity: being “the person who can do hard things” now that tools can do much of it.
  • Others argue you can still code “artisanal” style for fun, just as people still knit, sail, or play chess despite automation and stronger machines.

AI as empowering tool

  • Many older and mid‑career developers report AI has re‑ignited their passion by:
    • Removing boilerplate and “grunt work.”
    • Enabling long‑imagined side projects with limited time.
    • Letting non‑programmers or adjacent tech people build significant systems.
  • Common pattern: humans handle requirements, architecture, and domain understanding; AI does mechanical implementation, scaffolding, and mundane debugging.

Mandates, pressure, and burnout

  • Several complain about being forced to use AI by managers chasing hype or FOMO.
  • This changes expectations: faster delivery, more microservices in less time, and performance reviews tied to AI usage.
  • For some, that shift has turned previously enjoyable work into “wrangling a lying junior dev” and increased burnout.

Code quality, architecture, and security

  • Skeptics highlight:
    • LLMs’ tendency to produce brittle, layered “slop” that’s hard to maintain.
    • Risk of shallow understanding, unknown‑unknowns in architecture, and poor security when speed is prioritized.
  • Supporters counter that human‑written code is often bad too, and disciplined workflows (tests, reviews, small iterations) can keep quality acceptable.

Learning, mastery, and juniors

  • Concern: if AI handles all small, self‑contained tasks, newcomers may not develop deep skills needed to maintain complex systems.
  • Others think the “mastery target” simply shifts: from low‑level coding to problem definition, system design, and “agentic” workflows.

Analogies and broader reflections

  • Frequent analogies: motorboats vs rowing, diesel vs sailing, calculators vs slide rules, IKEA furniture, helicopters on mountain peaks.
  • Some see AI as ruining a shared ecosystem and craft culture; others see it as just another step up the abstraction ladder.