How to keep enjoying programming in a world of LLMs
A Haskell developer outlines a practical workflow to retain the joy and skill of programming by keeping humans in the driver seat and restricting LLMs to auxiliary tasks.
read it It provides a thoughtful perspective on developer workflows that directly addresses the rising tide of AI burnout.
summary
A Haskell developer argues that letting frontier LLMs handle all coding turns codebases into unmaintainable wastes and strips developers of their core skills. They propose a workflow where humans retain primary authorship while deploying LLMs strictly for ancillary tasks like planning, research, and minor cleanups. This approach preserves technical competence, mental health, and the intrinsic pleasure of programming. Ultimately, it frames LLMs as assistants rather than replacements to avoid alienation and burnout.
key points
- Delegating all coding to LLMs causes essential problem-solving and architectural skills to atrophy rapidly.
- The author advocates keeping humans in the coding seat while delegating planning, research, and routine cleanups to AI.
- Relying entirely on frontier models creates heavy dependence on unpredictable token availability and opaque cloud providers.
who should read it
Software engineers and developers navigating AI-driven burnout and changing workplace expectations.
discussion mixed
consensus
Commenters heavily resonate with the author anxieties about skill atrophy, loss of agency, and the frustration of reviewing low-quality AI-generated PRs from peers.
pushback
A minority view argues that programming jobs were already tedious, and LLMs successfully remove the drudgery, or that the profession is changing so drastically that maintaining manual skills is becoming obsolete.
One thing to keep in mind is that anytime you punt to the LLM (or anybody) for anything, that skill is going to atrophy.
I've seen this happen to myself where suddenly I had trouble planning out the architecture for a very small project. It should have been obvious to me, and I knew that. So it was disconcerting to not be able to suddenly have the answer appear in front of me like it normally would. I thought maybe I would go to Claude and help get some ideas.
But then I stopped myself. I knew I should be able to do this! So I got out a piece of paper and I scribbled ideas until the dam …
It provides a compelling personal anecdote about experiencing skill atrophy and realizing how delegating design work compromises core cognitive abilities.
Generated by an LLM from the article and thread. Check the sources before relying on it.