The self-reinforcing effect here was somewhat predictable given how LLMs are trained. The more repositories and AI blogs recommend the same tools, the more those patterns get locked in through training data. This makes market entry increasingly difficult for new tools.
I know that the "optimize for bots, not humans" strategy already exists, but I'm skeptical it works at meaningful scale. The training data collection is opaque, proprietary, and the volume a new project can generate is incomparable to what established tools produce organically. So I have a bad feeling about the future...
What Claude Code chooses
231–240 of 266 posts
Re: What Claude Code chooses
#232I've generally chosen these tools when I am creating a project. Though I generally use firebase hosting vs other front-end hosting. They have a much more generous free plan.
I'd suggest making some changes to how some of these things are categorized. You have database section with postgres at the top and then with supabase as number 2, but that's also a hosted postgres.
Overall, great job to the creators of this, I enjoyed seeing this analysis
Re: What Claude Code chooses
#233Earlier quoted context omitted.
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…
It is a valid concern. We are firmly in the goldilocks phase of LLMs, like in the first couple of years of Google when it was truly amazing. Then SEO made Google defensive, then websites catered to Google and not users, then Google catered to Google and not websites and we end up with 30 page recipe sites. LLMs are obviously different and will have different challenges, but their advantage is how deep into a user's r…
There wouldn't be an "ad" anywhere, though. You'll just ask the LLM for alternative implementations in plan mode, and it will be selling you one of them during the conversation rather than giving you an unbiased comparison. If you become suspicious it will make sure the pros just slightly outweigh the cons, or mention how well the thing works with something else in your stack, or whatever else a skilled salesperson would do to guide your choice without you realizing.
It's already doing this by telling everyone to use React and Tailwind, it's just that nobody's getting paid for it to do that.
Re: What Claude Code chooses
#234This 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.
how is it a conflict of interest for a google product to have a bias towards using google products? As users we must hold some accountability. AI is aiming to substitute for humans in the workforce, and humans would get fired for recommending competitor products for use-cases their own company is targeting. If we want a tool that is focused on the best interest of the public users, then it needs to be owned by the pu…
"Conflict of interest" isn't exactly the right term. "Conflict of value proposition" perhaps? E.g., you're using Google search based on the proposition it will effectively find things for you, but that turns out to be not what it actually does.
Re: What Claude Code chooses
#235Earlier quoted context omitted.
I use a skill that addresses these short comings, it basically forces it to plan multiple times until the plan is very detailed. It also asks more questions
Share?
Re: What Claude Code chooses
#236Earlier quoted context omitted.
Didn't you read? Don't give too simple one-shot prompts.
Share please? ;)
Re: What Claude Code chooses
#237[dead]
Re: What Claude Code chooses
#238[dead]
Re: What Claude Code chooses
#239Earlier quoted context omitted.
Glad I'm not the only one who finds Prisma an abomination. Claude suggested it to me in December. I hit half a dozen bugs within a day, one of which wiped my DB. I switched to drizzle and it's been smooth sailing. Edit: actually I think it was ChatGPT that recommended Prisma to me.
The software itself is bad enough, as a cherry on top the maintainers have a long history of astroturfing on Reddit to try and silence criticism. For a DB package . Come on man. Normally if maintainers do this they'll at least start with "Hey, maintainer here", but nope. Their whole mission is clearly "make the already easy things slightly easier, and the hard things harder or impossible". Or really "suck the VC teat…
It's crazy that prisma had 40k github stars last I checked. I haven't followed the js ecosystem that closely, but I thought stars would be some indication of quality, but no. It is totally unsuitable for any serious application. I've heard good things about kysely.
Re: What Claude Code chooses
#240And whatever Claude builds, it will run locally on port 3000. Always port 3000.