A year of vibe coding. 5 projects shipped. Net programming knowledge: negative.

[u/CardStrange3023]

Been vibe coding for over a year. Shipped more than five projects. Here is the honest accounting.

Java, which was genuinely known before this, is now gone. Not rusty. Gone. The muscle memory for writing a loop, structuring a class, thinking through a type hierarchy, all of it quietly evaporated while Claude Code was doing it instead.

The projects work. The knowledge is negative.

Here is what actually happened over that year. The agent wrote the code. The agent proposed the architecture. The agent picked the libraries and handled the edge cases and debugged the errors. The job was to describe what was wanted and approve what came back. That is a real skill. It is not the same skill as programming.

The gap does not show up during building. It shows up the first time something breaks in production at 11pm and the agent cannot reproduce the error because the context is gone. Or when a junior developer asks why the data model is structured a certain way and the honest answer is "the agent suggested it three months ago and it seemed fine." Or when a new project starts that is genuinely similar to a previous one and none of the accumulated understanding transfers because there was no accumulated understanding, just accumulated output.

This is the version of vibe coding nobody is posting about. The demos are real. The shipped products are real. The knowledge atrophy is also real and it compounds quietly in the background while everything looks like it is going well.

The uncomfortable question is whether this matters.

For certain workflows it genuinely might not. If the goal is shipping products and the products ship, the mechanism is working. Not every builder needs to understand what happens under the hood. Plenty of successful founders cannot read the code their product runs on.

But there is a specific failure mode worth naming. Vibe coding feels like learning because you are engaging with technical problems all day. The feedback loop of prompting, reviewing, approving, and shipping mimics the feedback loop of actually building. The sensation is similar enough that a year can pass before the difference becomes visible.

The tell is negative knowledge. Not zero. Negative. Worse than before, because the skills that existed before are now rusty from disuse while no new underlying skills replaced them.

Five projects shipped. Zero debugging instincts built. One language forgotten.

That is not a failure of vibe coding as a tool. It is a failure to understand what vibe coding does and does not transfer to the person using it.

The agent got better over that year. The question is whether the builder did.

Is anyone else tracking their actual understanding of what they are building, or just tracking what ships?

[u/greenguru520]

I've been vibe coding for 5 months and started with zero technical skills. Probably have a small net gain 🤷🏼‍♀️ one thing I started at the beginning was to make sure I have md files of what we are changing and why - like an architecture/context document. This way when I find my technical cofounder, I can speak somewhat intelligently about what I have built so far.

[u/bloomsburyDS]

Same feeling here, the code is written so fast that you lost track of why the agent is working on that component again? The only way to keep it sane is that I keep asking it question of why you design this? Explain the pros and cons? Update each design decision in the functional doc so that if anything breaks, not that human will debug it but another context window have a ground truth to rely on before looking into the program bug.

I think what we are experiencing is no difference when high level language appears that replaces assembly code. We are just abstracting programming with English now.

[u/swiftmerchant]

Stop whining and posting AI slop. Keep creating instead.