“This is, by the way, why we are still yet to get any tangible proof that AI is replacing software engineers…because it can’t.”
Our reading, the sentence that was checked:
There is still no tangible proof that AI is replacing software engineers because AI can't replace them.
Assessment: Unresolved Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, The Case Against Generative AI, paragraph 255.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-the-case-against-generative-ai-9d461c-a1
We recorded 46 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 2025-09-29. 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)
From the speaker
- still yet to get any tangible proof
- AI is replacing software engineers
- because it can’t
Our interpretation
- Assess the public evidence and capabilities existing by September 29, 2025, rather than treating the sentence as an unlimited forecast.
- In context, replacement means taking over an engineer's substantive responsibilities sufficiently to replace a position. Generating some code does not establish this.
- Reduced hiring through human productivity gains is relevant counterevidence, but differs from independently performing the full role.
Counts as supported if: Evidence must establish both the absence of documented replacement and that a demonstrated capability limitation explains that absence. Failed searches or isolated benchmark failures alone are insufficient.
Counts as contradicted if: A documented deployment must show AI taking over substantive engineering responsibilities and replacing positions by the post date, or directly disprove the claimed causal explanation.
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
Salesforce publicly connected AI productivity gains to reduced hiring plans. That is relevant evidence of labor substitution, but does not show AI independently replacing an engineer's responsibilities. SWE-Lancer documents capability limits, not their effect on employment. Neither source settles the combined absence-of-proof and causal claim.
Limitations
- The result depends on distinguishing full-role replacement from partial automation and avoided hiring.
- Employer productivity statements are self-reported.
- Later deployments cannot establish that replacement had already occurred when the post appeared.
Evidence (2 items)
Context only: Salesforce; transcript by S&P Global Market Intelligence,
productivity increase on engineering.
Why it matters here: The company linked greater engineering productivity to a hiring freeze. This challenges a broad assertion that AI cannot substitute for engineering labor, but does not document autonomous replacement of existing engineers.
- Publisher
- Salesforce; transcript by S&P Global Market Intelligence
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
Context only: Miserendino et al., arXiv,
unable to solve the majority
Why it matters here: SWE-Lancer documents substantial limitations on real freelance engineering tasks. It neither measures employment replacement nor establishes that technical incapacity caused an absence of replacement.
- Where
- Abstract
- Publisher
- Miserendino et al., arXiv
- Kind of source
- Preprint, not peer reviewed
- Describes events of
- Public from
What would settle it
Dated deployment and staffing records showing whether AI took over engineering responsibilities before September 29, 2025, together with evidence identifying why replacement did or did not occur.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, The Case Against Generative AI
This is, by the way, why we are still yet to get any tangible proof that AI is replacing software engineers…because it can’t.
- Where
- paragraph 255
- Published
- 2025-09-29
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-the-case-against-generative-ai-9d461c-a1: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment wyea-the-case-against-generative-ai-9d461c-a1.