Task Paralysis and AI

Original Article ↗ Hacker News Discussion ↗

AI, Task Paralysis, and Executive Function

  • Many commenters with or without ADHD say AI dramatically lowers “activation energy” for tasks: drafting tickets, boilerplate code, docs, planning, and breaking work into steps.
  • For some, “it’s cheap to write the prompt” is enough to overcome paralysis; AI replaces video games or other distractions as the go‑to activity.
  • Others report the opposite: with implementation taking minutes, they must context‑switch constantly, which is exhausting.

Dopamine, Addiction, and Gambling Analogies

  • Repeated theme: the shortened idea‑to‑result loop feels addictive, especially for people prone to chasing quick dopamine.
  • Several describe burning through paid token limits and even feeling “relief” when cut off.
  • Analogies vary: slot machines (intermittent reinforcement, random quality), gaming, social media, alcohol, smoking. Some push back, arguing it’s just a tool and “gambling” is overstated.

Impact on Joy and Identity as a Programmer

  • A substantial group feels AI erodes the intrinsic rewards of coding: exploration, hard problems, deep understanding, and the sense of “I built this.”
  • They describe becoming “managers of agents” instead of tinkerers, with work feeling hollow or like cheating.
  • Others report the opposite: AI finally lets them realize ideas despite weak syntax memory or ADHD, and feels like a superpower rather than a loss.

Career, Skills, and Long‑Term Risks

  • Some worry AI use is:
    • Good short term (productivity, meeting demands),
    • But bad long term for individual engineers (skills atrophy, shallower system understanding, less peer collaboration, easier to replace).
  • Fear that companies can eventually swap much of the team for agents, while engineers themselves are actively evangelizing the tools.

Usage Patterns, Boundaries, and Mitigations

  • Suggested patterns:
    • Use AI for boring plumbing/backend, keep “fun” or UI/architecture work manual.
    • Use it for research, design, code review, or templates rather than full implementations.
    • Limit tokens/tiers intentionally; switch to cheaper/free models for “play.”
    • Pair AI with GTD systems, pomodoro, or physical/analog activities to manage focus.
  • Skepticism about fully agentic workflows: many want tools that enhance understanding and context, not opaque code factories.