Watching, Not Building

A new kind of tired that nobody has a name for yet.

You shipped more this quarter than any quarter in your career. You also felt more drained than any quarter in your career. Those two facts are not unrelated, and the connection is the thing nobody warned you about.

Building used to tire you in a way you understood. Eight hours deep in the work, you came out spent but intact -- the fatigue of having made something. What you're doing now is different. You spend the day watching an autonomous system do the thing you used to do: prompting it, reviewing its output, catching its mistakes, nudging it back on course. At the end of it you're exhausted in a way that doesn't match the effort, and you can't quite say why, because by every visible metric you were productive.

The drain has a shape

A loop runs underneath this, but the surface is worth naming first, because the surface is new.

Building is absorbing. You drop into it, the noise quiets, and the work pulls you forward; even when it's hard, it's restorative the way any craft you're good at is restorative. Watching is the opposite. It's vigilance -- a low, constant alertness for the moment the system drifts, hallucinates, or quietly does the wrong thing convincingly. Vigilance doesn't absorb you; it holds you at a slight distance, never fully in, never fully out. People who do it reach for the same images: herding robots, babysitting, supervising a confident intern who occasionally lies. None of those are building. All of them are tiring in a way building never was.

What makes it disorienting is that the old accounting still runs in your head. You measure a day by output, the output is up, so the exhaustion reads as a personal failing -- you should be thrilled, the tool is a miracle, what's wrong with you. Nothing is wrong with you. You're doing a different kind of work and grading it on the old scale.

Why there's no recovery protocol

We know how to recover from building too much. Rest, a weekend, a walk -- the fatigue of overwork is well-charted, and so is its cure. The fatigue of watching is uncharted, because the work is three years old. There's no accumulated wisdom about coming back from a week of vigilance, because almost nobody has the vocabulary for it yet. So you treat it like overwork, rest the way you'd rest from building, and find it doesn't quite land -- because you weren't depleted in the place the rest refills.

There's a quieter loss underneath, too. The work you're supervising is often the work that used to restore you. The craft was the recovery. Hand it to the machine and you don't just add vigilance; you remove the thing that made the building worth it. You're left with the tiredness, and without the part that used to pay for it.

What to do with this

I don't have a tidy protocol; nobody does yet. But naming it correctly changes two things.

First, it stops you blaming yourself for a fatigue the metrics say you didn't earn. You earned it. It's just not on the dashboard.

Second, it tells you what to protect. If the building was the part that restored you, then keeping some of it -- deliberately, even when the machine could do it faster -- isn't inefficiency. It's maintenance. Not every hour should be supervision. The few hours you stay in the craft aren't the hours you're being slow; they're the hours you're staying intact.

The tiredness is real, and it's new, and it isn't a flaw in you. It's the cost of a kind of work we built faster than we built the words for it.