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.
Claude, change the “Add to Cart” button to blue
131–140 of 442 posts
Re: Claude, change the “Add to Cart” button to blue
#132Haha this is spot on how I've been feeling lately. I find it unbearable to work with this model for this reason... any trick out there you can do to steer it not to overcomplicate things? I guess Codex here I come
`/model claude-opus-4-7`
This isn't a defense of it doing those four other things. It would be nice if it did what you wanted correctly. I'm just saying, as long as our programming skills have not completely atrophied, we have the power.
“Ford carried on counting quietly. This is about the most aggressive thing you can do to a computer, the equivalent of going up to a human being and saying "Blood...blood...blood...blood...” ― Douglas Adams, The Hitchhiker's Guide to the Galaxy
Re: Claude, change the “Add to Cart” button to blue
#133Do people really prompt AI like this? Multiple times the choice was either to yell at the agent, or ask it why it did something, neither of which are very fruitful lines to go down if you know what you're doing
Re: Claude, change the “Add to Cart” button to blue
#134Re: Claude, change the “Add to Cart” button to blue
#135> 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.
Re: Claude, change the “Add to Cart” button to blue
#136Earlier quoted context omitted.
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 b…
Re: Claude, change the “Add to Cart” button to blue
#137That's so weird... This doesn't at all match my experience with Claude. I've never seen it behave this way.
Re: Claude, change the “Add to Cart” button to blue
#138At 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?
Re: Claude, change the “Add to Cart” button to blue
#139Mine immediately did it correctly?
Re: Claude, change the “Add to Cart” button to blue
#140Earlier quoted context omitted.
Models hallucinate plausible answers to why they did things. It might be true and it might be complete fiction.
I'm growing increasingly confident that this is how people often work, as well.