Amdahl's Law for LLM generated code
Amdahl's Law highlights the limitations of using large language models (LLMs) for generating code. While LLMs can produce vast amounts of code, ensuring its correctness requires thorough human auditing, which is often more complex than writing the code itself. This suggests that the potential efficiency gains from LLMs are fundamentally constrained when it comes to critical coding tasks.
- ▪LLMs can generate millions of lines of code, but correctness is not guaranteed.
- ▪Hand-auditing every line of code is necessary for important projects.
- ▪The speedup from LLMs is limited when writing code that requires careful consideration.
2 outlets in our directory ran this story, first to last over 32 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Security of LLM-generated Code: A Comparative Analysis — arXiv cs.AI
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48278179 |
| Publication time | Tue, 26 May 2026 11:21:24 +0000 |
| Retrieval time | 2026-05-26T11:37:48.652Z |
| Last seen | 2026-05-26T11:37:51.947Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | I7BHsEeqmm3J · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
LLMs may theoretically be able to generate millions of correct lines of code.But for any important code the only way to know that it's correct is to hand-audit every line, which is harder than writing every line because this allows you to build a conceptual hierarchy and model within which you can think about the code.So there's a fundamental limit to the speedup from LLMs when writing anything you care about.(The main objection will be what about when you have a human engineer working on your behalf. But this is a distraction: sometimes you can fully trust an engineer, which is not at all true for LLMs.)
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.