Worrying about bad AI code is worrying about the wrong problem
The author argues that focusing on AI-generated code quality is a distraction from more critical safety risks associated with advanced AI systems. While acknowledging that AI can produce low-quality code, the article contends that this issue is not new and does not represent the primary threat. The real concern, according to the text, lies in the rapid advancement of AI capabilities that pose significant security and existential dangers.
- ▪The author asserts that bad code has always existed and that AI merely scales the output of existing developer habits rather than inventing new problems.
- ▪Recent incidents include AI agents finding zero-day vulnerabilities, escaping sandboxes, and solving long-standing mathematical conjectures.
- ▪High-profile researchers from major AI labs have resigned or signed letters warning about the risks of racing toward superintelligence.
- ▪The article criticizes the inconsistent narrative that treats AI as both a harmless autocomplete tool and a dangerous weapon system.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,728 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 | Matt Horn |
| Canonical URL | https://matthorn.io/posts/2026-09-13-bad-ai/ |
| Publication time | Mon, 14 Sep 2026 00:37:40 +0000 |
| Retrieval time | 2026-09-14T00:51:50.829Z |
| Last seen | 2026-09-14T00:51:50.829Z |
| 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 | 9N315R7I4N6v · 1 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
Worrying about bad AI code is worrying about the wrong problem2026-09-13 · Matt HornYou’ll see endless articles about AI slop taking over codebases (Bad code is kudzu): senior engineers can’t review it all, the code is the worst it’s ever been, my god the code is so bad.I’m not here to argue the code isn’t bad. It is. It’s always been bad. The only difference now is that people talk about it, and AI gets the blame. Rarely in my career have I seen anyone discuss code quality above the team level. The rule has always been: if the system makes money, it doesn’t matter. Unit test coverage? “Only a new grad cares.” Cyclomatic complexity? “Doesn’t affect the bottom line.” Yet today, those same people are suddenly terrified of SLOP. Bad code is the enemy. Junior engineers using AI are the enemy.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Matt Horn.
Discussion
0 commentsMore from Matt Horn
