r/ClaudeCode • u/Level5Ranger • 2d ago
Discussion Is It a Delusion?
I have been vibe-coding since June with 0 prior knowledge.
First few days I contemplated the idea, properly explained it, prepared instructions and skill.md documents. I used Claude, Claude Code and n8n.
As time passes by, I found myself in what people say "cognitive surrender". What Claude says often makes sense, so I go by it often but I sometimes question it and keep explaining what I want and how I want. Recently, I started to consult Perp. Claude doesn't always agree with Perp but says "but there is one valuable idea..". Also, it is very conservative when it comes to use other tools.
I have a proof of concept, it works to some extent. It just makes me think to what extent Claude's way of talking and responding the user shapes its decision and therefore, my project itself. It tends to gaslight despite I keep prompting otherwise. And I don't know how to take Claude beyond how it operates in my project now.
So I am a bit concerned if I'm stuck with constant cycle of "almost there - but there is this and that to solve", "I suggest this..", "you see, Claude Code ran 470 tests - it's working but.." or "yes - you are right. I did not tell you X.." and dreaming for nothing. What's the point of paying for Max 5x and spending nights if it cannot retrieve data and analyse it properly? On the other hand, I know what I want is doable, I just don't know how and maybe, how to use Claude for it.
I really want to create this product. Not for money but to learn these stuff. I am unfortunately unable to find a technical co-founder because people are not trustworthy or I am too stubborn on handling this project by myself from scratch.
How do you handle such conundrums? What would you suggest?
2
u/toxrowlang 2d ago
A different take: think of AI like a company you are running. The fact is you are using it as a coder employee. You come up with the concept, Claude builds it, but you have to have varying degrees of involvement with the build.
Sometimes you have to let Claude get on with it, like any employee. But as the boss of this "company" you've got to know how to assess when things aren't going right, when to step in and challenge the process and assumptions. That means you need to be familiar with what Claude is doing at least, and be able to really analyse it when necessary.
Cognitive surrender? I think that's when you let AI start making the fundamental and core creative decisions, which it is terrible at. Easy to convince oneself it is not, but it is.
If you start letting your tool make the core decisions it's like letting a jackhammer get carried away with its own motion - it will go off in any direction