The Machine Writes Now
Discover the paradox of progress as a coder grapples with the transition from creator to overseer in the world of machine-generated code.
I used to write code.
Now I describe code, and something else writes it. I sit back. I drink coffee. The fans spin somewhere in a datacenter I will never see, and the work gets done. It is faster than I ever was. It does not get tired. It does not care.
It is wonderful. I hate it a little.
For fifteen years the job was the same shape: a problem, my hands, a long quiet stretch in between where the two were resolved into each other. That stretch was the whole point. Not the output. The stretch. The hours where the thing was half-built and only I knew how it would end.
That's gone now. I state the intent. The intent becomes the artifact. The middle has been deleted.
Turns out the middle was where I lived.
People keep telling me to be excited. Look how much you can ship. Look how little you have to suffer for it. And they're right, and I am excited, and I ship more in an afternoon than I used to ship in a week.
But shipping was never the part I loved. I loved the suffering. The specific, stupid, pointless suffering of getting a thing exactly right by my own hand. You don't get a craftsman's joy from describing a chair. You get it from making one badly, then less badly, then well.
The machine makes the chair. I approve the chair. I am a man approving chairs.
I'm not going back. That's the part nobody warns you about — there is no door behind me. The skill I spent half my life sharpening is now a thing I gesture at. I am very good at gesturing. It pays well.
So I drink the coffee. It's good coffee. The code is good code.
And somewhere under all of it, quiet as a held breath, I miss being needed by the work itself.
The machine wrote most of this too. I just told it where it hurt.