I am quite honestly baffled by all these posts. I'm not a hardcore skeptic, at least I don't think so, I have tried most of the vibe coding tools, and I regularly try new ones and continue using many; and I do NOT have the experience described in all these posts. So two possibilities come to mind: 1. I, somehow, use every single one of those tools wrong. 2. Or; you and the other people raving about Claude code are so…
Sometimes you have to learn how to frame the problem in a way to get the results that you want. These tools need lots of context, not just about the rest of the code base but the problem itself. You can think of it a bit like how the early adopters of high level programming languages had to fight against compilers to get the assembly output that they wanted.
For example, if I tell an LLM to generate a python script that finds the square of a number I might want: def square(x): return x * x
but it may give me: print("Enter a number:") x = int(input()) print("The square is", x * x)
This is a very very simple example but I think it illustrates my point. If you provide enough context to the exact problem you want to solve the results are astronomically better.