Dirty Computr — The Human Variable

Your AI didn't
get dumber. You did.

There's a moment — a few hours into the work — when the machine seems to fall apart. It didn't. You did. I gave the thing that's actually happening a name.

Read the theory

The Theory

PHANTOM
DEGRADATION.

The decline you swear you see in the AI is a mirage1. The model runs identically on hour one and hour ten. What changed is the person at the keyboard.

The mechanism — Operator Drift2
01

Your prompts get lazier. A paragraph of context collapses into "no. fix it."

02

You become a worse editor — and stop catching the mistakes you'd have caught an hour ago.

You feed it worse and review it worse. The output never dropped. Your standards did. The machine is just a mirror.

1 — Borrowed from materials science, where "phantom" loss describes apparent degradation that's actually an artifact of how you measured — not real damage.

2 — Borrowed from safety engineering: "drift," where operators slowly deviate from sound practice without ever noticing they've moved.

Field Diagnostic

You've drifted if —

Two or more? Close the laptop.
The next hour is debt.

Who / What

Dirty = the human.
Computr = the machine.

dirty computr is one person in three trades. By night, a recording artist. By day, a full-stack engineer who ships the product — and an identity & access security leader who decides who's allowed to touch it. I've built both the software and the unglamorous plumbing of digital trust, for organizations at scale.

Now I think out loud about the messiest, least-audited variable in any system: the human holding the keyboard. Phantom Degradation is the first idea. There will be more.

Follow The Work

Stay in the loop.

The Day Job

All of this, shipped as software — gatekeep, the layer that decides what your AI agents are actually allowed to touch.