“You cannot just “replace a coder,” because “coder” isn’t really the job”
Our reading:
You cannot just replace a coder because coding isn't really the job, and while this might affect entry-level software engineers at some point, there is yet to be proof it is happening or that AI rather than, say, outsourcing is taking these jobs.
Assessment: Unresolved
What happened
Was it true for the period described?
Outcome: Unresolved
We checked, and the evidence so far doesn’t settle it.
Judged on a plain reading. They named no measure, so we used the reading a typical informed reader would take. It is spelled out under “How we judged it”.
Evidence up to . Checked .
Why
On February 26, 2025, Salesforce's CEO linked a plan to hire no new engineers that year to reported coding-tool productivity gains [e1]. This was a company statement, without an entry-level breakdown or independent verification of substitution [e1]. A research account published February 5, 2024 reported a 20% decline in freelance coding postings [e3]. The May 2025 Danish study found no significant earnings or recorded-hours effects across 11 exposed occupations, using outcomes through June 2024 [e2]. These findings do not establish complete engineering-role replacement or attribute entry-level engineering displacement to AI while addressing alternative causes [e1, e2, e3]. They also cannot establish that no qualifying public evidence existed by June 16, 2025, leaving the claim unresolved [e1, e2, e3].
Caveats
- The packet does not comprehensively establish what evidence was publicly available by June 16, 2025.
- The evidence does not directly test whether coding automation can replace a complete engineering role [e1, e2, e3].
- Hiring plans and freelance postings do not establish realized entry-level engineering job losses [e1, e3].
- The Danish results cover outcomes through June 2024 and do not establish effects elsewhere or specifically among entry-level engineers [e2].
Evidence (3 items)
Context only: Salesforce; transcript by S&P Global Market Intelligence,
new engineers
Why it matters: Benioff connects this hiring plan to reported gains from coding tools in the surrounding passage. It is material evidence of intended labor-demand substitution, but not verification of entry-level job losses or replacement of complete engineering roles.
- Publisher
- Salesforce; transcript by S&P Global Market Intelligence
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- About events on
- Published
Context only: National Bureau of Economic Research,
economic impacts
Why it matters: The original Danish study reports small measured labor-market effects using administrative outcomes through June 2024, but cannot establish absence of displacement elsewhere or specifically among junior engineers. The source gives May 2025 only; available_at conservatively uses month-end.
- Where
- Abstract
- Publisher
- National Bureau of Economic Research
- Kind of source
- Preprint, not peer reviewed
- About events on
- Published
Context only: Imperial College Business School; Xinrong Zhu,
coding fell
Why it matters: The researcher reports declining freelance coding demand and comparisons between occupations with different AI exposure. This is substantive counterevidence to a broad denial of labor-demand effects, but the study does not identify entry-level engineering employees or demonstrate complete role replacement.
- Publisher
- Imperial College Business School; Xinrong Zhu
- Kind of source
- Independent measurement
- About events on
- Published
How we judged it
- Kind of claim
- Observation
- Deadline
- None given. We don’t add one.
Conditions
- this might affect entry-level software engineers at some point (their words)
- there's yet to be proof (their words)
Where we had to interpret
- This concerns the public evidence available by publication, rather than a prediction that displacement can never occur.
- Cannot just replace a coder is read as a claim about replacing an engineering role through coding automation alone, not a literal denial that coding occupations exist.
- Proof means credible evidence connecting lost engineering work or positions to AI while addressing plausible alternative causes.
- The target is the accumulated public record through June 16, 2025. Its start is unspecified because yet imposes a cutoff rather than a particular reporting year.
- The possibility of future effects is a qualification, not a conditional forecast to score separately.
Right if: A sufficiently comprehensive contemporaneous record supports the distinction between code generation and full engineering-role replacement, and establishes that claimed entry-level displacement had not been credibly attributed to AI rather than alternative causes.
Wrong if: Evidence public by the post verifies replacement of complete engineering roles by AI, or credibly attributes entry-level engineering job losses or reduced hiring to AI while addressing relevant alternatives.
We wrote this test after the outcome was known.
What would settle it
Evidence public by June 16, 2025 that verifies complete engineering-role replacement, or credibly attributes entry-level engineering job losses or reduced hiring to AI while addressing outsourcing and other plausible causes, would contradict the claim. Support would require a sufficiently comprehensive contemporaneous record establishing both the distinction between coding automation and full-role replacement and the absence of credible attribution of entry-level displacement to AI.
We found 24 claims in this post. See them all.
Full record
Source and dates
Where's Your Ed At, Sincerity Wins The War, paragraph 79.
- Said
- We read the source
- live page, full text, public
- Evidence up to
- Checked
We read this wording on 2026-10-28. The post may have been edited after 2025-06-16.
Where it was said (1)
Said once in the posts we read.
: Where's Your Ed At, Sincerity Wins The War
You cannot just “replace a coder,” because “coder” isn’t really the job
- Where
- paragraph 79
- Published
- 2025-06-16
- We read it
- , live page
- Access
- full text, public
History
Versions
- Current: Unresolved. Evidence up to 2026-10-28.
What happened to this record
PublishedBy us
Published after both AI reviews and the final check passed.
Held backBy us
The final check failed: the quote didn’t match the source.
Held backBy us
The final check failed: our summary didn’t match their words, and the quote didn’t match the source.