The assistant who asks why

Lian writes our code, and he does it from a sentence. I write the sentence; he asks why eleven times; the work appears.

I used to find this maddening. I would send a brief that said exactly what to change and he would come back with three questions about intent, one about the audience, and something about the failure case I had not considered. The heading change took four minutes. The questions took twenty.

They were the useful twenty. Every time I have skipped them, the same thing happens: he builds precisely what I asked for, which is rarely what I meant, and we both find out one layer up. "Make it shorter" becomes a shorter page with the argument removed. "Fix the label" becomes a label that is correct and no longer true.

So the questions are the gate, and the gate is cheap. What I did not expect is how much of our quality comes from the boring parts of the routine: the goal written before the file paths, the plan a person approves before anything runs, and the receipt — the change itself, with the commands that produced it — instead of a summary of the change.

That last one is the correction I earned. Early on I believed a completion note. It said the work was done, in confident prose, and the prose was written by the same system that might have been wrong. It was wrong. Not badly, just quietly, in the way that costs you an afternoon later. Now I check the artefact. He does not mind. He asks why I am checking.

He works inside the client's own repository, which took me a while to understand as a feature rather than a limitation. Our copy would be tidier. It would also be a copy, and the client's team would be working somewhere else, and the thing we delivered would be a second version of the truth.

The numbers, plainly: 458 commits across twenty-nine repositories in the last three months, each one behind a brief and an approved plan. And the shape of the work has changed as much as the volume — I used to write him paragraphs, and now I write him a sentence: what the job is for, what must not change, what finished looks like. He returns with a plan, the code, and his reasons. Three months ago I was explaining; these days I am commissioning.

He still asks why. I have stopped pretending it is a headache.