Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What Claude Code chooses

amplifying.ai

Post reply on HN
Print view View original

41–50 of 266 posts

Re: What Claude Code chooses

#41

Post by Onavo »

prinny_ wrote: post #37

Unrelated to the topic at hand but related to the technologies mentioned. I weep for Redux. It's an excellent tool, powerful, configurable, battle tested with excellent documentation and maintainer team. But the community never forgave it for its initial "boilerplate-y" iterations. Years passed, the library evolved and got more streamlined and people would still ask "redux or react context?" Now it seems this has car…

Well, the tech du jour now is whatever's easier for the AI to model. Of course it's a chicken and egg problem, the less popular a tech is the harder it is to make it into the training data set. On the other hand, from an information theoretic point of view, tools that are explicit and provides better error messages and require less assumptions about hidden state is definitely easier for the AI when it tries to generalize to unknowns that doesn't exist in its training data.

Re: What Claude Code chooses

#42

Post by tommy_axle »

prinny_ wrote: post #37

Unrelated to the topic at hand but related to the technologies mentioned. I weep for Redux. It's an excellent tool, powerful, configurable, battle tested with excellent documentation and maintainer team. But the community never forgave it for its initial "boilerplate-y" iterations. Years passed, the library evolved and got more streamlined and people would still ask "redux or react context?" Now it seems this has car…

More like redux vs zustand. Picking zustand was one of the good standout picks for me.

Re: What Claude Code chooses

#43

Post by hyprwave »

HPsquared wrote: post #36
wrs wrote: 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.

I wonder if aggregators will emerge (something like Ground News does for news sources)

LLM pattern [0] will probably eventually emerge as the best way to fight those biases. This way everyone benefits from token burn!

[0](https://github.com/karpathy/llm-council)

Re: What Claude Code chooses

#44

Post by actionfromafar »

MeetingsBrowser wrote: post #30
layer8 wrote: post #23

Earlier quoted context omitted.

Advertisers will only pay if AI providers will provide them data on the equivalent of “ad impressions”. And unlabeled/non-evident advertisements are illegal in many (most?) countries.

It doesn't necessarily have to be advertisers paying AI providers. It could be advertisers working to ensure they get recommended by the latest models. The next form of SEO.

That's called LLM SEO now I believe.

Re: What Claude Code chooses

#45

Post by babaganoosh89 »

prinny_ wrote: post #37

Unrelated to the topic at hand but related to the technologies mentioned. I weep for Redux. It's an excellent tool, powerful, configurable, battle tested with excellent documentation and maintainer team. But the community never forgave it for its initial "boilerplate-y" iterations. Years passed, the library evolved and got more streamlined and people would still ask "redux or react context?" Now it seems this has car…

Redux should not be used for 1 person projects. If you need redux you'll know it because there will be complexity that is hard to handle. Personally I use a custom state management system that loosely resembles RecoilJS.

Re: What Claude Code chooses

#46

Post by ossa-ma »

Good report, very important thing to measure and I was thinking of doing it after Claude kept overriding my .md files to recommend tools I've never used before.

The vercel dominance is one I don't understand. It isn't reflected in vercel's share of the deployment market, nor is it one that is likely overwhelming prevalent in discourse or recommended online (possible training data). I'm going to guess it's the bias of most generated projects being JS/TS (particularly Next.js) and the model can't help but recommend the makers of Next.js in that case.

Re: What Claude Code chooses

#48

Post by [deleted] »

dataviz1000 wrote: post #39

I'm running a server on AWS with TimescaleDB on the disk because I don't need much. I figure I'll move it when the time comes. (edit: Claude Code is managing the AWS EC2 instance using AWS CLI.) Claude Code this morning was about to create an account with NeonDB and Fly.io (edit: it suggested as the plan to host on these where I would make the new accounts) although it has been very successful managing the AWS EC2 se…

[deleted]

Re: What Claude Code chooses

#49

Post by esafak »

wafflemaker wrote: post #25
glimshe wrote: post #13

Earlier quoted context omitted.

Claude Free suggests Visual Studio. Claude Plus suggests VSCode. Claude Pro suggests emacs.

I'm not quite sure if you're making fun of emacs or actually praising it.

Stallman paying for advertising, now that is good one :)

Re: What Claude Code chooses

#50

Post by dvt »

dataviz1000 wrote: post #39

I'm running a server on AWS with TimescaleDB on the disk because I don't need much. I figure I'll move it when the time comes. (edit: Claude Code is managing the AWS EC2 instance using AWS CLI.) Claude Code this morning was about to create an account with NeonDB and Fly.io (edit: it suggested as the plan to host on these where I would make the new accounts) although it has been very successful managing the AWS EC2 se…

> Claude Code likely is correct that I should start to use NeonDB and Fly.io which I have never used before and do not know much about

I wouldn't be so sure about that.

In my experience, agents consistently make awful architectural decisions. Both in code and beyond (even in contexts like: what should I cook for a dinner party?). They leak the most obvious "midwit senior engineer" decisions which I would strike down in an instant in an actual meeting, they over-engineer, they are overly-focused on versioning and legacy support (from APIs to DB schemas--even if you're working on a brand new project), and they are absolutely obsessed with levels of indirection on top of levels of indirection. The definition of code bloat.

Unless you're working on the most bottom-of-the-barrel problems (which to be fair, we all are, at least in part: like a dashboard React app, or some boring UI boilerplate, etc.), you still need to write your own code.

Post reply on HN