What You Owe the Strangers Who Run Your Code
The build tells you it works. Nothing tells you what it does.
You write the function, run the suite, watch it go green.
I have argued before that the compiler is the one judge you cannot talk past. A tired reviewer can be worn down. A manager against a deadline can be managed. A failing test cannot be negotiated with. I still believe that, and I left out half of it.
The judge answers one question: Is this correct?
It has never once answered what the correct thing does to anybody.
Nothing else in the pipeline answers it either.
Hierocles Drew Circles
There was a Stoic in the second century named Hierocles. Nearly all of him is lost. One image survived.
Picture yourself at the center of a set of rings. You, then your household, then relatives, then neighbors, then the city, and at the far edge everyone else. Strangers you will never meet.
Drawing the rings was not the point. He wanted you to pull the outer ones inward, to treat someone further out the way you would treat someone a ring closer. His method was oddly specific. Change what you call them. Address the cousin as a brother, the uncle as a father. Fix the language and let the feeling arrive behind the name.
He is not asking for impartiality. Closer stays heavier. The instruction is narrower than it sounds and it is achievable. Move one ring.
Now put a deployment in the middle of that diagram.
In his world, distance and effect traveled together. The stranger sat at the far edge because your life did not reach them. The rings measured closeness and consequence at the same time, because those were the same measurement.
They are not the same measurement anymore. The person at the outer edge of your rings is living inside a decision you made in ninety seconds and never revisited. The distance held. The effect collapsed. You reach the last ring hourly, at volume, feeling about it exactly what anyone feels about the last ring.
I am not standing outside this. Code I wrote years ago is still running and I could not name one person who runs it. Not a name, not a job, not a room they sit in. That does not make me negligent, it makes me a working developer. The job is built that way.
And our word for them is users. A container you can put a million people into and carry with one hand. Hierocles would have recognized immediately what that word is doing.
You Don’t Pick the Features. That Was Never the Obligation.
You did not choose the product. You did not write the requirements. You were handed a ticket with acceptance criteria attached, and the decisions that determine what this software does to people were made in rooms you were not in. Push back hard enough and often enough and you get managed out, and the thing ships anyway with somebody else’s name on the commit.
All of that is accurate. It is also the most load bearing excuse in this profession, and it is covering for a pile of decisions nobody made you make.
The timeout you picked without thinking, which decides whether someone on a bad connection finishes the form or loses everything they typed into it.
The error message you left as “An error occurred. Please try again,” read at eleven at night by somebody with no idea whether their money moved.
The validation rule you tested against your own name, which rejects a real one for having an apostrophe in it.
The retry that quietly swallowed a failure, so someone believes their submission went through.
Nobody assigned you those. No reviewer will comment on them. They take under two minutes each, and they are the parts of the system a stranger actually has to stand inside.
That is the obligation, and it is smaller than it sounded. Not the roadmap. The ninety-second decisions, and what you are willing to say out loud before the thing ships.
Nothing Will Prompt You
There will never be a ticket that says a human being is on the other end of this. The suite will not check for it. The linter has no rule. The retro will not get to it. Every prompt this job gives you points at the machine, because the machine is the part that answers in seconds.
So it has to be deliberate, and small enough to survive a normal week.
Before you close the ticket, take one pass through it as one person. Not users. One. Somebody with a bad connection, an unusual name, a reason to be doing this at eleven at night, and no idea what any of your words mean. Then read your own work back and ask what the next five minutes look like for them.
That is the practice. It costs a minute and it will not always change anything.
You still will not learn their name. That part is permanent. The rings do not close.
You pull anyway.
👉 If you enjoy reading this post, feel free to share it with friends!
Or feel free to click the ❤️ button on this post so more people can discover it on Substack 🙏
You can find me on X and Instagram.