HackerTrans
TopNewTrendsCommentsPastAskShowJobs

edwin

no profile record

Submissions

The Security Decisions Claude Code and Codex Make

amplifying.ai
2 points·by edwin·3 maanden geleden·1 comments

Claude Code's Leak: Every Hardcoded Vendor and Tool

amplifying.ai
8 points·by edwin·3 maanden geleden·0 comments

What tech stack Claude Code defaults to when building apps

amplifying.ai
6 points·by edwin·5 maanden geleden·1 comments

Use your leftover CC/Codex tokens overnight for maintenance PRs

github.com
1 points·by edwin·5 maanden geleden·0 comments

comments

edwin
·3 maanden geleden·discuss
There’s something quietly impressive about getting modern AI ideas to run on old hardware (like OP's project or running LLM inference on Windows 3.1 machines). It’s easy to think all the progress is just bigger GPUs and more compute, but moments like that remind you how much of it is just more clever math and algorithms squeezing signal out of limited resources. Feels closer to the spirit of early computing than the current “throw hardware at it” narrative.
edwin
·5 maanden geleden·discuss
I’m one of the authors.

Our interest is straightforward: If coding agents scaffold a growing share of new apps, their defaults will become prevalent. Not necessarily because they’re objectively best, but because the choices are frictionless. The model becomes the gatekeeper of early architectural decisions that used to happen in a meeting room.

So we measured what those defaults actually are.

We ran structured app-building prompts through Claude Code, captured the generated repos, and extracted stack choices: auth, UI framework, database, deployment assumptions, package management, etc.

A few observations that stood out: - Deployment assumptions are shifting toward Vercel and Railway, and away from AWS/GCP-first patterns. - Defaults evolve as models update. For example, Opus 4.6 recommends Drizzle more frequently than Prisma.

Prompts, raw outputs, and parsing logic are here: https://github.com/amplifying-ai/claude-code-picks

This is a snapshot in time. An interesting question is how quickly these defaults drift.
edwin
·vorig jaar·discuss
Unlike classic search, which got worse over time due to SEO gamings, AI search might actually improve with scale. If LLMs are trained on real internet discussions (Reddit, forums, reviews), and your product consistently gets called out as bad, the model will eventually reflect that. The pressure shifts from optimizing content to improving the product itself.
edwin
·vorig jaar·discuss
We looked at the same data that Rand Fishkin used and definitely came to a different conclusion.
edwin
·vorig jaar·discuss
A few take-aways from a study we ran (~800 consumer queries, repeated over a few days):

* AI answers shift a lot. In classic search a page-1 spot can linger for weeks; in our runs, the AI result set often changed overnight.

* Google’s new “AI Mode” and ChatGPT gave the same top recommendation only ~47 % of the time on identical queries.

* ChatGPT isn’t even consistent with itself. Results differ sharply depending on whether it falls back to live retrieval or sticks to its training data.

* When it does retrieve, ChatGPT leans heavily on publications it has relationships with (NYPost and People.com for product recs) instead of sites like rtings.com

Writeup: https://amplifying.ai/blog/why-ai-product-recommendations-ke...

Data: https://amplifying.ai/research/consumer-products