← Back to Library

Why “learn to code” failed

The Three-Word Mantra That Ate Higher Education

PolyMatter's deep dive into the "learn to code" phenomenon arrives at a moment when the wreckage is impossible to ignore. Fewer software developers are employed in the United States today than six years ago, even as computer science programs have ballooned to grotesque proportions. The video traces a clean arc from political slogan to cultural religion to economic reckoning, and it lands most of its punches. But some of its sharpest observations deserve more scrutiny than they receive.

The numbers alone tell a damning story. At UC Berkeley, computer science graduates increased by over 1,000 percent in a single decade. At MIT, a full 40 percent of undergraduates now study the same subject. Seven chemistry majors graduated from MIT last year. Seven. American universities, as PolyMatter puts it, have transformed from multidisciplinary institutions into

Microsoft training programs that also dabble in philosophy and physics on the side.

That line is funny because it is barely an exaggeration. The concentration of talent into a single discipline represents one of the most dramatic shifts in the history of American higher education, and it happened in plain sight, cheered on by politicians of every stripe.

Why “learn to code” failed

A Bipartisan Fever Dream

One of the video's strongest arguments is that "learn to code" succeeded precisely because it meant different things to different people. Republicans saw vocational training. Democrats saw economic empowerment. Corporations saw a taxpayer-funded labor pipeline. National security hawks saw geopolitical advantage. The slogan was, in PolyMatter's framing, "vague enough to absorb virtually any of the difficult questions posed by globalization at an especially fraught moment."

This is a genuinely useful insight. The bipartisan consensus around coding education meant that nobody was asking the obvious follow-up questions: How many programmers does the economy actually need? What happens when supply outstrips demand? Is coding really comparable to literacy, or is it just another skilled trade subject to the same boom-and-bust cycles as every other?

President Obama called coding "a ticket to the middle class." President Biden offered his own characteristically blunt endorsement:

Anybody who can throw coal into a furnace can learn how to program for God's sake.

The condescension embedded in that comparison is remarkable in hindsight. It simultaneously oversells the accessibility of programming and undersells the intelligence of manual laborers. It is the "learn to code" ethos distilled to its essence: the assumption that any job worth having involves a keyboard, and that the barrier to entry is merely willingness.

The Boot Camp Mirage

PolyMatter's account of coding boot camps follows a familiar Silicon Valley trajectory: disruption, growth, compromise, and collapse. The boot camps promised to do what universities could not -- turn anyone into a six-figure programmer in twelve weeks. But they ran headlong into the same constraints they claimed to have transcended.

The teacher shortage hit boot camps just as hard as it hit universities. A PhD student earning a $40,000 stipend could make five times that at Amazon or Netflix. Boot camps resorted to hiring their own recent graduates who could not find work elsewhere, a detail that should have alarmed prospective students far more than it did.

The most revealing passage concerns how boot camps and universities eventually merged into a single dysfunctional system. Through a 2011 Department of Education loophole, universities could partner with "online program managers" -- the boot camps, rebranded -- who would create curricula, hire teachers, and recruit students. The university would slap its name on the product for a 40 percent cut. Boot camps got access to federal student loans. Students got a trusted brand name. And the government got to pretend the whole arrangement was accredited.

Put differently, boot camps became more and more like the unwieldy, inefficient 4-year universities they originally sought to disrupt until they were swallowed whole by those very same universities.

This is a pattern that repeats across industries: the disruptor gradually adopts the practices of the incumbent, discovers those practices exist for reasons, and ultimately becomes indistinguishable from what it sought to replace.

What the Analysis Misses

For all its strengths, PolyMatter's narrative has some blind spots. The video attributes the current tech downturn primarily to rising interest rates and an oversupply of programmers. Both factors are real, but the elephant in the room -- artificial intelligence -- receives only a passing mention as an example of tech volatility. This is a significant omission.

The irony is almost too neat: the very industry that told everyone to learn to code is now building tools designed to automate coding itself. GitHub Copilot, Claude, and similar AI systems are not replacing programmers wholesale, but they are changing the calculus of how many programmers a company needs for a given amount of output. The "learn to code" generation may find that the skills they acquired are being devalued not just by oversupply but by the tools their own industry created.

The video also underplays the genuine value that coding education has delivered to millions of people. Not every computer science graduate ends up unemployed or disillusioned. The median salary for software developers remains well above the national average. The problem was never that coding is a bad career -- it was that coding was sold as the only career worth pursuing, and that the pipeline was built to produce far more graduates than the market could absorb.

There is also an uncomfortable class dimension that PolyMatter touches on but does not fully develop. The students who benefited most from the coding boom were those who already had advantages: financial cushions to weather unpaid internships, family connections in the industry, prior exposure to computers, and the luxury of attending elite programs. The students who suffered most were those the movement claimed to help:

Many single parents working two jobs earnestly enrolled in boot camps, only to discover they offered minimal support for and couldn't accommodate non-traditional students. Former general contractors struggled to keep up with their peers who had prior coding experience. And since they were told learning to code is so incredibly easy, they blamed themselves.

That last sentence is the cruelest part. When a movement tells people that failure is nearly impossible, those who fail internalize the shame rather than questioning the premise.

The Deeper Lesson

PolyMatter frames the moral of this story as one about economic fundamentals: supply and demand always wins, no matter how many inspirational speeches say otherwise. That is correct as far as it goes. But there is a broader lesson about the danger of monoculture thinking in education and workforce development.

Every generation has its version of "learn to code." In the 1950s, it was engineering. In the 1980s, it was finance. In the 1990s, it was law. Each time, a surge of enthusiasm floods a single profession with more aspirants than it can absorb, credentials are diluted, and the workers who arrived late to the party bear the heaviest costs. The specific profession changes; the pattern does not.

The video makes the point that demand for occupational therapists is expected to grow by 22 percent and wind turbine technicians by 60 percent -- far faster than software developers. Yet nobody is filming inspirational YouTube videos about occupational therapy. No president has declared servicing wind turbines a ticket to the middle class. The jobs that most need workers are rarely the ones that capture the cultural imagination.

Bottom Line

PolyMatter delivers a well-structured autopsy of a movement that promised universal prosperity through a single skill and instead produced an oversaturated labor market, a generation of indebted graduates, and a higher education system warped beyond recognition. The analysis is strongest when it follows the money -- tracing how boot camps, universities, and the federal loan system merged into a self-reinforcing machine that served institutional interests far better than student interests. It is weakest when it skirts the AI question, which may ultimately prove more consequential than anything else discussed. The fundamental error of "learn to code" was not that coding is unimportant. It was the fantasy that any single skill could serve as an insurance policy against economic uncertainty -- a fantasy that persists today, with "learn AI" rapidly replacing "learn to code" as the mantra of the moment.

Sources

Why “learn to code” failed

by PolyMatter · PolyMatter · Watch video

Between 2011 and 21, the number of computer science graduates at UC Berkeley increased by 1,16%. If this trend continues, as one professor observes, all 30,000 of its undergrads will study computer science in just 7 years. By 209, the school will churn out more computer scientists than there are people in California. Meanwhile, get this.

There are fewer software developers employed in the United States today than there were 6 years ago. Clearly, something has gone terribly wrong. And Berkeley isn't even the most computer science obsessed university. Not even close.

This is UCB. This is Caltech. And this is MIT. You're not reading this wrong.

A full 40% of the school that once helped invent the radar spreadsheet and lithium ion battery studies the same one subject. Last year, a grand total of seven students graduated from MIT with a bachelor of science and chemistry. 266 majored in computer science and engineering. And that's not even its largest CS major.

Electrical engineering and computer science is over twice as popular. Over the past 15 years, US colleges have transformed from multiddisciplinary institutions of higher education to Microsoft training programs that also dabble in philosophy and physics on the side. In 2023, Berkeley joined MIT and Cornell in even creating an entire college of computing, its first new school since Eisenhower was president. It's not hard to see how we ended up here.

The iPhone was released in 2007. Uber, Airbnb, and Instagram soon after. America's cultural center of gravity was shifting from stuffy Wall Street boardrooms to youthful Bay Area garages. Shows like The Social Network and Silicon Valley mythologized the tech founder.

The 21st century's more meritocratic, more visionary, and certainly more eccentric answer to the industrial tycoons of the past. Then our nation's leaders endorsed programming with their official seal of approval, elevating it from a promising new career to the future. While in office, President Obama called coding a ticket to the middle class. The White House celebrated Computer Science Education Week, promoted Hour of Code, and warned of a dire shortfall of 1 million STEM graduates by 2022.

New York Mayor Michael Bloomberg even announced he personally would learn to code in 2012, although there's no evidence he ever did. There was something for everyone in that three-word mantra, learn to code. For Republicans, this directive neatly aligned with their vision for more vocational ...