A short personal essay from an anonymous blog (strong HN reception) that splits programmers into two types: people who write code to build products and make money, and people who write code because they cannot help it. The author places himself firmly in the first camp — he prefers creating to coding and happily delegates when possible — then makes an argument about the second.
The essay’s core claim:
- For “true programmers,” the process is the point: solving, designing, debugging, understanding the whole system. Income and output are secondary.
- So the “AI will replace programmers” claim is a category error for them — even a fully autonomous AI would not remove their desire or ability to write code by hand.
- The author’s parallel is writing: he refuses AI for prose because the thinking that happens during writing is the valuable part, and AI output feels soulless. Coders who treat code as art feel the same way about code.
It is a useful counterweight to productivity-centric AI discourse — a reminder that a meaningful slice of the profession optimizes for the experience of the work itself, not just the shipped result. Whether or not you share the romanticism, the question it poses is worth sitting with: if code could be written entirely by agents, who would still choose to write it, and why?
The blog’s related posts push the same thread: programmers resist AI coding not because it underperforms, but partly because writing code is an identity, not just an output.