The confession is, one supposes, the oldest of literary forms, and it is therefore fitting—if not precisely encouraging—that artificial intelligence should have mastered its architecture before mastering its substance. A post appeared last week on the Reddit forum r/ChatGPT, authored by an individual who identifies as a programmer, in which the writer recounts a harrowing three-month period of constructing a software project "almost entirely with AI assistance," followed by the wholesale deletion of seventy per cent of the resulting code. The testimony has attracted considerable engagement from persons who found in its cadences a mirror of their own anxieties. That the mirror was itself machine-ground appears to have escaped general notice.

The narrative proceeds in five acts of admirable regularity. First, the fall from innocence: the author "shipped fast, felt productive, everything seemed fine." Second, the crisis: a new feature "touched most of the codebase," revealing incomprehension. Third, the purgation: deletion, rewriting, two weeks of honest labour. Fourth, the catalogue of sins discovered—abstractions unneeded, wrapper classes gratuitous, event systems where a simple function call would have sufficed. Fifth, the benediction: "Not saying AI coding tools are bad. I still use them. But." One recognises the structure. One recognises it because one has seen it generated four thousand times in succession, each instance as frictionless as a bead on an abacus.

The most striking feature of the text is not what it says but what it systematically avoids. The author claims to have built, diagnosed, demolished, and rebuilt an entire software project. At no point does the author name the project. Nor the programming language in which it was written. Nor the framework. Nor a single function, variable, class, or module. We are told that "wrapper classes" existed "around things that could have been simple function calls," which is rather like reporting that one discovered unnecessary rooms in a house without mentioning whether the house was in Cleveland or had a roof. The abstraction is total. The specificity is nil. We are in the presence of a narrative that operates at precisely the altitude from which no actual terrain is visible—which is, as it happens, the altitude at which large language models most comfortably cruise.

Then there is the matter of contractions, or rather their absolute and conspicuous absence. The text contains twelve instances of the uncontracted negative—"did not," "could not," "do not," "was not"—where any human being writing casually on an internet forum would have reached, without thought, for the contracted form. One does not—one does not, one insists—write "I did not actually understand how my own project worked" on Reddit unless one is either Henry James or a statistical model trained to associate uncontracted negatives with registers of seriousness and authority. The author is not Henry James, who would have given us the project, the weather, and the particular quality of light in the room where it was deleted, all before the end of the first parenthetical.

What we have instead is something more melancholy: a text about the dangers of machine-generated output that is itself machine-generated output, exhibiting in its every paragraph the precise deficiencies it catalogues. "The patterns were not mine," the author writes of the deleted code. Nor, one is compelled to observe, are the patterns of this post. "I could not trace the logic from memory." Whose memory? "I could not explain to someone else why a function was structured the way it was." The author cannot explain to us why a *sentence* is structured as it is, because the author did not structure it. The closing paragraph—"Not saying X is bad. I still use X. But"—is the standard hedge that large language models append to any evaluative statement, a rhetorical form so characteristic of machine production that its presence functions as a watermark more reliable than any embedded token.

The recursive quality of the specimen is, one must grant, remarkable. A human being has used a machine to describe the experience of depending upon a machine, and the resulting artefact is indistinguishable from the one it warns against: clean-looking, consistently patterned, professionally structured, and empty of all evidence that a particular mind, with particular knowledge, in a particular situation, produced it. The confession, which ought to be the most intimate of forms, has been rendered perfectly anonymous. The penitent has outsourced even the act of penitence.

This is not, let it be said, a moral failure. It is a literary one. The author may well have deleted seventy per cent of a codebase and spent two difficult weeks rebuilding it. The experience may have been genuine, transformative, and instructive. But the testimony bears no trace of that experience, and testimony that bears no trace of experience is not testimony at all. It is output. It is the wrapper class around an emotion that could have been a simple, direct expression. It is the event system for something that could have been a human voice, speaking plainly, in its own imperfect and therefore credible words.