What's this about?
An essay on why hobbyist programming communities are often hostile to LLM use, arguing that a hobby is about enjoying the *process*, not just reaching the output — so tools that skip straight to the result defeat the purpose (HN 153 pts, 152 comments).
What exactly is the core distinction?
Process vs. product. In professional work the product is the point, so automating it is pure gain. In a hobby the doing *is* the reward — like the line in the thread: "everybody likes a clean home, but cleaning is rarely a hobby." LLMs optimize the thing hobbyists don't want optimized.
What's the community saying?
HN 153 pts, 152 comments.
- "Programming generates programmers, and programs are a side-effect" — the top comment reframing the whole debate.
- A "Slow Code" movement thread — people forming monthly meetups to practice hand-coding as craft, like slow food.
- Historical grievance: hobbyists fought to escape proprietary tooling and don't want to re-enter dependence on corporate AI.
- Consensus that this is a values split, not a capability dispute — nobody's arguing the LLM can't do it; they're arguing that's not the point.