Why AI hasn’t replaced software engineers, and won’t
Narayanan and Kappor challenge the prevailing narrative that AI will trigger mass job displacement once capabilities cross a threshold, using software engineering as their test case. Their argument hinges on empirical data showing that even in a sector with minimal regulatory friction and maximum AI exposure, widespread layoffs haven't materialized. The implication cuts deeper than tech employment: if knowledge work remains resilient despite AI's direct applicability to coding tasks, other professions with stronger institutional, legal, or social barriers face even lower displacement risk. This reframes the AI labor debate from inevitability to contingency, suggesting adoption friction and organizational inertia matter more than raw capability.
Modelwire context
Analyst takeNarayanan and Kappor's argument is methodological as much as empirical: they're treating software engineering as a natural experiment precisely because it removes the usual excuses (regulation, physical constraints, slow procurement cycles) that defenders of other professions rely on. If the most favorable conditions for displacement haven't produced it, the burden of proof shifts to those predicting displacement elsewhere.
This is largely disconnected from recent activity in our archive, as we have no prior coverage to anchor it to. It belongs to a growing body of labor economics commentary pushing back on capability-centric displacement models, a conversation that has been running in parallel to the mainstream AI hype cycle. The empirical grounding here is notable because most prior arguments in this space have relied on projections rather than observed employment data from sectors already saturated with AI tooling.
Watch whether Bureau of Labor Statistics software developer employment figures for Q2 and Q3 2026 show any statistically meaningful contraction. If headcount holds flat or grows despite continued AI coding tool adoption, it would directly validate the organizational inertia thesis Narayanan and Kappor are advancing.
This analysis is generated by Modelwire’s editorial layer from our archive and the summary above. It is not a substitute for the original reporting. How we write it.
MentionsArvind Narayanan · Sayash Kappor · Simon Willison
Modelwire Editorial
This synthesis and analysis was prepared by the Modelwire editorial team. We use advanced language models to read, ground, and connect the day’s most significant AI developments, providing original strategic context that helps practitioners and leaders stay ahead of the frontier.
Modelwire summarizes, we don’t republish. The full content lives on simonwillison.net. If you’re a publisher and want a different summarization policy for your work, see our takedown page.