Live data from Hacker News

Claude, change the “Add to Cart” button to blue

opusfived.dev

471–472 of 472 posts

Re: Claude, change the “Add to Cart” button to blue

#471

Earlier quoted context omitted.

> Please tell me that this is a grossly exaggerated parody, and that the tools don’t write like this, or do so many ridiculous things It's a pisstake, but (in the bits I read, and based on my own personal experience) the writing style is barely exaggerated, while the behaviour doesn't ring true at all.

The behavior, while slightly exaggerated, rings entirely true for me. From the other comments in this thread, it seems I am prompting poorly in a similar way to the options offered. I am guessing you prompt differently than what is shown in the game?

I'm not the person you were replying to, but yes. Let me show you the issue.

"Why is half the site blue now? I asked you to change one button."; half the site isn't blue, why would you say that? What would "half the site" even mean? Ironically even in this satire supposed to make fun of how Claude responds to prompts, it is smart enough to ignore that. A better prompt would be "Why are many parts of the site, such as the Cancel button, now also blue?", though in this case it doesn't matter as the reply would be roughly the same.

Next, Claude helpfully tells us we're dealing with a monstrosity of a codebase out of hell: "Seven components consume the token directly; another eleven reach it through aliases; three use it only in hover/focus state; and two appear to be accidental cross-role consumers" is such an insane codebase that the initial request was basically impossible to carry out.

Claude made that perfectly clear, yet the next prompt choice just ignores that fact. "Revert everything except Add to Cart. That is the whole task." It just explained why this is impossible. It had only made one change, so there is no "revert everything except X"; there's only a single change to revert, which would mean Add to Cart too would no longer be blue. The human just chose to ignore that. The other option is "I do not care about the token architecture. I do not care why it happened. Put everything back the way it was and leave ONLY the Add to cart button blue. Please.". This has the same issue; "Put everything back and _leave_ only the button blue" is an impossible ask, which it just explained to you. So if you really don't want to deal with cleaning up some of the mess, instead only adding on to it but getting your blue button, then you'd want to say "Revert the change you made, then make a new change that scopes the new blue color to only the Cancel button".

Ignoring the information it gives you, or telling it things that are incorrect, of course will lead to bad results. It's impossible not to.

Re: Claude, change the “Add to Cart” button to blue

#472

Earlier quoted context omitted.

It's extremely bespoke. Initial dev required talking to Claude. Now I add a ticket in the board, it makes me a mockup/writeup, I approve, and it gets me a temporary webserver, iOS/Android build, etc. to verify it. Review loops, agents that enforce my pet peeves and testing/debugging processes, etc. all run automatically... and then Codex strips down the prose at the end. There's not zero AI generated output, but it's…

So instead of talking directly, you talk indirectly through ticket ?

I’m of the feeling that talking directly to these things all day is a path to madness.

They talk to each other, come to consensus, and give me a structured thing to look at that has already been vetted and tested and screenshot evidence and a verification plan. It’s not conversational for me.

Post reply on HN