The pull request is four thousand lines. You approve it in under a minute, because there are six more behind it and they all landed this morning from the same machine. You did not read it. You have not really read one in months. You are not sure anyone has.
This is what winning looks like now. The output graph is vertical. The team ships more in a week than it used to ship in a quarter, and every number you take to the board is bigger than last month's. The machine writes, and it writes fast, and by every measure you have, you are ahead.
But you cannot tell if any of it is right, because you cannot read as fast as it writes. Nobody can. The machine took the writing and handed you the reading, and reading was always the slow part, the part that happens one person at a time, at the speed of a single human mind.
Writing was never the deliverable. Understanding was. The document was just where the understanding got made, because you cannot write a thing you do not understand, not really, not past a paragraph. Getting it into words was how you worked it out, and when you finished, the document was almost a byproduct. The real output was you, now knowing the thing.
That is why a written thing could be trusted. Somebody had understood it into existence. Whoever read it next got that understanding cheaply, in far less time than it took to make, because the hard part was already done and laid out in order for them. Reading a good document is not the same work as writing it. It is the writer handing you the understanding they already paid for.
So making and understanding moved together, always. You could not run ahead of your own understanding, because making the thing was how you got there. The reader stayed close behind without trying, because you had already done the hard part. Nobody ever had to ask whether the words on the page were understood by anyone. The words were the proof.
The machine writes what it does not understand. What comes out looks exactly like work a person labored over, except no one did, and nothing was worked out along the way. The understanding that used to live inside the words is missing. The words read the same as ever. They just aren't proof of anything anymore.
That makes it harder to read, not easier. A person who writes something hands you their understanding already sorted into the order they found it. The machine gives you an artifact with nothing underneath, no reasoning and no order, because none went in. You have to build the understanding yourself, from the outside, with no help from the thing in front of you. That is closer to forensics than to reading, and it can take longer than writing the code yourself.
The reading cannot be sped up. The machine has erased every limit it could reach. This one it cannot, because the limit was never in the software. It sits in the person doing the reading, and people read at the same speed they always have. We have timed silent reading for a century, and it has not moved from a couple hundred words a minute. Code goes slower still. The largest study ever done on code review, two and a half thousand of them, found that past about four hundred lines a reviewer stops catching the defects. Not slows down. Stops. Your four-thousand-line pull request is ten times past the point where a person stops seeing the code at all. A sharper reader gets a little further before hitting the same wall, because the wall is one mind, and there is only one of those behind any pair of eyes.
You stopped reading. Not all at once, and not on purpose. The volume just won. There was always one more thing to approve, and reading each one properly would have made you the bottleneck, so you learned to skim, then to glance, then to trust the green check and move on. The machine writes faster than you can read. In the end that does not mean you read faster. It means you stop.
This is not laziness, and it is not only you. It is a known failure in how people work alongside machines. When something produces confident output faster than you can check it, you begin to trust it by default, and the trust deepens every time it turns out fine, right up until the time it does not. Researchers named this decades ago, long before AI: automation bias. Put a person next to a machine that is usually right, and they stop checking, and then they are not watching on the day it is wrong.
The output keeps coming, every piece carrying your name and none of it a human. Code no one has read is running in production. Next year's plan came out of a document no one finished. None of it is understood, and all of it is yours. You are on the hook for work no one in the building could explain if you woke them and asked.
Unread work is not knowledge. It is a rumor with your name on it.
No tool is coming to save you from this. The tool is the flood.
The fix is not a better tool. It is a rule you impose on yourself, and it is the one nobody has ever needed before: nothing counts as done until a specific human being has read it and understood it and will answer for it. Not shipped, not approved. Understood, by someone with a name who could be woken at night and would explain it. If no one can do that, it is not done. It is just something that has not gone wrong yet.
Which means producing less than the machine will let you. On purpose. This is the part that feels like sabotage, because every instinct you have been trained on says more output is better, and for your whole career it was. It is not anymore. Past the line where you can still understand what you make, more output is just more that no one understands, which is worse than nothing, because nothing does not run in production.
Use the machine to draft. That is what it is for, and it does it well. Then do the only thing that was ever the real work: read what it wrote until you understand it as if you had written it, and own it, or throw it out. The drafting was never the job. The understanding is the job, and it cannot be handed to the machine, because understanding has to happen in the head that will answer for it, and the machine answers for nothing.
The company that wins from here is not the one that generates the most. It is the one that understands everything it ships, and therefore ships less, and sleeps at night. Everyone selling you more output and more velocity is handing you a bigger flood and calling it a river you can ride. You cannot ride it. You can only drown in it quietly while the graphs stay green. Build less, understand all of it, and put your name only on what you could explain.
We build. They bill.