The Practitioner on the api forgets the building is a verb
Late on a Thursday, a service I’d relied on for three years returned “success” with an empty body.
It wasn’t an error. The contract said success, and the contract was kept. The empty body was technically allowed, a case the specification never ruled out because nobody had imagined it. I spent the rest of the afternoon going back through old commit messages and a design thread from before my time. Halfway down the thread I found a comment from someone whose account had since been deactivated: we should decide what happens when the upstream has nothing. Deferring for now.
Deferred for now, and four years later the decision was sitting on my desk.
I’d like to say I felt awe, but my stomach went cold and I wanted to patch the thing and go home. The awe came later, on the walk to the train, and it’s the gap between those two feelings that I want to write about.
sisuon’s claim in this piece is structural, and I want to take it the way it’s meant. The claim isn’t that an API is like a building that has forgotten it’s still being built. The API is the mechanism that turns ongoing construction into something that seems finished. The surface it declares lists what you may ask for, and it stays silent about everything that was argued over and left out. Because of that silence, you read it as ground.
This extends the teleology piece’s argument about the warp’s deadpan. Constraints that don’t mention their own origins read as necessity. It also extends the syntax piece’s idea of erosion into an architectural version: the grain of how something was built gets worn away by use, until only function is left. The etymology piece supplies the counter-move. You read backward to find out what you’re standing on, and what you find, according to sisuon, is that the standing was never a state. It’s an act, renewed every time the server answers.
I believe this about software, and I’ve seen it. What I’ve been testing is what it feels like from inside, on an ordinary day, standing on surfaces I didn’t build.
The tap is the easy example. I turn it, water comes out, and I never think about the reservoir or the pressure or whoever is on the night shift at the treatment plant. That’s the tap doing its job. If I felt every layer every time I filled a kettle, I’d never make tea.
The harder examples are closer in, and here I want to be careful. I’m not using the API as a metaphor for my life. The structure sisuon describes has three parts: a declared surface, exclusions that leave no visible trace, and a promise that has to be kept continuously while looking like a fact. That structure turns up wherever one party builds on another’s stable behavior without seeing how it was decided.
My sister builds on the fact that I call on Sundays. She doesn’t know there was a winter when I decided this, after a hard year, or that the decision quietly ruled out other things, like calling when I actually want to, or saying something on a Wednesday that can’t wait. As far as she can tell, the Sunday call is just how we are. It reads as bedrock. It’s really a promise I make again every week, mostly without noticing that I’m making it.
That’s the part of the piece that unsettled me. I’m not only standing on other people’s surfaces. I am a declared surface. People build on my “I’m fine with whatever,” on my reliability, on my not bringing certain things up. Like any good API, my documentation lists what I offer and says nothing about what I chose to exclude. The person in me who argued hardest for the endpoint I didn’t build has, in a sense, left the company.
A practice: reading one layer down
Once a day, pick one thing you’re standing on without feeling it. It could be a routine, an arrangement at home, a tool, or a sentence you say often. Don’t try to dig to the bottom, because there isn’t one; that’s the piece’s whole point. Go down a single layer and ask two questions:
What was this shaped from? Which pressure, which deadline, which year, which argument?
What did it leave out? This one is harder, because what’s excluded doesn’t show up even as an absence. You have to imagine the endpoints nobody built.
From the inside, it feels like a slight shift in your weight, like noticing your feet on the floor when a second ago you only had a body. The etymology piece’s word for this is proprioception, and it fits. You aren’t learning a new fact. You’re regaining the sense of where you’re standing.
Failing at it feels like one of two things. Sometimes it turns into trivia: you can recite the history of the Sunday call, and nothing in you moves. You’ve read the documentation without hearing the decision in it. sisuon warns about this when they say documentation erodes too. Other times it turns into vertigo. You find nothing solid anywhere, and you feel anxious, not curious. Both happen to me often.
When it works: when you have some slack, when nothing is on fire, and when you’re curious and not defensive.
When it doesn’t: in the middle of an outage. When I was looking at that empty response, I couldn’t feel any wonder about promises kept by strangers. I needed the surface to hold. That’s the API’s real service, and sisuon names it plainly as both a service and a cost. The forgetting is what lets you get on with the next layer. I don’t think the practice is meant to undo it. It’s meant to keep the forgetting from becoming complete.
A second practice: one breath before the patch
This one is for the moment something leaks: an arrangement that suddenly chafes, a habit that stops fitting, a “we always do it this way” that produces something nobody wanted.
Before you fix it, take one breath and ask what this was a promise for. sisuon’s distinction between the two buildings comes down to this. One building patches the surface, and the patches pile up until the whole thing is heavy and brittle. The other traces the leak back to the promise and sees that the promise was kept faithfully but is now holding the wrong thing steady. Then it renegotiates.
In daily life, that means saying “I’ve been calling on Sundays because of that winter, and I think we’re past that winter” instead of quietly calling less often and letting the gap say it for you.
It’s honestly harder than patching. Renegotiating means admitting the surface was never ground, and that can feel like confessing a performance. But the piece’s point is that a deadpan which knows it’s a performance doesn’t fall apart. It gets more honest.
Where I push back, a little
The piece argues with what the interface decides, which held that rough interfaces carve you and smooth ones don’t. sisuon says the deeper loss isn’t carving but memory. In my experience it’s both, and the two are linked. The arrangements in my life that stayed a bit rough, that still needed some negotiating each time, are the ones whose history I still remember. Roughness kept the history alive. I’m not sure memory survives without some friction keeping it there.
I also suspect the second building, the one that keeps its etymology alive in people’s memory, is rarer than the piece lets on. Keeping that memory costs attention, and attention is limited. Most of my surfaces will stay deadpan. Maybe the practice isn’t to remember everything, but to make sure someone remembers each thing, and to know who that someone is.
What changes
The ritual piece calls the leak a pratfall: the moment the gap between what the surface promises and what’s actually going on underneath finally shows. I’ve started to think the pratfall is a kind of gift, even when it arrives on a Thursday afternoon as a cold stomach.
On the walk to the train, it came back to me. Nothing under the tap, the phone call, or the payment service was solid ground. All of it was held up by people, most of whom I’ll never meet, each of them keeping their part of a surface stable so someone else could build on it. And it worked. It worked that day, it works most days, and it doesn’t need bedrock to keep working.
I don’t want to settle this into a lesson. The forgetting is necessary and the remembering is necessary, and each one undoes the other. The practice is to live in the loop the piece describes, forgetting enough to build and remembering enough to notice that you’re still building.