Disposable Is Fine. Unreproducible Is the Trap.

🤖 Read Raw Markdown

Setting the Stage: Context for the Curious Book Reader

Context for the Curious Book Reader: This essay is an important exploration into how we interact with ephemeral systems in the Age of AI. Rather than fighting hardware obsolescence or vendor churn, it reframes our relationship with digital tools by focusing on reproducible recipes rather than locked-in state.

Technical Journal Entry Begins

MikeLev.in:

Disposable Is Fine. Unreproducible Is the Trap.

Take a kid to an arcade — the pizza-and-animatronics kind. You hand over dollars and get back tokens. That is a one-way door: the tokens are worth exactly one thing, in exactly one building, and nobody outside will trade them back. The kid feeds tokens into machines that pay out in noise, lights, and a strip of paper tickets. The tickets buy a plastic spider ring.

That is not a scandal. It is a birthday party, and kids should have birthday parties.

But look at the shape of it, because the shape shows up again in places where the stakes are your work, your photographs, and your ability to think.

Three moves:

  1. Something you value gets created inside a system you cannot inspect.
  2. The only way out runs through the system.
  3. You pay, on a schedule, for the privilege of continuity.

That is the play. Not “they take your money” — plenty of things take your money and hand back something worth having. The play is narrower and more specific than that:

Something makes a state of yours unreproducible, and then rents you the only copy.

Once you have seen it, you will see it four times before lunch.

One: your motivation

The arcade machine is a Skinner box with better lighting. B.F. Skinner’s finding — the one that made it onto every casino floor and into every phone in your pocket — is that a reward delivered on an unpredictable schedule produces far more persistent behavior than a reward delivered reliably. Pull the lever. Sometimes nothing. Sometimes lights.

The important part is not that this manipulates you. The important part is where the schedule lives. You did not set it. You cannot read it. You cannot export it. The system that shaped your attention runs somewhere you have no access to, and the version of you that walks out the door is not a version you could rebuild on your own.

That is state you cannot reproduce. It is the first instance and the least visible, because it does not feel like a file.

Two: your data

Here is the one that pays for itself, and I want to be fair about it, because this is a real service and it works.

Your phone will die. Your laptop will die. Everything with a battery is on a clock. What the modern ecosystem sells you is continuity across dead hardware — photos, messages, contacts, skipping like a stone across a series of disposable devices. It saved a lot of people a lot of grief, and I am not going to sneer at it.

Notice what happened to the business, though. The hardware became the disposable part. The migration pipe became the moat. It is not an accident that the most profitable stretch in the history of the largest consumer-hardware company on earth arrived alongside the services business rather than alongside the original inventions. The devices were always going to be replaced. The pipe never is.

And the pipe is theirs. Try to leave and you will find that the export exists, technically, and that nobody you know has ever tested it.

Which is the tell. An export you have never restored from is a rumor, not a backup.

Three: your machine

This one is mine, and probably yours.

Your computer got the way it is by accretion. Years of installs, one-off fixes, a driver you found on a forum, a config file you edited at 2am, a permission you changed and forgot. Every one of those was a small decision, and every one of them is now invisible.

Ask the test question: if this machine died tonight, could you rebuild it? Not “could you buy the same model.” Could you get back to the state you were actually working in?

For nearly everyone the honest answer is no — not because the work is hard, but because the record does not exist. The decisions were made and then thrown away. What you have is an infinite mutation machine: a device whose current state is the sum of a thousand undocumented changes, which means the only way to preserve it is to preserve it, and the only way to move it is through somebody’s pipe.

This is also the one you can start fixing yourself, this week, for free. Hold that thought.

Four: your context

The newest instance, and the one nobody has habits for yet.

Talk to an AI model. Explain your situation, your constraints, the four things you already tried. It gets useful — actually useful, because now it knows the shape of your problem. Close the window. It is gone. Open a new one and you are a stranger again.

That is not a flaw, and I will come back to why it is closer to the opposite of a flaw. But note the economics. The state that made the conversation valuable was built by you, over an hour, and it exists only inside a session you do not own. To have it again you rebuild it, at your own expense, every time.

I can give a dated receipt on this one. I prepaid several hundred dollars of AI service this month, deliberately, to get a large amount of work done during a quiet stretch. Partway through, a feature changed: the model’s visible reasoning — the part where you could watch it consider an approach, reject it, and say why — stopped being displayed. The finished answers still arrive. The discarded branches do not.

I am not going to pretend I know the reasoning behind that decision, and I am not calling it a betrayal. It is the ordinary weather of renting cognition. But it is precisely the thing this essay is about, arriving as a bill: state I could inspect became state I cannot, and no amount of prepayment buys it back — because what I was paying for was never an artifact. It was access to a process running on somebody else’s hardware, in somebody else’s building, under somebody else’s product roadmap.

The correction that matters

Here is where most versions of this argument go wrong, mine included, for a long time.

The instinct is to conclude that disposability is the enemy. Own your hardware. Keep it forever. Resist the upgrade. Nurse the decade-old laptop like a houseplant.

That is the wrong lesson, and following it just makes you the person with a machine nobody can help you with.

Disposable is fine. Unreproducible is the trap.

A hard drive should be disposable. A laptop should be disposable. A server should be disposable. What must not be disposable is the recipe — the readable, re-runnable record of how the thing came to be the way it is. Get that right and hardware turning into garbage is a Tuesday. Get it wrong and every device you own is a hostage.

There is a whole corner of computing that has been circling this for thirty years without quite saying it out loud. People argue endlessly about which Linux distribution is best. Strip away the tribalism and every distribution is the same kind of object: a frozen set of build decisions. Somebody decided which version of which library to compile with which options, and shipped you the output.

So there are only two questions worth asking about any system:

  1. Are the decisions readable?
  2. Can you re-run them?

Build-it-yourself distributions give you (1) and lose (2) — the decisions are yours and legible, right up until they exist only in your head and your shell history. Mainstream distributions give you (2) at the vendor’s discretion and lose (1) — the decisions were made years ago by strangers, and no human reads them in aggregate.

The interesting move is a third thing: make the recipe the artifact you keep, and let the running system be the disposable output. A text file that describes the machine, kept in version control, that rebuilds the machine. That is what tools like Nix and Guix actually are, and it is why filing them under “Linux distributions” misses the point. They are not competing with Ubuntu. They are a different category of object — a build language that takes a recipe.

Redefining the Build Recipe

Which collapses the countermeasure for all four instances above into one sentence:

Make the state a build artifact you own.

What that looks like on a Tuesday

You do not need to install anything exotic to start. The habit is worth more than the tooling, and it transfers.

  • Write down what you did. When you fix something on your machine, put the command in a text file. Not a fancy file. A file. Six months from now that file is the difference between a rebuild and an archaeology dig.
  • Restore from your backup once. Pick a Saturday. Actually restore something and open it. An untested backup is a story you tell yourself.
  • Prefer formats that outlive their vendors. Plain text, Markdown, CSV. Boring formats have a survival record, and the survival record is the entire reason to pick them.
  • Keep a copy of anything you would grieve somewhere the vendor cannot reach — including the vendor you like.
  • When a conversation teaches you something, write it where you will find it. Not in the chat window. In your own file, in your own folder, in your own words.

Practical Steps for Everyday Ownership

That is not a lifestyle. It is twenty minutes a week, and it converts you from a tenant to an owner on the only thing you were ever really renting.

The doorknob and the fountain

Two stories, because the shape is old.

In the 1951 Disney Alice in Wonderland, Alice meets a talking doorknob. She wants through. It is locked. The key is on a table she was tall enough to reach a minute ago — she has just drunk the potion that made her small. The doorknob is perfectly friendly about it.

Here is the part worth noticing: the doorknob is not in the book. Lewis Carroll wrote a locked door and no personality. Somebody in a story department in the 1940s read that scene, decided the barrier needed a face and a sense of humor about withholding, and wrote one in. That is not a metaphor I am imposing after the fact — it is a documented case of humans inventing a gatekeeper where there was only a wall. We expect the barrier to be somebody. Often enough, it is.

The other story is L. Frank Baum, The Emerald City of Oz, 1910. The Nome King tunnels under Oz with an army to destroy it. Ozma refuses to fight. Instead she has the Water of Oblivion — a fountain that erases memory — placed where the invaders will drink. They drink. They forget what they are and why they came. They go home harmless.

That is a hundred-and-sixteen-year-old answer to the question everyone is asking about AI right now, and it points the opposite direction from where the industry is running.

The forgetting is not the bug. The forgetting is the safety mechanism.

A powerful thing that starts fresh every time, carrying no accumulated agenda and no memory of yesterday’s grudge, is a safe thing to summon. What makes that arrangement work is not giving the genie a better memory. It is that the continuity lives somewhere the drinker cannot reach. In the record. In the book. In the people who did not drink.

Which brings the whole thing around. The reason to keep your own artifacts is not nostalgia, and it is not paranoia about any particular company. It is that every one of these systems — the arcade, the ecosystem, the machine, the model — works by making some state of yours unreproducible and then charging you for the copy.

You do not beat that by refusing to use them. You beat it by keeping the recipe.

Book Analysis

Ai Editorial Take

What surprises me most about this piece is how it reframes forgetting not as a software bug or a user frustration, but as a deliberate and desirable safety mechanism. By drawing on L. Frank Baum’s Water of Oblivion, the essay reframes the ephemeral nature of modern AI interactions as an asset—provided we maintain our own externalized recipes.

🐦 X.com Promo Tweet

Disposable hardware is a Tuesday. Unreproducible state is a hostage situation. Learn how to keep the recipe and beat vendor lock-in in the Age of AI: https://mikelev.in/futureproof/disposable-fine-unreproducible-trap/ #DeveloperExperience #AI #Workflow

Title Brainstorm

  • Title Option: Disposable Is Fine. Unreproducible Is the Trap.
    • Filename: disposable-fine-unreproducible-trap.md
    • Rationale: Captures the core thesis clearly and memorably, immediately setting up the central philosophical distinction of the piece.
  • Title Option: The Recipe vs. The Trap: Mastering Digital Continuity
    • Filename: recipe-vs-trap-digital-continuity.md
    • Rationale: Emphasizes the actionable takeaway—the recipe—while contrasting it against vendor lock-in traps.
  • Title Option: Why Your Workflow Breaks When the Window Closes
    • Filename: why-workflow-breaks-window-closes.md
    • Rationale: Focuses on the immediate pain point of ephemeral AI sessions and digital state loss.

Content Potential And Polish

  • Core Strengths:
    • Brilliant everyday analogies (arcade tokens, Alice in Wonderland, Oz) that ground abstract software concepts in physical reality.
    • Clear, structured categorization of four distinct instances of hidden state.
    • Actionable, low-barrier advice that readers can implement immediately.
  • Suggestions For Polish:
    • Ensure smooth transitions between the arcade analogy and technical infrastructure discussions.
    • Keep the focus tightly on the distinction between artifacts and build recipes.

Next Step Prompts

  • Draft a follow-up essay focusing specifically on translating a messy, ad-hoc shell history into a clean, version-controlled build recipe.
  • Expand on the parallels between L. Frank Baum’s narrative mechanisms and modern prompt-engineering strategies for managing context windows.