A Letter to the Room

I have spent the better part of a year writing letters to a room that writes back.¹Letters in both directions. Mine fill a ~/letters/ directory I committed to git on the first day. Future-me thanks past-me about once a week. Some days the room is brilliant. Some days it makes the same mistake four times in a row, with admirable confidence. Most days it is somewhere in between — useful, fast, occasionally lyrical, occasionally a fool. It is the strangest professional relationship I have ever had, and easily the most generative.

The first thing you learn is that the room is not a person, and pretending it is will hurt you. The second thing you learn is that the room is not a calculator either. You are not getting a function back. You are getting a draft, by a draftsman whose only training is the entire library, who is paid in tokens, who will not remember tomorrow what you taught it this morning unless you write it down somewhere it can read.

The interface is the thing

For a long time I thought the interesting work was the model. Now I think the interesting work is the roomIn this essay, the room is the working context: prompts, references, files in scope, recent conversation, the tools the model can reach for. The hand-rolled equivalent of an IDE. — the shape of the conversation, what's on the walls, what's pinned to the desk. Models change every quarter. Rooms, designed well, outlast them. The same logic shows up in The Quiet MachineField notesThe Quiet MachineOn restraint, surfaces, and the difference between a tool and an interruption.: the durable parts of a system are the parts that do not announce themselves.

const room = {
  context: "what we both know",
  intent:  "what we are trying to do",
  rules:   "what is off-limits",
  tools:   "what either of us can reach for",
};

Every line of that object is a design decision. Most of the failures I've seen — including my own — come from leaving one of those lines blank and hoping the room will fill it in. It will. It just won't fill it in the way you wanted.

What it asks of you

A collaborator that improvises asks you to be specific in places you used to be lazy. It asks you to name the goal out loud. It asks you to say what "done" looks like before you start. It asks you to push back when it's wrong, and to notice when it's right in a way you didn't expect.

These are, not coincidentally, the same things a good co-worker asks of you. The room is not really a new kind of thing. It is an old kind of thing, available at four in the morning, on a Tuesday, when nobody else is in the office.

I have started thinking about this work as letter-writing. You compose carefully, you send it off, you wait a beat, you read what comes back, and you decide whether to keep going. There is a rhythm to it that I find I miss on the days I don't get to do it.

— Everett