I lose it after removing the ToS and the button becomes gray lol.
Claude, change the “Add to Cart” button to blue
441–450 of 452 posts
Re: Claude, change the “Add to Cart” button to blue
#442Earlier quoted context omitted.
You can, but this is public and maybe you should post. If "you are what you repeatedly do" then we all collectively are what we all do. If we each stop arguing with racists because we're each tired of it, then what we are is a society that lets racism go unopposed, a site with racist comments proliferating, a site where racists gather because they are able to be themselves, a site where future readers and AI training…
A few things: (1) I admire your energy, but sir/ma'am this is a Wendy's. (2) I am very confused that you thought I was talking about tolerance-of-intolerance types of conversations, when I was more intending to say "I don't need to write an essay responding to technical comments even if I think I have a different angle of technical insight than the commenter, and not worrying about that can be freeing." (3) For posts…
(2) I didn't think that, it was an example. I didn't want to pick a technology as an example and have my comment be dragged off into whether my pick was good or bad so I tried to pick something away from tech. As in "be the change you want to see in the world", if you want less FORTRAN enthusiasm, counter it, if you want more FORTRAN, add to it. It's easy to see that a site overrun with racism looks like a place that approve of racism, it's much harder to see that a site with 0.001% more FORTRAN content affects anything - that's what the voting comparison was about.
(3) I wasn't really meaning trolling, I was meaning your "someone is wrong on the internet" about some topic you are interested in / care about.
(5) I thought we were all on the "amusing ourselves to death, wireheading, Brave New World, hedonism is bad" train.
Re: Claude, change the “Add to Cart” button to blue
#443This is fun and hits too close to home, I can appreciate that Claude won't ever screw up this badly for something this simple but it's a simplification that captures the essence of the rage loop perfectly.
It's making me realise something new about why I find Claude so exhausting. Of course you're getting terrible results with these prompts but I found myself getting just as enraged contemplating what my reply would be. Estimating every single way this little asshole will hyper-focus on a pointless bit of semantics, ignore explicit directions, go do something unrelated and spin its wheels until you’re out of credits or wasted a ton of time.
The defensive writing is honestly just as exhausting as reading Claude’s output. Every session is a game of Russian roulette with a chance you'll end up in one of these loops. At that stage all the joy you had of having it pump along with your intentionally crafted prompts and agent configuration is undone in an afternoon.
Re: Claude, change the “Add to Cart” button to blue
#444People keep saying those prompts are unrealistic, and no one would prompt like that. But those prompts are exactly what my managers/product people would use when they decide to do it themself after firing the entire dev department.
Re: Claude, change the “Add to Cart” button to blue
#445Earlier quoted context omitted.
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?
You went off on a tangent and I responded. None of this is actually relevant to the topic of whether LLMs are “basically gambling”. > In what way was amazing no-traffic "a reward"? What system was rewarding you for what change in behaviour? What does this mean? Are you asking me to describe the dopamine system or are you implying that rewards have to be driven by some external system’s goal?
A reward implies it was given by something outside of your control. The lack of traffic wasn't a reward given to you, it's just a state of the highway.
Re: Claude, change the “Add to Cart” button to blue
#446Earlier quoted context omitted.
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.
>very disorganized codebases where small changes require major refactoring.
In the vibecode era, this is more common than you thought.
Re: Claude, change the “Add to Cart” button to blue
#447Earlier quoted context omitted.
So maybe it's more like poker than a slot machine? Still intermittent rewards with a lot of random chance. The nuance of the analogy isn't that important to the general idea
My point is that the analogy is inherently bad. The fact that LLMs are somewhat inconsistent doesn’t make them like gambling.
The LLM could one shot a brilliant solution, or it could lead you down a days long path to nowhere. It could give you accurate useful information or it could completely make up something that isn't at all correct. The fact that each usage is a dice roll where you have a desired outcome that will be fulfilled at a variable level makes it very similar to gambling. And in fact the part that makes it addictive is the near hits where the LLM comes very close to giving you what you want, but not quite there. That keeps you coming back.
Re: Claude, change the “Add to Cart” button to blue
#448Earlier quoted context omitted.
Is your harness available for install somewhere? Surely you still have to give feedback to Claude. How do you do that without talking to Claude directly? By using a different model? But wouldn't that AI have no more common sense than Claude?
It's extremely bespoke. Initial dev required talking to Claude. Now I add a ticket in the board, it makes me a mockup/writeup, I approve, and it gets me a temporary webserver, iOS/Android build, etc. to verify it. Review loops, agents that enforce my pet peeves and testing/debugging processes, etc. all run automatically... and then Codex strips down the prose at the end. There's not zero AI generated output, but it's…
So instead of talking directly, you talk indirectly through ticket ?
Re: Claude, change the “Add to Cart” button to blue
#449[flagged]
Re: Claude, change the “Add to Cart” button to blue
#450Earlier 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.
For one thing, it helps clarify my own thinking and uncover any gaps. For two, it lets me peek into its own understanding of the problem and ensure we are both aligned. For three, the garbage I spew at it is usually hastily typed crap from a mobile phone. So it helps clean it up and unpacks things.
It’s one one the main ways I know what’s cooking under the hood.
Ps: I used to have to say “in your own words” to make it work right but now days that isn’t required. Other times I’ll add “make sure to ground yourself before doing so” or something to encourage it to load the right shit into its context be it web, files, service calls, whatever. I’ll also some times add “why it’s important (or isn’t, push back if I’m talking nonsense)”