111–120 of 457 posts
That's so weird... This doesn't at all match my experience with Claude. I've never seen it behave this way.
You were right to push back. It's not an accurate representation of claude. It's satire.
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…
It made me stop using Claude at all. Codex has almost surgical precision, and I like that a lot.
(But nowadays I just use DeepSeek Flash. it does screw up but its cents so ¯\_(ツ)_/¯).
To be fair I’ve worked on human programmed systems where similar “it should be a half point story” requests would be met with snark by the engineers and take 2 sprints. I guess we are all PMs now.
Also likely, devs took shortcuts to deliver fast. Now to make the button blue they need to differentiate primary buttons from others. Simple, right? But design guidelines prevent one offs, and no !important. So you create a CSS class, but you discover another element on the header declared itself as primary (the search icon or the sign in button). You talk to that team and they decided to scope what’s primary accordi…
This is actually what keeps people using AI: variable reward schedule. It's basically gambling.
That's so weird... This doesn't at all match my experience with Claude. I've never seen it behave this way.
Usually just restarting the session helps, though.
To be fair I’ve worked on human programmed systems where similar “it should be a half point story” requests would be met with snark by the engineers and take 2 sprints. I guess we are all PMs now.
Also likely, devs took shortcuts to deliver fast. Now to make the button blue they need to differentiate primary buttons from others. Simple, right? But design guidelines prevent one offs, and no !important. So you create a CSS class, but you discover another element on the header declared itself as primary (the search icon or the sign in button). You talk to that team and they decided to scope what’s primary accordi…
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.
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…