Fun, and weirdness, with #VibeCoding
While processing the #Bitcoin blockchain, I have a function to compute the block reward of a given block. I asked it (Claude Code) to check around the time of the first halving, to make sure there wasn't any off-by-one error.
It was working correctly, and Claude Code was happy that it was working correctly, but then it suddenly panicked and decided that the logic was wrong, see the end of this first screenshot:
It followed up with this false claim, and tryied to add this off-by-one error in the code: "Ah! The issue is that at block 210000, height / 210000 = 1, so we're calculating 1 halving, giving 25 BTC reward. But block 210000 itself should still have the 50 BTC reward - the halving takes effect
starting from block 210001. "
I think responded with "i don't think that's correct. A few questions. Is the genesis block considered to be block 0 or block 1?"
and it immediately corrected itself:
I could give lots of examples like this, where it did stuff that was slightly crazy or just wrong, and I have to overrule it, but I guess I don't want to bore you all; I'm very new to VibeCoding and I guess all of you that already have more experience with it have already learned all these fun lessons.
For now at least, humans are still badly needed to help the coding agent. But that could change of course ...