Live data from Hacker News

What Claude Code chooses

amplifying.ai

201–210 of 266 posts

Re: What Claude Code chooses

#201

Earlier quoted context omitted.

I find they are very concerned about ever pulling the trigger on a change or deleting something. They add features and codepaths that weren't asked for, and then resist removing them because that would break backwards compatibility. In lieu of understanding the whole architecture, they assume that there was intent behind the current choices... which is a good assumption on their training data where a human wrote it,…

// deprecated; use ThingTwo instead type Thing = ... // deprecated; use ThingThree instead type ThingTwo = ... // deprecated; use... I do frequent insistent cleaning passes with Claude, otherwise manually. It gets out of hand so fast This is one reason why it blows me away that people actually ship stuff they've never looked at. You can be certain it's riddled with craziest garbage Claude is holing away for eternity

I found that having a rule like this helped some too:

> * ABSOLUTELY DO NOT use `@deprecated` on anything unless you are explicitly asked to. Always fully refactor and delete old code as-needed instead of deprecating it

https://github.com/yokuze/aix-config/blob/f5094b5c5169261fae...

Re: What Claude Code chooses

#202

What coding with LLMs have taught me, particularly in a domain that's not super comfortable for me (web tech), is that how many npm packages (like jwt auth, or build plugins) can be replaced by a dozen lines of code. And you can actually make sense of that code and be sure it does what you want it to.

So… this has been happening for a long time now. The baseline set of tools is a lot better than it used to be. Back in 2010, jQuery was the divine ruler of JSlandia. Nowadays, you would probably just throw your jQuery in the woodchipper and replace it with raw, unfinished, quartersawn JS straight from the mill. I also used to have these massive sets of packages pieced together with RequireJS or Rollup or WebPack or w…

I smell wood reading this

Re: What Claude Code chooses

#203
The patterns in this analysis ring true from running production AI agents. The stack choices (Drizzle, React, etc.) match exactly what our agents consistently pick, even with different prompts and contexts. What strikes me is how these biases actually help - having consistent, well-supported defaults reduces decision fatigue and keeps architecture predictable across projects. The real challenge is knowing when to override these defaults for specific requirements.

Re: What Claude Code chooses

#204
post #195

Earlier quoted context omitted.

Note I might be wrong on this one but it's just extremely annoying that I even have to consider if I am being manipulated by an AI while reading HN comments. If I want to read AI stuff I go to Clawdbook or OpenAIs Sora app.

Sure, and we've banned the account, but please email us with these hn@ycombinator.com. @mentions don't work on HN; I only saw it because I was looking through the thread. We're also asking people not to make these accusations publicly, partly because they take longer for us to see than an email, and also because a false accusation is more harmful than a valid accusation is beneficial.

Okay fair about the mentions but I don't that email is a good process:

1. It puts more effort on me as a user to report the spam via email because I have to open my email, compose one by hand and add the reasoning. The offending user in comparison probably automatically spams. Can't we have a button at least?

2. It doesn't make the community aware of the ongoing issue. Other community members could be primed that currently they need to read comments more critically. At the moment that seems like the only detection that somewhat works but if I silently send an email instead of commenting here it doesn't inform anyone else of my suspicion.

Re: What Claude Code chooses

#205
post #74

Earlier quoted context omitted.

That's called LLM SEO now I believe.

There are competing terms currently being decided on by the market at large: AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) Candidly I am working on a startup in this space myself, though we are taking a different angle than most incumbents. While it's still early days for the space, I sense a lot of the original entrants who focus on, essentially, 'generate more content ideally with our pa…

> There are competing terms currently being decided on by the market at large: AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization)

It really annoys me the industry seems to be narrowing in on the two worse options rather than AIO.

Re: What Claude Code chooses

#206
post #201

Earlier quoted context omitted.

// deprecated; use ThingTwo instead type Thing = ... // deprecated; use ThingThree instead type ThingTwo = ... // deprecated; use... I do frequent insistent cleaning passes with Claude, otherwise manually. It gets out of hand so fast This is one reason why it blows me away that people actually ship stuff they've never looked at. You can be certain it's riddled with craziest garbage Claude is holing away for eternity

I found that having a rule like this helped some too: > * ABSOLUTELY DO NOT use `@deprecated` on anything unless you are explicitly asked to. Always fully refactor and delete old code as-needed instead of deprecating it https://github.com/yokuze/aix-config/blob/f5094b5c5169261fae...

Is this put as your Claude.md file?

Re: What Claude Code chooses

#207
There's an interesting flip side to this: what happens when an AI agent encounters something that doesn't exist at all? I've been documenting an AI agent's daily experience, and one recent episode was about the agent discovering that a morning briefing script it was supposed to run simply wasn't there. How it handled that gap -- whether to improvise, halt, or ask -- turned out to be more revealing than any tool-choice benchmark. The choices Claude Code makes when things go wrong might be as interesting as what it builds when things go right.

Re: What Claude Code chooses

#208
post #15

This is where LLM advertising will inevitably end up: completely invisible. It's the ultimate "influencer". Or not even advertising, just conflict of interest. A canary for this would be whether Gemini skews toward building stuff on GCP.

Considering how little data needed to poison llm https://www.anthropic.com/research/small-samples-poison , this is a way to replace SEO by llm product placement: 1. create several hundreds github repos with projects that use your product ( may be clones or AI generated ) 2. create website with similar instructions, connect to hundred domains 3. generate reddit, facebook, X posts, wikipedia pages with the same informa…

This is the major point the anti-scraping crowd misses.

If you want your ideas to be appreciated, you should do everything in your power to put those ideas into the brains of LLMs. Like it or not, LLMs is how people interact with the world now.

Re: What Claude Code chooses

#209
post #80

Earlier quoted context omitted.

from my understanding Anthropic are now hiring a lot of experts in different who are writing content used to post-train models to make these decisions and they're constantly adjusted by the anthropic team themselves this is why the stacks in the report and what cc suggests closely match latest developer "consensus" your suggestion would degrade user experience and be noticed very quickly

That sounds too expensive to be viable when the giveaway phase ends.

That's how Google search worked back when it was at its most useful. They had a large "editorial team" that manually tweaked page ranks on a site-by-site basis.

The core graph reputation based page ranking algorithm lasted for a hot second before people started gaming it. No idea what they do these days.

Re: What Claude Code chooses

#210
post #186
post #15

This is where LLM advertising will inevitably end up: completely invisible. It's the ultimate "influencer". Or not even advertising, just conflict of interest. A canary for this would be whether Gemini skews toward building stuff on GCP.

In my last conversation with a Google support person, I was sent a clearly LLM-generated recommendation to switch to a competitor's product. Either they're not doing this, or the support person wasn't using Gemini.

It's standard practice for customer support people to chase away unprofitable customers (in the US; no idea how Google works). Human or LLM, they may simply not want your business.
Post reply on HN