The Author of Clean Code No Longer Reviews AI-Generated Code
Robert Martin, author of Clean Code, shared his approach to overseeing AI-generated code. He avoids reading the code directly and instead relies on extensive constraints such as unit tests, Gherkin tests, QA procedures, and mutation testing. This strategy gives him high confidence in the output of his agents.
- ▪Martin began his programming career in the late 1960s and is known for his Clean Code principles.
- ▪He publicly stated that he does not read any code written by his AI agents.
- ▪He surrounds the agents with a suite of constraints, including unit tests, Gherkin tests, QA procedures, quality metrics, mutation testing, and test coverage.
- ▪Martin believes these constraints provide sufficient confidence in the agents' productivity without direct code review.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,493 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
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=49074693 |
| Publication time | Mon, 27 Jul 2026 19:47:06 +0000 |
| Retrieval time | 2026-07-27T19:53:58.939Z |
| Last seen | 2026-07-27T19:53:58.939Z |
| 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 | sZ1ptRg-Kz-4 · 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
Tweet URL: https://x.com/unclebobmartin/status/2080257779395154409?s=20Robert Martin, the author of Clean Code, tweeted the following:> I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.