Why AI Hasn't Replaced Software Engineers, and Won't
Original: Why AI hasn’t replaced software engineers, and won’t
Evidence-backed analysis argues AI tools amplify developer productivity but won't trigger mass software engineering layoffs.
Princeton researchers Arvind Narayanan and Sayash Kappor examine software engineering — AI's most exposed profession — and find no evidence of mass displacement. New York WARN Act data shows zero AI-related layoff disclosures after a full year of filings. Their qualitative analysis identifies three automation-resistant bottlenecks: specifying what to build, verifying outcomes, and the deep contextual understanding of codebases, businesses, and environments that only humans accumulate.
In a widely circulated essay, Princeton computer scientists Arvind Narayanan and Sayash Kappor challenge what they call the threshold fallacy — the assumption that once AI coding capabilities cross a certain bar, mass layoffs will follow. They deliberately choose software engineering as their test case because it faces unusually few regulatory barriers and is directly in the path of AI automation. Their conclusion: if disruption were going to happen anywhere first, it would be here — and it isn't.
Free shows the 3-line summary; Pro unlocks the full deep summary (~300 words) so you never have to click through.
See Pro plans →Want the original English / full article?
Read on Simon Willison's Weblog →Summaries are AI-generated; the original article is authoritative.