The Moral Economy of the Coder

In the AI Story

The compensation norm holds that expertise developed over years of practice should command a premium, that the premium should reflect the difficulty and scarcity of the expertise, and that the erosion of the premium through the deployment of cheaper alternatives is a violation of the implicit understanding between the profession and the market it serves. When AI tools allow unskilled or lightly skilled users to produce output that was previously the province of deeply trained professionals, the norm is violated not because the output exists—the moral economy does not claim a monopoly on production—but because the output devalues the expertise without compensating the experts whose work built the foundation on which the AI operates.

The quality norm holds that code should not merely function but should be maintainable, readable, and architecturally sound—that the pressure to ship fast should not override the obligation to ship well, and that the distinction between code that works and code that is good is a moral distinction as well as a technical one. AI-generated code frequently meets the functional standard while violating the craft standard—it works, but no human understands why it works in the specific way it does, and the architectural choices embedded in the generated code may not be the choices that a human engineer, reasoning about the system's long-term maintainability, would have made.

The attribution norm holds that the person who wrote the code should be credited, that the person who designed the architecture should be recognized, that the contribution of expertise to a collective product should be acknowledged rather than rendered invisible. The large language models that generate code were trained on the accumulated output of millions of developers. The developers are not compensated for this use of their work. The companies that deploy the trained models capture the revenue. The attribution norm is violated at every point in the chain.

The mentorship norm holds that senior engineers have an obligation to develop junior engineers—that this obligation is not merely a corporate investment in human capital but a professional duty, that the transmission of knowledge across generations is part of what it means to be a member of the profession rather than merely an employee of a company. When AI tools substitute for the human relationship through which professional knowledge is transmitted, the immediate effect is efficiency but the downstream effect is the attenuation of the transmission mechanism, and with it, the erosion of the professional norms that the mentorship was transmitting. The defenders of the moral economy are not technophobes. They are practitioners who understand, from inside the profession, that the norms being violated are the structural foundations on which professional practice is built.

Origin

The concept extends Thompson's 1971 essay "The Moral Economy of the English Crowd in the Eighteenth Century," which demonstrated that food riots were disciplined enforcement of community norms about fair prices rather than hunger-driven spasms. Thompson built explicitly on Hobsbawm's earlier work on pre-industrial labor protest. The application to contemporary knowledge work extends the framework to a new professional community facing structurally similar challenges from a new technology.

The framework has been developed in the contemporary literature on professional practices and moral deskilling, particularly by Alasdair MacIntyre and Shannon Vallor, whose analyses of internal goods and technomoral virtues align closely with the moral economy framework.

Key Ideas

Professional norms as implicit consensus. The moral economy is not written down or legally enforceable but functions through collective judgment within the community.

The four principal norms. Fair compensation for expertise, quality as craft obligation, attribution of contribution, and mentorship duty constitute the core of the coder's moral economy.

Violation as extraction. AI deployments that train on developer output without compensation, that override quality norms in pursuit of speed, and that substitute for mentorship relationships violate the moral economy at multiple points.

The analytical significance of violation. The framework explains why resistance is felt so deeply by practitioners who understand the technology—they are defending the structural foundations of their profession, not expressing irrational fear.

The enforcement problem. The moral economy is vulnerable to market disruption because its enforcement mechanisms are informal, and its defense requires institutional construction that the profession has not historically needed to undertake.

Debates & Critiques

The framework has been contested by those who argue that software engineering lacks the community density and shared tradition necessary to constitute a genuine moral economy in Thompson's sense, and by others who argue that such norms, where they exist, are preferences rather than binding obligations. The defenders of the framework—including the contemporary literature on practices and technomoral virtues—argue that the distinction between quality and merely functional work is itself a professional judgment that requires a moral vocabulary to articulate.