The self-congratulatory backslapping or glazing of the programmer, e.g. "Perfect! The thingamajig now frobbles before it frazzles, making this a much better experience for the user and improving the versatility of the system" (and of course accompanied by several lines with green checkmarks)...this drives me nuts. Why? Because it told me it's done all these things, so I adjust my mental model of the code accordingly. But then it turns out it actually hasn't done all those things at all.
If this was a junior dev you'd given a task to, and they came back full of praise for themselves for the stellar job they'd done - and then it turned out they'd botched it badly, after a few times you'd be having an HR discussion.
So instead, let all that stuff at the end of the task scroll by, train your eyes to ignore it, and just test whether it's working as intended. Claude Code is no longer my buddy, it's now a tool. Sanity is restored.
davydm•5mo ago
I don't think I'm an outlier either. I think most people using these tools are wasting their time having to debug hallucinated bullshit, instead of learning how to solve the problem themselves, by reading accurate, authoritative resources on the subject, ingesting and compiling that data, and experimenting to make it stick. It just feels like less work when the ai botches it and you have to fix it, vs the mental mountain you have to climb to truly get there, but the journey is overall more efficient when you do take the uncomfortable path.