Vernacular Competence

In The You On AI Field Guide

The mechanism of destruction is consistent. A domain exists in vernacular form—people healing, learning, building, caring for each other. Professionals enter, bringing specialized knowledge and institutional authority. The professional knowledge is, in many cases, genuinely superior for specific applications. But professionalization does not merely supplement the vernacular. It replaces it. The professional monopoly delegitimizes the non-professional practitioner. The midwife becomes a quack. The autodidact becomes a dropout. The vernacular knowledge, no longer practiced, atrophies. The community, no longer competent, becomes dependent on the professional class.

Software development followed this trajectory with textbook precision. Before the profession existed as a category, people solved their own computational problems—bending spreadsheets into databases, copying scripts from forums, assembling workflows from duct tape. This was vernacular software development: messy, inefficient, often ugly, and convivial in Illich's sense—conducted by people for their own purposes, using tools they understood and controlled. As the discipline formalized, the vernacular practitioner was progressively delegitimized. The monopoly was enforced not primarily through law but through cultural authority: amateur code was dangerous code, untrained builders were liabilities, building software was something only professionals should do.

AI disrupts this monopoly. When a non-technical founder builds a revenue-generating application through conversation with Claude, she exercises vernacular competence the professional monopoly had foreclosed. She is not coding. She describes what she needs in her own language and receives a working artifact. The professional gatekeepers have been bypassed. This is vernacular restoration.

But Illich's framework also predicts the shadow. Within months of AI coding tools becoming available, a new professional class is forming—prompt engineers, AI literacy consultants, certification programs. The vernacular practitioner who described her problem in plain language and received a working solution is being told, already, that she is doing it wrong; that there are techniques, best practices, a right way. The professional monopoly AI dissolved is reforming around the tool that dissolved it.

Origin

Illich developed the concept most fully in Shadow Work (1981), where he distinguished vernacular activity from both professional service and waged labor. The term drew on medieval and early-modern European contrasts between lingua vulgaris and institutional Latin, extended analogically to all domains of autonomous competence.

It has been taken up by scholars of indigenous knowledge, folk medicine, informal economies, and most recently by critics of the professionalization of software and of AI, where it supplies precise vocabulary for an otherwise inarticulate sense of what is being lost.

Key Ideas

Not romantic but historical. Vernacular competence is empirically testable knowledge developed outside institutional mediation; its existence and displacement are matters of record.

Professionalization as destruction. The mechanism by which the vernacular is lost is not demonstration of inferiority but delegitimization by a professional class with institutional authority.

AI as dual pressure. AI simultaneously restores vernacular capacity (the non-coder who can now build) and threatens new professionalization (the prompt engineer as gatekeeper).

Transferred dependency. Whether AI produces autonomous builders or new dependents depends on whether the interaction teaches or merely produces.

Protection of the vernacular. Preserving vernacular competence requires active resistance to professionalization cycles, not merely access to tools.