Alan Sondheim matters to contemporary poetry because he refuses to treat the network as a neutral delivery system. In much digital writing, the computer is a convenient tool: a place to type, revise, store, and distribute finished language. In Sondheim’s Internet Text, the machine is not backstage. It enters the sentence. It changes the name of the speaker. It makes a failed command sound like grief, a corrupted address sound like desire, and a bounced message sound like a theological condition. His work asks a question that remains useful for poets now: what happens when the medium that carries language becomes one of language’s speakers?
The answer is not simply that poetry can include code. Sondheim’s achievement is more radical and more intimate. He makes code, system messages, usernames, protocols, errors, and online performances behave as lyric pressure. Technical forms do not decorate feeling; they expose it. A command such as deletion can become self-erasure. A null device can become a private theology of disappearance. A subject line can become a title because, in an email-list poem, the system’s own architecture has already touched the poem before the reader begins.
This is the central lesson for a poet working after Sondheim: the digital element must perform meaning. It is not enough to place “error,” “file,” “password,” or “program” into a poem as fashionable scenery. The poem should behave as though it has been run through a system that can misunderstand it, reject it, multiply it, archive it, or return it altered. The form should know what the theme is doing. A poem about abandonment might not merely mention a lost connection; it might arrive as a sequence of delivery failures. A poem about memory might use a loop that cannot exit. A poem about prayer might become a request sent to an address that does not exist and yet somehow answers.
Sondheim’s public practice is also part of the work. The notes describe a body of writing sent daily to mailing lists over two decades, with subject lines preserved and the room left in. That matters because a listserv is not a book-shaped silence. It is a social machine. It has replies, objections, fatigue, filters, delete keys, mistaken readings, and witnesses who did not all consent to the intensity of the flood. The poem is therefore not only the text of a message but the event of transmission: who received it, who resisted it, who deleted it, who became implicated by continuing to read.
The altered bylines make this especially clear. Names such as Alan+++Sondheim, Alan /dev/null Sondheim, and Alan rm -r Sondheim turn authorship into an operation. They do not only rename the poet. They make the name behave like code. The self is appended, discarded, recursively removed, or made executable. In a tradition that often treats the poet’s name as a stable guarantee of identity, Sondheim shows the name becoming unstable inside the same technical system that carries the poem. A poet can learn from this without copying his signatures. The broader method is to let the byline register changes in state: author as draft, archive, interrupted session, ghost account, recovered file, unsent message.
Sondheim’s avatars extend that instability. Figures such as Julu, Jennifer, and Nikuko are not merely characters in a conventional dramatic monologue. They are distributed selves inside a networked text. Each can have a different relation to the body, the machine, the memory, and the authorial account. The result is not disguise for its own sake. It is a way of asking whether online speech ever belongs to one unbroken person. If a speaker can be renamed, reposted, forked, misread, and archived, then identity becomes a textual process rather than a fixed possession.
That process does not make the work cold. On the contrary, the notes insist that Sondheim’s writing is bodily, erotic, wounded, funny, obsessive, and unembarrassed. This is crucial. Codework becomes powerful when formal systems collide with what they cannot tidy up: sweat, shame, appetite, mourning, faith, breath, disability, aging, and desire. A command line is clean until the hand shaking over the keyboard enters it. A database is orderly until grief begins naming the same absence under too many filenames. A protocol is abstract until the body needs to be received and cannot be.
For Sarah B. Royal’s own experimental practice, Sondheim’s methods offer a vocabulary of permission rather than a template. Royal’s existing interests in codex structures, mathematical forms, recursive definition, devotional answer, fusion, and constructed constraint can meet Sondheim’s codework at the point where systems become spiritually and bodily charged. Mathematics, scripture, dictionary, palindrome, and command line can all become modes of pressure. The poem can ask not only “what does this form mean?” but “what does this form do when it touches a living soul?”
One useful application is dictionary recursion. A poem built from definitions can become more than a chain of meanings if the definitions are treated as commands, calls, or unresolved functions. “Necessary” can call “essential,” which calls “necessary,” and the poem can reveal the loop as both logic and longing. The error message is not a joke at the poem’s expense; it is the poem’s insight. Human beings often live inside recursive definitions: love proves need, need proves love, wound proves memory, memory reopens wound.
Another application is devotional codework. A prayer poem can borrow system language without trivializing faith if the system’s failure is made theologically meaningful. “Request timed out” might become the speaker’s experience of silence, but the poem should not stop there. It can ask whether silence is absence, delay, refusal, or a form of answer the current protocol cannot parse. In this way, error becomes a spiritual test rather than a clever screen effect.
A third application is mathematical embodiment. Royal’s interest in mathematical poetry can be joined to codework by treating equations as fragile forms of desire. Limits, sets, imaginary numbers, recursion, and cardinality can hold emotional argument. The imaginary number can become a real pressure in the poem because the speaker’s missing beloved, missing self, or missing God is also present through what ordinary counting cannot include. This kind of poem should not merely insert symbols. It should make the symbols bear the burden of the speaker’s experience.
The danger in using Sondheim’s techniques is superficiality. A poem full of slashes, brackets, broken tags, and error codes can become thin if the system language does not alter the poem’s emotional logic. The best test is simple: remove the code. If the poem means the same thing without it, the code is decoration. If removing the code collapses the poem’s argument, then the technique is doing real work.
Sondheim’s continuing usefulness lies in that demand. He shows that a networked poem can be excessive, public, unstable, embodied, and alive to its own machinery. He also shows that the machine does not cancel the human. It intensifies the human by forcing language to pass through structures that can store it, damage it, multiply it, and refuse it. For a poet editing this material in Sarah B. Royal’s name, the invitation is not to become Sondheim, but to let the poem’s chosen systems become active participants: dictionary as loop, equation as wound, prayer as failed transmission, avatar as divided soul, byline as changing state.
The system message becomes lyric when it is no longer outside the poem. It becomes lyric when it names the exact place where the human request meets a structure that cannot fully understand it. In that encounter, the poem does not merely speak about technology. It returns from technology altered, carrying the pressure of both body and code.