Hobby programmers reject LLMs because the struggle is the point

The Born Against essay frames something I have noticed in Discord servers for months. Hobby programming communities ban LLM usage. Professional teams mandate it. Same tool, opposite reaction. The difference is what you optimise for. At work, code is a means to an endpoint. Ship the feature, close the ticket, deploy on Friday. The faster you write working SQL, the better. Copilot writes boring CRUD so you can focus on the parts that actually matter. In a learning community, code is the endpoint. The person asking how to parse JSON in Python does not need JSON parsed. They need to understand how libraries work, how errors surface, how to read documentation. An LLM short-circuits that. You get the answer without building the mental model. This is why Advent of Code bans LLM solutions. The puzzle is not the algorithm. The puzzle is figuring out the algorithm. Pasting the problem into ChatGPT and submitting the output defeats the purpose the same way looking up crossword answers defeats the crossword. The essay argues this creates a cultural split. Professional developers see resistors as Luddites who romanticise difficulty. Hobbyists see LLM users as people who want credit for work they did not do. Both are half right. I use Copilot at work because my manager measures delivery, not education. I turn it off when learning a new framework because the autocomplete prevents me from reading the actual documentation. The tool is neutral. The context decides whether it helps or harms. What surprises me is how few people admit this trade-off exists. We pretend LLMs either ruin everything or fix everything, when the actual answer is boring. They are good for some goals and bad for others. Hobby communities ban them because learning is the goal, not the side effect.

---

Source: Born Against, or why hobby programming communities are against LLM usage