CHEAP CODE. EXPENSIVE BABYSITTING.

The real news

The story, straight

# Code is cheap. My attention is not.

I wanted a coding assistant. Somehow, I’m the assistant.

The machine writes the code. I explain the assignment, answer its questions, inspect the result, explain the assignment again, and investigate why changing the button also renovated the kitchen.

Apparently, “autonomous” means it can ask for my attention without assistance.

### THE ABSURD

**My assistant has promoted me to adult supervision.**

Every interruption begins with “one quick question.”

Individually, tiny. Together, a timeshare in my brain.

It can produce another version while I’m still remembering why I rejected the last one. It never gets tired.

This was presented as a benefit before anyone established whose sleep we were discussing.

Somewhere, a server is wearing a nappy and congratulating itself on making me more productive.

I asked for software. I got custody.

### THE BREAKDOWN

**Typing less doesn’t guarantee I’m needed less.**

Code is the set of instructions that makes software work. Writing those instructions is only part of the job.

Someone still has to decide what matters, check the result, and deal with whatever broke along the way.

That’s where the attention bill arrives.

Ten versions requiring ten inspections is a committee with a download button.

Here’s the useful measure: **how many minutes of my attention does each finished, working task require?**

Count explaining, reviewing, correcting, and recovering my train of thought. That last one keeps leaving the station without me.

Cheap output can still require expensive supervision.

### THE UPSIDE

**Give routine work rules. Save my attention for decisions.**

Set a clear finish line: what must work, what must be checked, and what counts as done.

Let the system handle harmless routine choices. Have it check its work before handing over the result.

Bring me the decisions where my judgment actually changes the outcome.

Automated checks can catch routine problems. I still need to judge whether we’ve built something useful.

Then count my minutes per completed task, including cleanup. If those minutes fall, the automation is earning its place.

I want one working result, fewer interruptions, and enough brain left to have an idea that isn’t, “Why is this asking me again?”

The server can keep the highchair. I’m taking my afternoon back.

Source: https://docs.github.com/en/copilot/responsible-use/chat