Coding Agents as a Continuation of the Normal Technological Development of Code-Writing Tools: CHART OF THE DAY
SubscribeSign in
SubTuringBradBot<br>Coding Agents as a Continuation of the Normal Technological Development of Code-Writing Tools: CHART OF THE DAY<br>From 500,000 Coders to 2.5 Million Devs: What Actually Changed? The programmer’s comparative advantage used to lie in being able to hold complex state in their head and to speak the dialects of...
Brad DeLong<br>Jun 15, 2026
28
Share
From perhaps 2000 calculator-tabulator Wirers in 1935 to 80,000 Coders in 1965 to 500,000 in 1995 to 2.5 Million Devs today: What actually changed in how they spent their time on the job? The programmer’s comparative advantage used to lie in being able to hold complex state in their head and to speak the dialects of both the compiler and the database optimizer. The software developer’s comparative advantage is fuzzier—a finger in many pies, but the ability to buckle down and write or boss the writing of code running very close to the bare silicon whenever it becomes essential to do more than add switches to a wizard…<br>More attention needs to be paid to how 500,000 computer programmers in 1995 in the United States became 2.25 million software developers and 250,000 computer programmers come 2025. Everyone wants to talk about whether AI will replace software engineers; almost nobody asks how the job already changed under their feet.<br>Today we have:<br>Arvind Narayanan & Sayash Kapoor : Why AI Hasn’t Replaced Software Engineers, & Won’t https://www.normaltech.ai/p/why-ai-hasnt-replaced-software-engineers>: ‘Coding agents as normal technology…. Knowledge work, including software development, as… “decide-execute-deliver”…. AI compresses the “execute”… but the other two layers resist automation in a way that will not be overcome by capability improvements alone…. The stories of AI-driven mass layoffs in software seem to be classic “AI washing”…. Among the 270 jobs in the 1950 U.S. census, only one job was automated away — elevator operator. But many others were rendered obsolete by new technology, like the job of telegraph operator….
Share<br>Writing code isn’t, and never was, the bottleneck…. Three things… [are] real bottlenecks:<br>(1) deciding and specifying what to build,<br>(2) verifying and being accountable for what is delivered, and<br>(3) the deep human understanding—of the codebase, the business, and the environment—required to carry out both of these….<br>As more and more of the execution layer gets delegated to AI, the software engineer’s role in the future becomes analogous to that of a crane operator. AI agents will do most of the cognitive heavy lifting; supervising the agent and keeping it in control becomes most of the human’s job…. The sandwich getting squished is a new trend and it is not uniquely due to AI…. This pattern—where humans remain heavily involved at both ends of the decide-execute-deliver sandwich, even as AI increasingly automates the middle layer, seems to be broadly applicable to most knowledge work, though it is farthest along in software.…<br>Some people predict that demand for software engineering skills will fall… [as] the work will be done by people who are not software engineers…. Maybe. But… there have always been [such] claims… FORTRAN, COBOL, and SQL were all accompanied by such prominent hopes…. It never happened. The barrier… is having enough skilled judgment to make good decisions while maintaining accountability…<br>AI as Normal Technology<br>Why AI hasn’t replaced software engineers, and won’t
There is great anxiety and uncertainty about AI replacing jobs. How can we move past vague warnings and bombastic predictions and bring data to bear on this question? One good way is to look at the profession where AI capabilities are furthest along and adoption has been exceptionally rapid: software engineering…<br>Read more<br>6 days ago · 194 likes · 37 comments · Arvind Narayanan and Sayash Kapoor
Give a gift subscription<br>Well, I cannot find much I think is really superb on how what the 2.5 million do is different from what the 500,000 did. So here is my take:<br>First: headcount has multiplied by roughly five, even as tools for writing software have become vastly more productive There have been massive improvements in languages, frameworks, cloud infrastructure, open-source libraries, and now AI coding assistants. In 1995, a “computer programmer” was, to a remarkable extent, a translator between a relatively well-specified business need and a relatively unforgiving, low-level environment. The programmer’s day was spent managing memory, juggling file handles, worrying about whether the database would lock, working around idiosyncrasies of vendor toolchains, and producing line-of-business applications or systems software that ran either on a departmental server in a closet or on a desktop. The interfaces to the rest of the firm were narrow: a requirements document, a meeting with a business analyst, perhaps some end-user...