Can you tell AI from human-authored code and should you even care?
Article · AI code v human code · August 2026 Can you tell AI code from human code — and does it matter? It started with a mailer script and a habit I couldn't unsee: the AI never edits a line of code. Six months of measurement later, I think most AI-code detection is answering the wrong question.
- ▪Article · AI code v human code · August 2026 Can you tell AI code from human code — and does it matter?
- ▪It started with a mailer script and a habit I couldn't unsee: the AI never edits a line of code.
- ▪Six months of measurement later, I think most AI-code detection is answering the wrong question.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,776 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 | Codedelta |
| Canonical URL | https://codedelta.app/article-ai-vs-human.html |
| Publication time | Wed, 05 Aug 2026 19:30:19 +0000 |
| Retrieval time | 2026-08-05T19:35:47.247Z |
| Last seen | 2026-08-05T19:35:47.247Z |
| 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 | LnRbCFpOuikg · 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
Article · AI code v human code · August 2026 Can you tell AI code from human code — and does it matter? It started with a mailer script and a habit I couldn't unsee: the AI never edits a line of code. It deletes the block and writes a new one. Six months of measurement later, I think most AI-code detection is answering the wrong question. 5 August 2026 · the measurements behind this are in two papers: REP_CHURN and a survey of detection methods The habit I couldn't unsee Earlier this year I was building a website and an automated mailer system with AI assistance. Nothing exotic — forms, a bit of PHP, the usual. Somewhere in the second week I noticed something about the way the assistant worked: it never, not once, edited a line of code in place.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Codedelta.
Discussion
0 commentsMore from Codedelta
