Do you want to be doing this when you're 50? (2012)

Original Article ↗ Hacker News Discussion ↗

Experiences of Programming at 50+

  • Many commenters in their late 40s–70s say they still code professionally and/or as a hobby and enjoy it, some more than ever.
  • Common pattern: they like IC roles, problem‑solving, mentoring, and “puzzle‑like” work, but strongly dislike late nights, fire drills, and pointless stress.
  • Several say they’d quit immediately if stuck in mega‑corp, heavily politicized, or non‑technical roles; others left management to return to IC work.
  • A few older devs feel burned out, physically and mentally, and want to step back to part‑time or hobbyist coding.

Environment, Agency, and “Toxicity”

  • Whether programming feels toxic or joyful is repeatedly framed as “environment-dependent”:
    • Bad: misapplied agile, endless bug chases, 2am sprints, security theater, micromanaging managers, Jira‑driven time tracking, no domain understanding.
    • Good: autonomy, remote work, small teams, direct contact with users, time to understand domains, ability to say no to unrealistic demands.
  • Several argue the real issue is lack of agency and poor communication with stakeholders, not programming itself.

Art, Constraints, and Craft vs Factory

  • One camp: constraints (time, budget, legacy code) are inherent and even generative—like in art—so complaining is a sign of weaker engineers or perfectionism.
  • Counterpoint: many constraints (ceremony, process, arbitrary deadlines) are unnecessary and stifling; once you’ve worked without them, they’re hard to accept.
  • Some emphasize personal craft and long‑term “pet” systems where they can pursue their own standard of perfection.

Corporate Processes, Agile, and “Golden Age” Nostalgia

  • Older devs recall 1990s–early‑2000s as a “hacker” era: smaller teams, more slack, less ceremony, more intrinsic motivation.
  • They see later waves of agile/scrum and management theory as attempts to turn coding into a factory line, attracting people “just for the money” and diluting hacker culture.
  • Others push back: agile was meant to reduce bureaucracy but was co‑opted; problems come from management culture, not methodology per se.

Work, Money, and Retirement Choices

  • Many 50+ devs keep working because they enjoy it, but also due to financial needs or lifestyle expectations.
  • FIRE and “one more year” dynamics appear: people trade hated but high‑paying mega‑corp roles for future independence.
  • Some urge younger devs to avoid lifestyle inflation, cultivate options (small companies, self‑employment), and separate “coding for joy” from “coding for a paycheck.”

AI and Future of the Profession

  • Several older devs are excited about AI tools removing drudgery and making mundane tasks fun again.
  • Others worry about enshittification and commoditization, but most in the thread do not believe near‑term “prompt‑engineering only” doom.