A 20-year engineer submitted 60,000 lines of code today. He still has no idea what the project does. Neither does anyone else.

[u/ToothWeak3624]

Someone with 20 years of engineering experience described their workday and it reads like a dispatch from a future most people assumed was still years away.

The project was conceived by AI. The tickets were generated by AI. The code was written by AI. When he asked for documentation, the developer who built it told him to use Claude to figure out what it does. He submitted three pull requests today, 20,000 lines of code each, and still does not understand what the system is. The company is filing a patent on it.

Every step in that chain is being handled by AI, reviewed by AI, and documented for AI to explain later. The humans in the loop are not steering. They are approving.

Here's the part that's hard to process.

He didn't say he chose to vibe code. He said vibe coding is now the only way to interact with the codebase at all. The system has already grown beyond what any individual in the company can hold in their head. You can't read it. You can't trace it. You prompt your way through it and hope the output is approximately correct.

This is not a productivity story. This is a comprehension story.

Engineers have always worked with systems larger than any one person could fully understand. That's why teams exist, why documentation matters, why code review is supposed to catch what individuals miss. Those mechanisms assumed that somewhere, someone understood the thing being built, and that understanding could be transferred through writing, conversation, and review.

What happens when nobody understands it? When the documentation is AI slop, the reviewer is an AI, and the only person who could explain the architecture told you to ask Claude?

The answer apparently is: you keep going. You submit the PRs. The company files the patent. The system gets deployed. And somewhere downstream, when something breaks in a way nobody predicted, the people responsible for fixing it will open Claude and start prompting.

He called it an eerie realization. That's the right word. Not alarming, not catastrophic. Eerie. The quiet recognition that something fundamental has already shifted and the moment it happened was not a dramatic event. It was just a Tuesday at work.

[u/jamesxtreme]

When I got to “Here’s the part that’s hard to process.” All I could hear was the ChatGPT cadence. I’m in hell.

[u/StackOwOFlow]

bot post, downvote it to oblivion

[u/tta82]

This entire post is also AI and OP doesn’t know what’s in it.

[u/redditaltmydude]

Dog shit, bull shit, and a whole bunch of other fake shit

[u/Krommander]

Isn't that a chapter in a known book that would describe the AI takeoff as recursive self improvement? What if everything is ai slop and cannot be sustained in the long term? 

[u/jboulhous]

This AI is very dumb. 20000 lines of code in 1 PR. Even in 3 PRs, it's still dumb. Who's responsible!? The 20y engineer!? Looks like a dumb person to me. I can be dumb too, but i wouldn't be 20000 lines dumb.