AI Slop 与 Craft 危机
What it is
"Slop" refers to AI-generated output that is technically functional but generic, incoherent, or devoid of human judgment. The term captures a systemic risk: as AI lowers the cost of production to near zero, the volume of mediocre work rises, and the human taste required to distinguish good from bad becomes the scarce resource.
Why it matters
When anyone can generate a complete product in an afternoon, the barrier to creation drops, but the barrier to quality rises. Without deliberate craft — the final 10% where a human applies taste — AI output converges toward sameness. This affects software, design, writing, and any creative field where AI is deployed as a production tool.
Key points
- Software lost its soul before AI arrived. Ryo Lu (Cursor Design Lead) traces the erosion of software personality to the rise of growth metrics and A/B testing, which standardized design systems and flattened product character. AI accelerates this trend but did not start it.
- "Overcooking" is a new form of design debt. When the cost of adding features drops to near zero, individually sensible decisions accumulate into collective incoherence. A dashboard with sparklines on every number, confirmation modals on every action, and animated illustrations on every empty state is not wrong in any single choice, but wrong as a whole. Attention is finite; overload dissipates focus.
- Most "new ideas" are repackaged old concepts. Ryo Lu argues that many AI-generated features are new stickers on old concepts. The thinking does not go deeper; it duplicates itself into confusion. The solution is not more tools that make more slop, but the discipline to see through chaos and cut everything that does not serve the core purpose.
- Craft lives in the last 10%. Peter Yang (Product, Roblox) notes that AI is useful for generation, but craft is in the manual application of taste to make something you can be proud of. Many people never bother with this step. This echoes Kieran Klaassen's "polish" phase in Compound Engineering: the human judgment that elevates output from functional to exceptional.
- The risk is drowning, not displacement. Ryo Lu's core fear is not that AI will replace quality practitioners, but that it will flood the market with mediocrity, making it harder for crafted work to surface.
- Slop as experimental fuel. Mitchellh argues that slop is what enables fast parallel experimentation. The etiquette is not to avoid slop, but to understand when you are in "exploration mode" (where slop is valuable) versus "delivery mode" (where craft matters). This reframes slop from a problem to a phase.
Evidence across sources
| Source | Key Claim | Relevance |
|---|---|---|
| AI 简报 2026-03-31 | Software personality eroded by metrics and A/B testing before AI | Pre-AI root cause of homogenization |
| AI 简报 2026-04-01 | AI risks drowning quality practitioners in mediocrity | Framing the "drowning" risk |
| AI Builders Digest 2026-04-23 | "Overcooking": individually sensible decisions accumulate into incoherence; craft is the last 10% | Mechanism (overcooking) and solution (craft) |
| AI & I Podcast — The AI Sandwich | Without human polish, AI output becomes "all slop, all the same" | Independent validation from engineering practice |
| AI Briefing 2026-05-08 evening | Mitchellh: slop enables fast parallel experimentation; the skill is knowing which phase you are in | Counter-narrative: slop as a productive phase, not just a problem |
| AI Briefing 2026-05-09 morning | Mitchellh's concrete examples: internal API/GUI built entirely with slop; overnight agent-generated dozens of plugins; compares to Terraform 0.1's 3 weak providers vs today's 100 slop-generated providers | Demonstrates slop as velocity multiplier with clear guardrails (no unreviewed PRs, no customer delivery without transparency) |
| Nabeel Qureshi — What Makes Art Great? | AI slop is easy to compress (low information content); great art is hard to compress. AI picks "obvious" word choices. True craft requires Surprise, Echoes, and Depth | Formal framework for diagnosing why AI output feels dull; bridges aesthetics and engineering judgment |
Open questions
- Can "taste" be systematized or taught, or is it inherently intuitive and experiential?
- Will platform-level curation (app stores, search rankings) adapt to filter slop, or will the flood overwhelm existing quality signals?
- If AI eventually learns to mimic individual taste profiles, does craft become a training-data problem rather than a human-judgment problem?
Prompts for witness
- What is the "overcooking" pattern in your own work or products? Where have you added features that made sense in isolation but weakened the whole?
- What is the last 10% of craft in your current project that you have been skipping because AI made the first 90% so easy?
- If you had to define a single "taste standard" for your team's AI-generated output, what would it be and how would you enforce it?
Related
- harness-engineering/compound-engineering — The "polish" step as an engineering methodology
- product-trends/ai-founder-guide-to-taste — Taste as a strategic asset in creative industries
- product-trends/living-software-framework — Expectation models for software that evolves vs. static tools
- product-trends/design-is-understanding-not-output — Design quality as a function of problem understanding