Nobody Cares About the Code in the Box

Every great magic trick has three acts.

First comes the pledge. The magician presents something plain and lets you believe you understand it. A coin. A card. A locked box. Nothing suspicious, at least not yet. Then comes the turn. The ordinary thing refuses to stay ordinary. It disappears, changes places, or behaves in a way it has no business behaving. This is where everyone starts looking for the secret, which is funny, because most of us do not really want a diagram. We want the feeling of being fooled. But a disappearance is only half a trick. The hard part is bringing the thing back. That last act is the prestige. The thing you thought was gone returns, and for a second the room agrees to believe. Software development has a similar arc. The pledge is intent: the human need, the business rule, the outcome someone is hoping for. The turn is implementation: code, configuration, data, services, tests, and all the hidden machinery that makes the thing work. The prestige is the outcome: the user gets one of those small impossible moments, like the first time Shazam names a song from a noisy room or your phone identifies a house by simply taking a picture of it. For a long time, code was where the mystery lived. Most people could see the result, but not the mechanism. Developers understood the hidden machinery. The wand was a keyboard. The cape was mostly a hoodie. The mystery still worked. The better question is more practical: which parts of software work have been hiding inside the box, waiting to become tools? My bet is the code-shaped part. AI is getting good at producing the machinery: endpoints, migrations, tests, glue code, little refactors, and the thousand boring cuts that make a feature stand up. That machinery still matters. A trick with bad machinery is just an accident with better lighting. But it changes where I want to spend my judgment: defining intent, testing the result against reality, making architectural calls, and asking whether the thing is worth building at all. That is why I keep coming back to the phrase "the man in the box." 🏳️‍🌈 A quick note on language In The Prestige, "the man in the box" is the movie's wording. The phrase is not meant to exclude anyone. Developers are women, men, nonbinary people, and people with plenty of other ways of describing themselves. Here, it means the hidden role in the trick.

For a long time, code was the thing in the box. Essential, but not the thing anyone came to see. The audience was never there to admire the latch, the hinges, or the joinery. They were there for the impossible moment. Developers knew how the box worked. We knew where the trapdoor was, which latch stuck in winter, and why one "small change" to the billing rules could break an API contract, overload a SQL query, or wake up a workflow everyone thought had been retired. That knowledge mattered. It still matters. But the box is changing. The pledge The pledge is intent. It is the ordinary thing we show up with before the machinery starts moving: a business rule, a user need, a promise about how the software should behave. In real projects, the pledge is rarely a neat sentence in a ticket, no matter how many systems we use to pretend otherwise. We have put it in Jira tickets, GitHub issues, kanban cards, user stories, acceptance criteria, and meeting notes with dates in the filename. Then someone says, "Can we just..." and the room slowly discovers that "just" is doing a lot of cardio. This is where experienced developers earn their keep before writing a line of code. We ask what should happen, what must not happen, who depends on the current behavior, and which part of the system will wake up angry if we touch it. We remind people that the simple screen has a batch job behind it, that the API has outside callers, that the report nobody loves is still how finance closes the month. The pledge is also where we name what is easy, what is hard, and what is merely pretending to be easy because nobody has looked behind the curtain yet. That work used to feel like prelude. Increasingly, I think it is the durable part. The turn The turn is implementation. It is where intent becomes code, configuration, data, tests, services, and all the other machinery that makes software move. For decades, code was where intent finally became real, so we treated it like the main event. We wrote it, organized it, argued about it, reviewed it, and renamed things until the naming debate had its own weather system. We argued over tabs versus spaces as if civilization depended on the outcome. I used to obsess over alphabetizing methods. At the time, I honestly thought my OCD made me a better developer. I also treated duplicate code like a moral failure. Some of that discipline helped. Some of it was just me trying to make the file look sane because the business rules would not return the favor. Tooling changed that. Formatters...

Nobody Cares About the Code in the Box

Related Articles

(no title)

Is AI ruining our skills? Early results are in – and they're not good

The Anatomy of an AI-Native Org

Apertus – Open Foundation Model for Sovereign AI

The labor share of income in the US is at its lowest post-war level