Pundit ClaimsAI claims by Gary Marcus and Ed Zitron, with the evidence

“AI-authored code — especially vibe-coded programs — is inherently dangerous and disrespectful to the user, and I believe endless AI-generated code is behind the overall deterioration of software at large.”

The AI Hater's Manifesto, paragraph 47. The full statement is at the source.

Our reading, the sentence that was checked:

AI-authored code, especially vibe-coded programs, is inherently dangerous and disrespectful to the user, and Zitron believes endless AI-generated code is behind the overall deterioration of software at large.

Assessment: Unresolved Evidence as of

Where and when Ed Zitron wrote it

Where's Your Ed At, The AI Hater's Manifesto, paragraph 47.

Said
Source observed
live page, full text, public
Evidence as of
the cutoff for this assessment
Assessment recorded
assessment wyea-the-ai-haters-manifesto-5f6d31-a1

We recorded 49 claims from this post. See every claim from this post.

The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-08-25. This page does not claim the wording was captured then.

What the claim commits to

Kind
Causal claim
Deadline, as the speaker wrote it
None stated. This site does not add one.
Deadline state when assessed
No horizon
Deadline state on 2026-10-29
No horizon (the release’s reference date)

Conditions

  • especially vibe-coded programs (scope, stated by the speaker)
  • I believe (qualifier, stated by the speaker)

From the speaker

  • AI-authored code
  • especially vibe-coded programs
  • inherently dangerous
  • disrespectful to the user
  • I believe
  • behind the overall deterioration of software at large

Our interpretation

  • Disrespectful is a value judgment and is not scored as an empirical finding.
  • The assessable causal assertion is that substantially AI-authored software creates security or reliability hazards and materially contributes to a broad decline in software quality.
  • The surrounding passage permits small scripts and emphasizes surrendering understanding and responsibility. It should not be read as condemning every AI-assisted line of code.
  • I believe expresses uncertainty about the causal explanation; it is not a conditional antecedent.
  • No beginning or baseline for the alleged deterioration is supplied. The assessment concerns deterioration already occurring by the post date.

Counts as supported if: Representative evidence establishes an underlying decline in software quality and isolates a material contribution from AI-authored code, with evidence that the asserted danger persists in the relevant development conditions.

Counts as contradicted if: Representative causal evidence rules out a material contribution to the alleged decline, or demonstrates that the asserted inherent danger does not hold under the relevant conditions. A limited favorable study cannot settle software at large.

Retrospective: these criteria were written after the outcome was public.

Current assessment

Does the evidence support the cause?

Outcome: Unresolved

The record was checked, and the evidence available by the cutoff does not settle it.

Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.

Evidence as of
Deadline state when assessed
No horizon
Assessment recorded
Policy version
2026-10-28.7

Rationale

There is concrete evidence that generated code can contain security and quality defects and needs verification. A controlled maintainability study, however, found no significant downstream penalty in its setting. Neither result establishes whether AI-authored code is causing an overall deterioration of software. The disrespect judgment is normative and is excluded from the factual score.

Limitations

  • Benchmark flaws do not establish industry-wide causation.
  • A null result in one controlled task does not prove universal safety.
  • The evidence does not consistently distinguish assisted coding from unchecked vibe coding.

Evidence (2 items)

  • Context only: Sabra, Schmitt and Tyler via arXiv,

    requires verification

    Why it matters here: Static analysis of generated Java assignments found defects and security vulnerabilities, supporting concern about unchecked generated code. It does not establish unavoidable danger or a causal decline in software overall.

    Publisher
    Sabra, Schmitt and Tyler via arXiv
    Kind of source
    Preprint, not peer reviewed
    Describes events of
    Public from
  • Context only: Empirical Software Engineering, Springer Nature,

    no significant differences

    Why it matters here: The controlled study found no measurable downstream maintainability penalty for its AI-assisted development tasks. That limits blanket deterioration claims, but the study does not test autonomous vibe coding or the entire software industry.

    Publisher
    Empirical Software Engineering, Springer Nature
    Kind of source
    Peer-reviewed paper
    Describes events of
    Public from

What would settle it

Representative longitudinal production evidence linking measured AI authorship and review practices to changes in defects, security, and reliability, with credible controls for other causes.

Where it was said (1)

Said once in the sources this register covers.

  • : Where's Your Ed At, The AI Hater's Manifesto

    AI-authored code — especially vibe-coded programs — is inherently dangerous and disrespectful to the user, and I believe endless AI-generated code is behind the overall deterioration of software at large.

    Published
    2026-08-25
    Source observed
    , live page
    Access
    full text, public

History

Assessment versions

Recorded events

  1. Assessment publishedBy this site

    First assessment published after both reviews and the final-text check passed.

    About assessment wyea-the-ai-haters-manifesto-5f6d31-a1.