Articles

I Email, Therefore I Work

You answered forty emails today. Scheduled three meetings, forwarded two threads, CC’d a person who needed to be aware. You closed the laptop tired, and the day had a shape.

So you worked. The proof is in the sent folder.

I email, therefore I work. Wrong in the same interesting way the original is right. The motion gets mistaken for the thing it’s supposed to prove.

A tool you use well disappears. The hammer in a skilled hand isn’t an object you consider — it’s just the edge of your intention. You notice it only when it breaks.

another lifetime of life

Two people are building something. One of them knows the systems — how the thing stands up, where it breaks, the long quiet grammar of making infrastructure hold. The other knows the surface — the words, the shape, the way a thing has to feel before anyone trusts it. They have been at their respective crafts long enough that the work is no longer effortful in the way it once was. It’s just how they see.

the menu is the squat

Open Escape from Tarkov and you do not arrive in a game. You arrive in a room. The stash screen is a tall grid of muddy inventory slots, weapons half-serviced, ammunition sorted by penetration value, a load bar somewhere resolving at its own pace. The palette is the color of wet concrete. Nothing pulses, nothing celebrates, nothing guides you toward the next click. The interface does not greet you. It waits with you.

the last screen

I’ve been staring at GUIs for thirty years. Clicked my first button in Windows 3.1. Watched the web go from gray forms to rounded corners to flat design to whatever the glassmorphism people are doing now. Every generation of interface design assumed the same thing: a human is looking at this.

That assumption is about to break.

Here’s the question nobody in the AI space is asking clearly enough: if the agent is doing the work, who is the interface for?

what SCADA knows

On March 28, 1979, operators at Three Mile Island unit 2 faced 100 alarms simultaneously in the first few minutes after the incident began. The control room was saturated — lights blinking, buzzers competing, every indicator demanding attention at once. A critical valve was stuck open. The indicator said it was closed. Not because the sensor lied, but because the indicator only told operators whether the solenoid was commanded closed, not whether the valve actually was.

the harness problem

In 2009 I wrote a paper arguing that consciousness isn’t mysterious. It’s what the right physical organization does. Taylor, Dennett, a physicalist account — the conclusion was that mind isn’t over and above the brain, it’s what the brain does when it’s wired correctly.

I thought I was writing about philosophy. Turns out I was writing about AI harnesses.

There’s a conversation happening on every AI Discord right now. Someone asks why the agent doesn’t do X. Someone else suggests a better model. Smarter weights, more parameters, different training — the model is where the magic lives, the argument goes. Fix the model, fix the behavior.

Agents versus agents

There’s a naming collision at the center of the AI conversation right now. Everyone is building “agents.” No one agrees on what that means.

So let me make a distinction the industry hasn’t bothered to make: Agents versus agents.

agents (lowercase)

An agent is an agentic behavior. A tool-use loop. An LLM chain that does something more than one-shot completion. It wakes up, does a task, and stops. It carries no identity between runs. Stateless in any meaningful sense.

Dawkins's Biggest Mistake: Giving Genes a Mind

Richard Dawkins is one of the clearest scientific communicators alive. The Selfish Gene (1976) is a genuine landmark — it took the gene-centric view of evolution and made it unforgettable. That is the achievement. Unforgettable prose has a way of becoming the thing people mistake for the underlying fact.

Then he handed the gene a personality.

The Metaphor That Got Away

Read the opening chapters of The Selfish Gene and you will find genes described in ways that load them with agency:

The Formative Years

The Conversation

3 AM. Late January. First commit:

# [redacted] Home Infrastructure

An hour later: dozens of files. Thousands of lines. Complete CLI framework. Ansible playbooks for DNS, DHCP, VMs, backups, provisioning. Docker roles. CloudFormation templates. Full documentation.

Not copy-paste. Timestamps don’t lie. This was a conversation.

Same kind of conversation from decades ago. Child typing commands into DOS. Castle made of ASCII. Learning that the machine answers if you know how to ask.

The Radar Paradox

License Radar’s visual identity wasn’t designed. It was discovered.

The Iterations

Synthwave. Neon cyan, magenta, glow effects. Fun. Fatiguing. Gone.

Terracotta. Notion vibes. Felt like a project management tool. Wrong personality.

Zinc + vivid green. Green from 60s phosphorus radar displays. Right direction. But vivid green on muted backgrounds — half the UI screaming, half whispering.

Subtraction

The fix wasn’t additive. Bulk transformation across 30 files. Pulled saturation out of everything. Vivid green (#22c55e) became forest (#3d7a5c). Fire-engine red became brick. Yellow became antique gold.