Agreed, this site isn't reflective of any of my experience with Claude. It does what I ask it to do, and when it doesn't get it right, it generally turns out there's a good reason for it, which is any of the 100 reasons a human doesn't always get code fixes right on the first try either.

I do remember that one of the first things I did with my CLAUDE.md was to tell it to stick to the scope of the task, never to jump ahead and do extra "helpful" things without confirming with me first, and to follow best software practices including around refactoring but also to specifically avoid overengineering. I don't know if that is what's giving me a different experience from whatever the author seems to be "satirizing".

Aye, and amid all of the (admittedly annoying) word salad, the "Claude" in this satire identified the reason the requested change was hard: someone(s) at some point had hijacked the button markup for other purposes. Un-doing all of that kind of mess is never a trivial change, and probably requires someone with more coding expertise / knowledge of the code than the given prompts reveal the putative user to be.

AI isn't magic, and it won't (or, at least, doesn't yet) enable anyone to do All The Things.

I think this really was a relevant issue around a year ago, give or take, maybe a year and a half now.

But with current models you actively have to sabotage the context to get this kind of behavior, or dramatically underspecify (3 words versus 2-3 sentences)