2026-03-18 2331 OpenClaw, Vibe Coding, LLM and, so on

Recently I keep getting spammed by friends' recommendation for OpenClaw and my parents' anxiety about whether I will be lost my job. In short, I don't want to touch it, and I don't believe OpenClaw, Claude Code or something else will take over developers.

Let's describe a dream of a project manager in a big company: Everyday 8:00 a.m. he opens his agent teams and find one hundred OpenClaw agents work overnight and submit over thousands of PRs. All of these PRs are perfectly coded, well tested and magically make 0 tech debt. The only leftover "experienced" human developer just review these LLM's code everyday but do nothing, pm just decide to fire the last human in the team.

So, what's next?

One day the sun explode and the solar radiation flip a bit on the machine which cause a bug. Now the manager has a choice: push the whole codebase into the context window of AI, or push this piece of small part of code into the context window. The previous one will immediately generate a bill of token that can directly reach to the moon. The other one seems pretty reasonable, but anything outside that piece of code is totally black box to AI, and each time we do such kind of thing is creating knowledge gap between project, AI, and developers.

The point is AI will become less and less familiar with the project as the codebase getting bigger. Of course, human developers will face this problem as well, especially in high-turnover teams. But human does not need to learn the whole project from the beginning each time they sit in front of the screen, this compound effect takes time to show the benefit. LLMs, in the other way, has obvious marginal effect on this situation: you need to burn more and more tokens (dollars) to add a small piece of code in the context window.

Maybe one day, this manager will realize dream is just dream. Or actually they understand all of these things from the very beginning. But undoubtedly, developers will face a hard time, before LLMs really f**k up everything.

License & Copyright

cc_badge.png
This article is licensed under the CC BY-NC-SA 4.0 license. Embedded code snippets are released under the GPLv3 license.
If you share or adapt this material, please provide a link back to this original page. See the Full License Policy for more details.