The LLM Critics Are Right. I Use LLMs Anyway.
- Validity of Common Critiques:
- Acknowledges that major LLM criticisms—such as generating "slop," relying on copyrighted training data, high environmental costs, and circular financial hype—are fundamentally valid.
- Warns against trusting LLM outputs blindly, noting that models produce fluent, confident-sounding content that often defaults to generic consensus rather than optimal or creative solutions.
- LLMs as Thought Amplifiers:
- Posits that LLMs function as force multipliers for existing human ideas: "If you have thoughts, they come out sharper and faster. If you have nothing, nothing comes out, very fluently."
- Emphasizes that LLMs should never write primary artifacts from scratch, but rather be used to refine, stress-test, and critique human-authored drafts.
- Effective Usage & Avoidance of Traps:
- Advocates for a human-first workflow: humans create initial drafts/structure, while the LLM is restricted to finding contradictions, blind spots, or sharpening specific phrasing.
- Highlights key failure modes, such as asking models for opinions where strong consensus exists (leading to bland defaults) or attempting to use AI for unverified original research.
Hacker News Discussion
- Inverted Workflow (AI as Reviewer, Human as Creator):
- Commenters strongly support using LLMs as tireless reviewers rather than initial content generators, pointing out that humans enjoy creating but dislike reviewing, whereas LLMs excel at patient, meticulous critique.
- Reversing the dynamic—letting humans write and AI review—prevents low-quality content generation while retaining human intent and voice.
- Prompting Strategies to Avoid Flattery:
- Users note that due to RLHF training, LLMs default to flattering the user's ideas; removing self-identification from prompts (e.g., framing your work as a third party's) results in more objective, critical feedback.
- Geopolitical & Vendor Risks:
- Discussions raise concerns regarding dependence on proprietary APIs subject to export controls or sudden access cuts (e.g., US regulations affecting non-US Anthropic access), highlighting the importance of self-hosted, open-weight fallbacks.
- Resistance to Open Source AI Contributions:
- Highlighted growing pushback across major open-source projects (e.g., Zig, Gentoo, Pi.dev) against AI-generated pull requests, which maintainers view as low-effort noise that shifts the burden of review onto humans.