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

121–130 of 442 posts

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

#121

Post by madibo3156 »

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.

Part skeptic and part zetetic, what prompt would you have used?

My impression is that this is an oversimplified demonstration of what can happen when you prompt Claude in a system with many more variables (than two buttons and two colours).

If I want the button to turn blue and that's it, what instead do I ask? Even in a complicated system with many levers, what do I request other than the desired end result, hoping that Claude pulls the right levers to produce something acceptably close to what I think I asked for?

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

#123

Post by theluketaylor »

tarxzvf wrote: post #112
_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…

Models hallucinate plausible answers to why they did things. It might be true and it might be complete fiction.

True, but even a hallucinated explanation of where things went wrong added to the context can force the model down a better path over the next few inputs.

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

#126

Post by blackenedgem »

malfist wrote: post #120
_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…

When you've been perfectly precise in your spec and language, isn't that programming? Why use a stochastic goblin to do things in that case?

See https://www.commitstrip.com/en/2016/08/25/a-very-comprehensi...

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

#127

Post by throwaway6977 »

malfist wrote: post #120
_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…

When you've been perfectly precise in your spec and language, isn't that programming? Why use a stochastic goblin to do things in that case?

It's just a lot faster at hammering it out than me pound for pound, and I can quickly rattle off via voice-to-text exactly what I want much faster than I can type all of the code (especially when across a few different files), in a huge majority of tasks I perform. It's also especially good at debugging by brute force quickly and at scale meaning e.g. it can start desperately bisecting diffs to find the source of a bug 10000% faster than I can.
Post reply on HN