Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

opusfived.dev

Post reply on HN
Print view View original

231–240 of 448 posts

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

#232

Post by selestify »

plorkyeran wrote: post #146
johnisgood wrote: post #135

> Why is half the site blue now? I asked you to change one button. > Half the site is blue. I asked for ONE button. Those are my only options when the site is clearly not blue, two buttons are. There is a reason for why I am much more specific than this.

Yeah, if this is how people interact with claude I’m not surprised they’re having a bad time in ways that I don’t. Asking it why it did something or getting combative is a waste of time.

How does one learn to interact with Claude more effectively?

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

#233

Post by gedy »

pc86 wrote: post #201
RobKohr wrote: post #182

Earlier quoted context omitted.

If it takes more than 20 min to review a pr, ask the dev to come on a call and explain what the code does.

It must be nice to work on such small-scale systems that you can reasonably expect PRs to be this quick.

It's a cultural thing, but you can do incremental PRs towards a large goal. Giant PRs that are expected to be reviewed never really seemed worth it imho.

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

#234

Post by supern0va »

lathiat wrote: post #145
taeric wrote: post #119

Earlier quoted context omitted.

I'm growing increasingly confident that this is how people often work, as well.

“Post Hoc Rationalisation” https://www.patheos.com/blogs/tippling/2013/11/14/post-hoc-r...

Exactly. I am becoming increasingly convinced that this is actually just a part of how intelligence/cognition works.

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

#235

Post by selestify »

catapart wrote: post #102
kstenerud wrote: post #34

That's so weird... This doesn't at all match my experience with Claude. I've never seen it behave this way.

same. none of the available prompts are what I would prompt claude with and I get way better results than this. makes sense to me why the provided prompts result in the simulated outcomes. garbage in, garbage out.

So how would you prompt it instead? Because that's exactly how I prompt it, because any reasonable human being would know exactly what I mean by "Make the shopping button blue", and I am sick and tired of getting shitty results.

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

#237

Post by reedlaw »

_fat_santa wrote: post #84

At least with Codex, this has not been my experience at all. It still screws up sure, but in every case I can ask "why did you do this" and it can trace back what made it take that particular decision. Typically it's always that I either didn't specify the problem correctly or made a really dumb mistake (executing the task on the wrong project....did this one yesterday) or it's something within a skill file that inst…

Codex has the opposite problem. Instead of being overly proactive it's overly reticent. I have been preferring it lately, although my preference tend to switch every few months when a model or harness regresses horribly.

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

#238

Post by selestify »

teiferer wrote: post #97
dwringer wrote: post #63

Earlier quoted context omitted.

I only made it through the first round of prompt selection; both options for the second step were equally pointless and not at all prompts I would ever expect to result in a constructive outcome. In my experience, telling the model it screwed up without specifically addressing, unambiguously, how to fix it, only leads to more suffering. If this page illustrates nothing else, I think it shows the immense downside of t…

> In my experience, telling the model it screwed up without specifically addressing, unambiguously, how to fix it, only leads to more suffering. I wonder if this is just a reflection of some senior folks being arrogant towards junior folks. When the latter finished a task but not to the liking of the senior person they might just get a "that's wrong, try again". Just to have sth similar repeat the second time around.…

How is "Make the shopping button blue" not specific? Any human with a lick of digital common sense would be able to understand what I obviously mean. How am I supposed to anticipate every single way the AI could possibly misinterpret a simple fucking instruction like that?
Post reply on HN