Developers are split over LLM coding tools, with some mourning the loss of hands-on coding as a craft. Les Orchard, who learned BASIC at seven, sees these tools as another rung on his lifelong ladder, while Nolan Lawson laments the fading tactile relationship with code. Their divide reflects deeper philosophical rifts: Orchard values output efficiency, Lawson grieves the disappearance of the creative process itself. Both agree the tools have merely exposed an existing schism in how developers define their work.

The tension mirrors Karl Marx's concept of alienated labor, where workers lose connection to their craft. For Lawson, LLMs strip away the satisfaction of wrestling with code, reducing programming to mechanical output. Orchard, however, remains detached from this anguish, having never tied his identity to the act of coding. This asymmetry highlights how individuals internalize technology differently based on personal history and professional priorities.

Structural forces amplify these divides. The article notes developers using LLMs often do so out of market pressure, not choice. Productivity metrics favoring speed over craftsmanship push even reluctant users toward assistance tools. Yet the author, sustained by grants rather than corporate demands, maintains a hybrid approach: using LLMs for repetitive tasks while preserving creative coding for meaningful work. This model suggests technology's impact depends heavily on workplace context.

The debate ultimately questions whether grief over lost craftsmanship should target the tools themselves or the systems compelling their use. While capitalism accelerates this shift by prioritizing output velocity, the core issue lies in how work is measured. As the author writes, "The sun rises, the sun sets," implying resignation isn't inevitable. The real challenge: redefining value beyond speed in an era where code generation tools rewrite the rules of creation.