Live data from Hacker News

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

opusfived.dev

361–370 of 482 posts

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

#361

Great site, triggered memories! haha. To try to add something to this discussion -- I think that while I've seen these sort of loops less --- what I have seen is "overly helpful". Models nowadays want to double-triple-quadruple check things. I'm being silly but it verges on "I have a working solution but let me write a variation in Rust to ensure a convergent solution and prove this works". I've had to stop models no…

This is my recent experience as well. Models want to run linters, tests, etc. And that is all covered in GitHub actions. So I have been instructing agents to push a draft PR, then I validate the static checks pass and tell the agent if there are issues. Agents and AI are getting expensive, it seems silly to waste tokens on static checks.

Downside would seem to be that CI tends to increase the cycle time and feedback loop and add their own cost into the equation.

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

#363

I dont find this to be indicative of Claude (opus?) at all. My experience doesnt lead me to think it would change a cancel button to blue if I ask it to change an "Add to Cart" button to blue. I assume this is just a contrived example?

I think it's best read as a humorous piece of creative fiction and you can employ your suspension of disbelief for this ride

>I think it's best read as a humorous piece of creative fiction and you can employ your suspension of disbelief for this ride

But what is the point of the fiction, if not that its relatable? Is it supposed to mirror some fictional reality that the author is relieved we dont live in? Or is it supposed to parody real life?

I think its supposed to parody reality, but I don’t see the resemblance.

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

#366

Great site, triggered memories! haha. To try to add something to this discussion -- I think that while I've seen these sort of loops less --- what I have seen is "overly helpful". Models nowadays want to double-triple-quadruple check things. I'm being silly but it verges on "I have a working solution but let me write a variation in Rust to ensure a convergent solution and prove this works". I've had to stop models no…

This is my recent experience as well. Models want to run linters, tests, etc. And that is all covered in GitHub actions. So I have been instructing agents to push a draft PR, then I validate the static checks pass and tell the agent if there are issues. Agents and AI are getting expensive, it seems silly to waste tokens on static checks.

It seems running those tests, linters, etc locally would save pipeline minutes as well, like precommit hooks

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

#367

Earlier quoted context omitted.

"Plus rigorously ensuring backwards compatibility for a project that is 2 hours old and has zero users." That is exactly how the slop accretes and you get a pile of crap. Claude somehow assumes that said 2 hour old userless app is some dusty enterprise app with millions of users and billions of dollars at stake for a 1 second outage. I have to constantly have these things "take a deep breath, step back and look at th…

> please restate what i'm asking you to do and why it's important" This doesn't actually do anything though, right? There's no understanding, so the machine will just reiterate the original token query back to you. The 'why it's important' part will just generate some patronizing boilerplate as a raison d'etre.

The purpose of a prompt like that is to have it rephrase it in its own words, so you can spot any misunderstandings and correct them.

If you're of the belief that this is a contradiction in terms, then what can I say? It works.

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

#368
post #307

Earlier quoted context omitted.

> " Everything is variable reward. Is everything gambling? " well, no. If you work overtime and get paid overtime, you are not gambling and that is not a variable reward. Humans engage more with rewards that are intermittent and variable. Like Futurama's scene from 'The Scary Door' where the character says "A casino where I'm winning, I must be in heaven! A casino where I always win, that's boring, I must really be I…

> A constant predictable reward is boring, less engaging. Perhaps but predictable outcome is a very desirable quality. No one wants a hammer that sometimes drives nails and sometimes doesn’t. All of the current harness engineering work is about squeezing predictability out of the LLM. > Good traffic is not a "reward" for driving to work(!) Like hell it’s not. I drove into work last Friday and there was no traffic bec…

I think you're missing the point. Predictable outcomes are desirable, but they aren't addictive or gambling. People quickly get used to opening the faucet and seeing water come out and stop doing it, whereas people scroll TikTok or channel surf for hours at a time.

In what way was amazing no-traffic "a reward"? What system was rewarding you for what change in behaviour?

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

#369
post #108
post #79

I don't get who this is making fun of: - The people who won't make any effort to learn the tools, and something as simple as reverting code (via git) needs to be done by AI? - The awful programmers who we've had to endure working with, who are so bad at simple changes that they have negative productivity? - Or Claude itself? --- BTW: I don't have these problems, but I'm also not afraid to do things myself when it's e…

It's reductio ad absurdum , satirizing the Claude experience.

Then, IMO, the joke is lost: This feels like working with various forms of difficult, immature, indecisive, engineers; and possibly with very disorganized codebases where small changes require major refactoring.
Post reply on HN