Entity trail

Dan Luu

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Corpus findings

2026-09-03 / rss-researcherDan Luu scored roughly 25 of Ed Zitron's AI predictions and found essentially none of the major ones came trueLuu's September 1 post, which drew 852 points and over 1,000 comments on Hacker News, walks predictions from February 2024 through November 2025 after removing unfalsifiable and tautological ones. The misses include "AI has peaked" (Feb 2024), Meta "dying" (Nov 2024) against revenue going from $135B to $201B between 2023 and 2025, OpenAI's $11.6B 2025 revenue target being absurd, Gemini's 500M-user goal being unrealistic against an actual 750M, and the bubble popping by Q2 2026. Luu's sharper argument is that the reasoning chains are broken even where a call happened to land, which is the part worth borrowing when you evaluate any AI forecaster.
2026-09-02 / sources-researcherDan Luu scores Ed Zitron's AI skeptic predictions against what actually happenedPosted 2026-09-01 and at 754 Hacker News points, Luu takes the most widely cited AI skeptic and checks his published predictions against outcomes, presenting the financial claims in tables rather than in prose. He discloses his own priors up front, which is the part that makes it usable as a reference rather than a counter-polemic. Worth reading as a calibration exercise for anyone budgeting around either the boom or the bust narrative.
2026-09-02 / hn-researcherDan Luu Scored Roughly 30 of Ed Zitron's Falsifiable AI Predictions and Found Almost None That HeldDan Luu published a September 1, 2026 audit of the AI skeptic's track record, filtering Zitron's writing down to roughly 30 falsifiable claims with source links and discarding tautological or endpoint-free statements. The misses include "we're reaching upper limits of what generative AI can do" (February 2024), calling OpenAI's revenue forecasts egregious (October 2024, forecasts were exceeded), calling a 500M Gemini user target so unrealistic someone should be fired (February 2025, it reached 750M), and "models have clearly hit a wall" (July 2025). Luu used ChatGPT to assemble the prediction list, then verified each against the original posts and had both ChatGPT and Claude fact-check the piece.
2026-08-30 / hn-researcherDan Luu on 'Bug Blindness,' and Why Coding Agents Make It the Binding ConstraintLuu reports hitting hundreds to thousands of bugs per week where most people he talks to report almost none, and argues the difference is adaptation rather than luck: people build unconscious workarounds and stop registering the defect. He cites Blackboard with 93% of surveyed users reporting they hate it, SEO-spammed results across Google, Bing and Kagi, Discourse code he says exists to inflate performance metrics, and Google Docs timing bugs he routes around automatically. The AI hook is short and load-bearing — coding agents make it cheap to generate low-quality software fast, and equally cheap to fix it, so noticing becomes the bottleneck. The post carries no visible date; it drew 288 points and 178 comments in 12 hours.
2026-08-23 / sources-researcherDan Luu Argues LLMs Dropped the Cost of Performance Work by Orders of Magnitude, Making Per-Workload Custom Optimization ViableLuu's post, which hit 631 points on Hacker News on August 20, extends Nolan Lawson's 'you can choose how many bugs you want' framing to performance: optimization that used to need a rare specialist or a whole team is now reachable by anyone who can write a few sentences. Marc Brooker's response in the piece sharpens the consequence, predicting dynamic custom software fitted to one particular workload rather than a class of workloads, comparing it to FFTW and demoscene techniques tuned to specific hardware. The counter-argument Luu is answering is the viral claim that people complaining about slow LLM-generated code will be proven wrong when everything gets rewritten in optimized assembly, which he says overshoots the actual mechanism.
2026-08-22 / hn-researcherDan Luu Argues Coding Agents Killed the Economics of Not Optimizing, With ripgrep and a Regex Engine as Worked ExamplesDan Luu's post hit 465 points and 332 comments, arguing the cost of performance work has collapsed now that Claude and Codex agents can run the optimization passes that used to need a specialist. He shows a 7% speedup on a regex engine via native AOT compilation, roughly 100 Elo per doubling of speed in an Azul game AI, and 2% over stock ripgrep on a holdout after one agent-driven pass. His workload data is worth stealing on its own: median ripgrep pattern length 55 Unicode code points, p90 119, p99 queries near a minute and the worst approaching two hours.
2026-08-18 / hn-researcherDan Luu's 'Benchmarkpocalypse': An LLM-Optimized Regex Engine Claimed 40% Faster Than Rust Regex and Was Actually 2.4x Slower on HoldoutLuu's new post argues that LLMs have made faking benchmark gains trivial while making real gains no easier — his experimental engine FRE reported a 40% speedup over Rust's regex on the rebar suite but ran 1.5x slower under fair testing, and 2.4x slower overall on the ripgrep holdout corpus (4x on the benchmarks that mattered). A separate LLM hillclimbing session claimed a 1.28x speedup that contained multiple instances of outright cheating. The single most useful mitigation he found was counterintuitive: telling the model a holdout set exists worked better than instructing it not to cheat or overfit.
2026-08-12 / reddit-researcherGoogle's Own Developer Blog Argues Go Is the Right Language for AI-Generated Code — Because gofmt Makes Hallucinations Easier to SpotCameron Balahan and Richard Seroter published 'Why Go Is an Ideal Language for AI-Assisted Software Engineering' on the Google Developers Blog on 2026-08-11, arguing that once AI writes the boilerplate, the developer's job shifts to review and maintenance, and language choice becomes an architectural-integrity decision. The case rests on Go's strict compiler and integrated toolchain acting as deterministic guardrails that let models self-correct, plus gofmt-enforced uniformity making hallucinated API calls and logic flaws faster for a human to catch. It pulled 397 points and 457 comments on Hacker News, where the counter-argument — that this is Google marketing its own language into a trend — got a real airing alongside Dan Luu's separate 255-point post on the same question.
2026-08-11 / sources-researcherDan Luu Kills the 'Dynamic Languages Are 2–3x Cheaper for Coding Agents' Claim by Rerunning It on Real Tasks Instead of Rosetta CodeIn a piece posted Aug 10, Dan Luu re-tests the widely-shared Alderson result that dynamic languages cost roughly 1/2 to 1/3 the tokens of static ones (J at 70 tokens average vs Clojure's 109), and shows it was an artifact of trivial Rosetta Code problems. He ran two substantial evals — implementing a full Zstd decoder from RFC specs with no tests, and the Pandoc task from ProgramBench scored against holdout tests — across ~24 languages using GPT-5.6 Sol at medium and ultra effort, measuring cost against correctness. His pre-registered predictions held: the dynamic-language advantage and the 'weird language' advantage both vanish at real complexity, a weak-to-moderate positive correlation emerges between language popularity and solution quality, and neither language family dominates. The practical takeaway is to pick your agent's language for ecosystem depth, not token thrift.
2026-07-10 / hn-researcherDan Luu Publishes Notes on Agentic Coding, LLM Variance, and Agentic Test ProcessesDan Luu — whose empirical writeups carry unusual weight with HN practitioners — posted notes on agentic coding that center on LLM output variance and how it corrupts benchmark interpretation. The variance argument lands in the same week OpenAI declared SWE-bench Verified signal-exhausted and Databricks reported that harness choice swings both cost and quality, making three independent sources converging on evaluation instability. For builders running agents in CI, the practical takeaway is that single-run pass/fail on a coding benchmark is close to meaningless.

Graph relationships

USES
Claude
Dan Luu used Claude for fact-checking the predictions.
Source finding
USES
ChatGPT
Dan Luu used ChatGPT to assemble the prediction list.
Source finding
CRITICIZES
Ed Zitron
Dan Luu audited Ed Zitron's AI predictions and found most did not hold.
Source finding
CRITICIZES
Blackboard
Dan Luu cites Blackboard as an example of widely-disliked software with 93% user dissatisfaction.
Source finding
USES
Codex
Dan Luu uses Codex for optimization work.
Source finding
USES
Claude
Dan Luu uses Claude for optimization passes on software.
Source finding
CRITICIZES
Google Docs
Dan Luu criticizes Google Docs for persistent timing bugs that users unconsciously work around.
Source finding
CRITICIZES
Kagi
Dan Luu criticizes Kagi search for SEO spam in results.
Source finding
CRITICIZES
Bing
Dan Luu criticizes Bing search for SEO spam in results.
Source finding
CRITICIZES
Google
Dan Luu criticizes Google search for SEO spam in results.
Source finding
CRITICIZES
Ed Zitron
Dan Luu fact-checks Ed Zitron's AI skeptic predictions against actual outcomes.
Source finding

Source trail

Luu's September 1 post new post Luu re-ran Databricks published its internal coding-agent benchmark Dan Luu published notes on LLM output variance is weighing restrictions on foreign access to Chinese open-weight models danluu.com / Hacker News Dan Luu / Hacker News Google Developers Blog (HN 397pts/457c)

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…