The Abstraction Sequence

In the AI Story

The structural consistency of the sequence deserves recognition as a law of professional evolution in computing: every increase in abstraction triggers the gatekeeping argument from the previous level, and the argument fails whenever the new level produces output adequate for the organizations that consume it. Assembly programmers argued that high-level language users wrote bloated code. They were right; it was irrelevant. High-level language programmers argued that framework users assembled black boxes. They were right; it was irrelevant. At each level, the organizations arbitrating the dispute defined adequacy in terms of their own needs, not the profession's internal standards.

Each transition also produced cultural losses alongside economic shifts. Communities of practice formed around each level developed their own aesthetic standards, their own criteria for excellent work, their own communal identities. Assembly programmers valued elegance measured in instruction counts. High-level programmers valued clarity of algorithmic expression. When a new level rendered those values less relevant to organizational demand, the cultural loss was experienced as intensely as the economic one. Practitioners were not just losing market position; they were losing ways of being in the world that had given their work meaning.

AI's radicalism lies in abstracting the translation process itself. Previous abstractions still required learning a specific technical language—a programming language, a framework API, a deployment syntax. AI removes even this requirement. The practitioner describes what they want in the medium of human thought—natural language—and the tool handles every technical translation the implementation requires. The potential jurisdiction this creates is not defined by technical knowledge of any kind. It is defined by intent specification, outcome evaluation, and judgment about what deserves to be built. This is the ascent Abbott's framework describes: the movement up the professional hierarchy toward work that is more judgment-intensive and more dependent on the distinctly human capacities no level of abstraction can replicate.

The pattern extends beyond computing. In medicine, each diagnostic abstraction—physical examination, laboratory testing, imaging, genomic analysis—expanded scope while reducing the depth of hands-on examination each diagnosis required. In law, each research abstraction—library review, computer-assisted search, AI-augmented analysis—expanded the scope of precedent the lawyer could survey while reducing engagement with individual cases. The abstraction sequence is not unique to technical professions; it is a universal feature of professional evolution whose jurisdictional implications are consistent across every domain.

Origin

Abbott's framework for understanding abstraction as a jurisdictional phenomenon was developed in The System of Professions and elaborated in subsequent work on the sociology of knowledge. The application to computing's abstraction hierarchy draws on the same analytical principles Abbott applied to nineteenth-century medical and legal transitions.

Key Ideas

Structural law. Every increase in abstraction triggers gatekeeping arguments that fail whenever output meets organizational adequacy standards.

Cultural loss. Each transition dissolves the aesthetic values and communal identities of the displaced community of practice.

Ascent, not descent. Higher levels of abstraction produce practitioners with broader scope and greater judgment responsibilities, not shallower ones.

Universal pattern. The sequence operates across every profession, not only computing.