Live data from Hacker News

What Claude Code chooses

amplifying.ai

221–230 of 266 posts

Re: What Claude Code chooses

#221

I've been worried for some time now that genAI will effectively kill the market for dev tools and so we will be stuck with our current dev tools for a long time. If everyone is using LLMs to write code, the only dev tools anyone will use will be the ones that the LLMs use. We will be stuck with NPM forever.

I think the opposite may be true. If dev tools are broken and it annoys someone, they can more easily build a better architecture, find optimizations and release something that is in all ways better. People have been annoyed with pip forever, but it was the team behind uv that took on pip's flaws as a primary concern and made a better product.

I think having a pain point and a good concept (plus some eng chops) will result in many more dev tools - that may be cause different problems, but in general, I think more action is better than less.

Re: What Claude Code chooses

#222
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…

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 request they go. Advertising comes down to a binary choice - use product X or not. If I want implementation instructions for a certain product on specific hardware an ad will be obviously out of place and irrelevant.

So "shopping comparison" asks might get broken, but those have been broken for a while.

Re: What Claude Code chooses

#223
post #154

Supreme irony: this website itself is a better exercise in showing what Claude Code uses than the data provided. Everything current Claude Code i.e. Opus 4.6 chooses by default for web is exactly what this linked blog uses. Jetbrains Mono is as strong of a tell for web as "Not just A, but B" for text. >99% of webpages created in the last month with Jetbrains Mono will be Opus. Another tell is the overuse of this font…

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 until it's as parched as the Sahara". In that sense, Prisma is the exact thing you'd expect to happen with a VC-funded DB package. ZIRP really made them invest into the craziest things.

I like Kysely more than Drizzle, even moreso now with Claude, but Drizzle is fine too. As long as it's not Prisma, and preferably not TypeORM or Sequelize either.

Re: What Claude Code chooses

#224
This matches what I observed running AI agents overnight for content generation. The temptation is always to add cost controls inside the application — but that logic doesn't survive when the agent goes off-script.

The fear of a 3am runaway was real enough that I ended up building a separate gateway layer just to have a kill switch that lives outside the application entirely.

"Build vs Buy" is the right framing, but for cost enforcement and kill switches specifically — building it inside the app is exactly the wrong layer.

Re: What Claude Code chooses

#225

Ist why I never give it such vague prompts. But it's sad it does not ask the user more. Also interesting and important to know how one would tease out good and correct information from llms in 2026. It's like relearning now to Google like it was 2006 all over again, except now it's much less deterministic. I wonder how the tail of the distribution of types of requests fares e.g. engineer asking for hypothesis generat…

creating plans in claude and asking chatgpt via api to review loop was my strategy this week. I'm not a big fan of codex as a coding harness because it seems to just give up quite easily where claude will search the problem space and try things but I think gpt does a much better job of poking holes and asking clarifying questions when prompted.

Re: What Claude Code chooses

#226
post #220

I've been worried for some time now that genAI will effectively kill the market for dev tools and so we will be stuck with our current dev tools for a long time. If everyone is using LLMs to write code, the only dev tools anyone will use will be the ones that the LLMs use. We will be stuck with NPM forever.

What kind of tools do you have on your mind specifically? My experience is that LLM can create me a decent dev tool that I wouldn't ever bother making so nice myself.

IDEs, graphical debuggers, etc.

It's extremely weird that 40 years after TurboPascal, 30 years after Delphi and VBA, we've only regressed in terms of truly integrated development environments.

Heck, even programming languages have regressed. Python and Javascript are less type safe than Java circa 2005. Even though we have technology needed to make type safe languages much more ergonomic, since then.

Re: What Claude Code chooses

#227
post #61
post #50

Earlier quoted context omitted.

> 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…

How do you make an LLM that’s was trained on average Internet code not end up as a midwit? Mediocrity in, mediocrity out.

reinforcement learning is all code that was created by coding gig workers through scale ai and similar. I cannot believe it would be very good.

Re: What Claude Code chooses

#228
post #23
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.

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.

Advertisers pay for ads that don’t have impression data all the time. You can’t count how many people looked at a billboard or listened to your radio ad or paid attention to your televised ad.
Post reply on HN