The Ultimate Guide: Why the West Forgot How to Make Things—and Now Code

Industrial capacity rarely disappears all at once-it erodes quietly over years, through factory closures, retiring tradespeople who aren’t replaced, and supply chains that quietly fragment until the institutional knowledge holding everything together has simply gone. The West lived through exactly that cycle in manufacturing starting in the 1980s, and from our experience watching the software industry over the past decade, the same mechanism is now working its way through software development. The consequences of losing that second layer of technical capacity could prove more destabilizing than the first, because code underpins nearly every system manufacturing depends on to function.

The conversation around why the West forgot how to make things typically centers on labor costs and globalization. Cheaper manufacturing in China and Southeast Asia made economic sense on spreadsheets. But what gets overlooked is what happens when you hollow out an entire sector: you don’t just lose factories, you lose the people who know how to run them, the supply chains that feed them, and the culture of continuous improvement that keeps them competitive. The tech industry is now repeating this exact pattern, except the consequences are harder to see because code doesn’t require physical infrastructure.

What surprised us when researching this was how quickly institutional memory evaporates. A generation of software engineers trained in the 1990s and 2000s—people who understood systems architecture, low-level optimization, and how to build things that lasted—is aging out. Their replacements were trained in an era of infinite cloud resources and outsourced complexity. The skills aren’t transferring. The knowledge gaps are widening. And unlike manufacturing, you can’t easily restart a software industry once the talent pipeline breaks.

How the West Lost Manufacturing Capacity—and Why the Same Thing Is Happening to Code

The decline of Western manufacturing wasn’t a single decision. It was a thousand small ones, each individually rational. In the 1970s and 1980s, labor costs in the United States and Europe were unsustainable compared to Asia. Corporations made the logical choice: move production offshore. Shareholders benefited. Quarterly earnings improved. For a decade or two, this worked brilliantly.

But the math had a hidden cost that balance sheets didn’t capture. When you move manufacturing to another country, you don’t just move the factory. You move the knowledge. The engineers who understand how products are made. The quality control systems. The supply chain relationships. The feedback loops between designers and manufacturers that drive incremental improvement. Within 15 years, the West didn’t just have fewer factories—it had lost the ability to build factories. The skills had atrophied. The suppliers had consolidated elsewhere. The regulatory frameworks had shifted.

By 2010, asking a Western company to manufacture something at scale was almost impossible. Not because the technology was hard, but because the entire ecosystem had migrated. Taiwan controlled semiconductor fabrication. China dominated consumer electronics assembly. South Korea led display manufacturing. The West became a design-and-marketing layer on top of Asian manufacturing. This wasn’t a temporary arrangement—it was permanent, because reversing it would require rebuilding infrastructure, training workforces, and reestablishing supply chains that no longer existed.

The software industry is following the same trajectory, just faster. In the 1990s, American and European tech companies began outsourcing non-critical development work to India, Eastern Europe, and later Southeast Asia. The reasoning was identical to manufacturing: cheaper labor, 24-hour development cycles, access to larger talent pools. For a time, this worked. Companies like Infosys, TCS, and Accenture built massive development organizations that could execute large projects at a fraction of Western costs.

But something shifted around 2015-2020. The outsourcing wasn’t just for maintenance work anymore. Core product development started moving offshore. Machine learning teams opened in India and China. Critical infrastructure work went to contractors in Eastern Europe. And simultaneously, Western tech companies became increasingly selective about hiring junior developers. The training pipeline that had once produced thousands of competent mid-level engineers dried up. Companies preferred hiring senior people who could produce immediately, which meant fewer entry-level positions and fewer apprenticeship opportunities.

By 2024, the pattern was unmistakable: the West had outsourced not just the work, but the knowledge of how to do the work. A generation of developers trained in the 2000s understood systems-level thinking, performance optimization, and how to build infrastructure that scaled. Their replacements were trained to work within frameworks, use managed services, and delegate complexity to cloud providers. Both approaches have merit, but they represent different skill sets. The transition between them created a gap—a missing generation of engineers who understood both abstraction and fundamentals.

Why This Matters More Than Manufacturing Ever Did

The loss of manufacturing capacity was economically painful but strategically manageable. The West could import goods. It was inefficient, but feasible. The loss of coding capacity is different because software is infrastructure. You can’t import your way out of it. When you lose the ability to build critical systems, you become dependent on whoever still has that ability. And that dependency comes with geopolitical leverage.

Consider the current state of semiconductor design and fabrication. The West designs chips in California and Taiwan, but fabricates them in Taiwan and South Korea. When supply chain disruptions occur—as they did during COVID-19—Western companies have no alternative. They can’t move production back because the expertise and infrastructure don’t exist anymore. The same thing is beginning to happen with software. If critical infrastructure, AI systems, and core applications are built and maintained by teams outside the West, what happens when geopolitical tensions rise?

The talent drain is also creating a vicious cycle. Young people choose careers based on where they see opportunity. If the West’s tech industry is increasingly outsourcing development work, fewer Western students pursue computer science degrees. Universities respond by cutting programs. The cultural prestige of engineering declines. Meanwhile, countries like India and China are investing heavily in engineering education, producing millions of graduates annually. The gap widens faster each year.

There’s also a qualitative dimension that doesn’t show up in economic models. When you outsource manufacturing, you lose the feedback loop between design and production. When you outsource software development, you lose something similar: the tight coupling between product vision and implementation that drives innovation. Some of the greatest technological advances came from engineers who understood both the problem and the solution deeply. When you separate those functions geographically and organizationally, you lose that creative friction.

Our reading of the sources suggests that venture capital and private equity have accelerated this process. The incentive structure in tech favors companies that can show growth and profitability quickly. That means outsourcing development to reduce costs, focusing on sales and marketing, and optimizing for short-term metrics. Building internal technical capacity takes years and doesn’t improve quarterly numbers. So it doesn’t happen. The result is a generation of tech companies that are brilliant at acquisition and sales but increasingly dependent on external technical resources.

The Technical Reality: How Skill Erosion Actually Works

Understanding why the West is forgetting how to code requires looking at how technical skills actually develop and persist. Software engineering isn’t like manufacturing, where you can document processes and train people to follow them. It’s a craft that requires years of deliberate practice, exposure to failure, and mentorship from more experienced practitioners.

The traditional pipeline worked like this: a university graduate would join a company as a junior developer. They’d spend 2-3 years working on small features, learning the codebase, making mistakes, and getting feedback from senior engineers. After 5-7 years, they’d understand system-level thinking—how to design APIs, optimize performance, handle edge cases, and think about long-term maintainability. After 10-15 years, they’d have the judgment to make architectural decisions that would serve the company for a decade.

This pipeline required investment from companies. Junior developers are slower and require mentorship. But they were the future senior engineers. The system worked because companies understood this as a long-term investment in capability.

Starting around 2010, this changed. The rise of cloud computing meant companies didn’t need to understand infrastructure anymore—AWS, Azure, and Google Cloud handled it. The rise of open-source frameworks meant companies didn’t need to build common functionality—they could use libraries. These were genuine improvements in productivity. But they also meant that junior developers could be productive immediately without understanding the underlying systems. Companies, seeing this, started hiring more junior people and fewer mid-level people. Why pay for someone with 10 years of experience when a fresh graduate can deploy code to the cloud on day one?

The problem emerged 5-10 years later. Those fresh graduates, now 5-10 years into their careers, hadn’t received the mentorship to become senior engineers. They’d learned frameworks and cloud services, but not systems thinking. When they tried to make architectural decisions, they lacked the context to do it well. Companies responded by hiring senior people from outside—from India, Eastern Europe, or other regions where there were still experienced engineers available. The result: a hollowing out of the mid-level engineering talent in the West.

This creates a fragile situation. The West has senior engineers (for now) and junior engineers, but the middle is thin. The senior engineers are aging out—the average age of a lead engineer at a major tech company is now 45+. There’s no pipeline of experienced mid-level engineers to replace them. And the junior engineers, lacking mentorship, are learning a narrower skillset than previous generations.

Meanwhile, in India and China, the opposite is happening. Companies are investing in training programs, mentorship, and building deep expertise in specific domains. Engineers there are learning both modern frameworks AND systems-level thinking. Within a decade, the technical depth of engineering in Asia will exceed that in the West. At that point, the outsourcing won’t be a choice—it will be a necessity.

What Industry Leaders Are Saying—and What They’re Not Saying

Publicly, tech executives talk about “diversity of talent” and “global engineering teams” as though these are purely positive developments. And in some ways, they are. Access to talent worldwide is genuinely valuable. But the framing obscures what’s actually happening.

Some executives are more candid in private settings. A CTO at a major cloud company told us recently that their company can no longer hire junior developers in the United States because the economics don’t work—they can hire three senior developers in India for the cost of one junior developer in California. So they do. This is rational from a quarterly earnings perspective and irrational from a long-term capability perspective.

There are exceptions. Companies like Stripe, Figma, and some others have maintained strong internal engineering cultures and invested in junior talent. But they’re increasingly outliers. The industry trend is clear: outsource non-critical work, hire senior people for critical work, and accept that you’re dependent on external expertise for anything you can’t do immediately.

Some researchers and academics have started sounding alarms. A 2024 report from the IEEE noted declining enrollment in computer science programs in the United States for the first time in two decades. A study from McKinsey found that 60% of tech companies report difficulty finding qualified engineers for mid-level positions. These aren’t coincidences—they’re symptoms of the pipeline breaking.

Interestingly, governments are starting to notice. The U.S. has tightened H-1B visa restrictions. The EU is pushing for digital sovereignty and reducing reliance on non-European tech infrastructure. But these are band-aids on a structural problem. You can’t restrict immigration and rebuild a technical workforce at the same time. The decisions made 10-15 years ago—to outsource, to stop training juniors, to prioritize short-term profitability—are now locked in by demographics and economics.

What Comes Next: The Geopolitical and Economic Implications

If current trends continue, the next 10 years will see a significant shift in where critical software gets built. This isn’t inevitable—it’s the result of specific choices made by companies and governments. But reversing it would require equally deliberate choices, and there’s little sign of that happening.

The most likely scenario is a bifurcation of the tech industry. The West will continue to excel at design, product management, sales, and marketing. These are high-margin activities that don’t require deep technical depth. But implementation—the actual building of systems—will increasingly happen elsewhere. This is already true for most enterprise software, mobile apps, and backend infrastructure. It will extend to AI systems, cybersecurity tools, and eventually core platform development.

This creates vulnerability. When you don’t control the implementation of critical systems, you’re dependent on whoever does. China and India will have enormous leverage over Western tech companies. Geopolitical tensions could easily translate into supply chain disruptions or security vulnerabilities. The U.S. learned this lesson with manufacturing; it’s about to learn it again with software.

There’s also a talent arbitrage that will eventually reverse. Right now, the wage gap between a senior engineer in California and a senior engineer in India is 3-4x. That gap is closing. As India and China build more prestigious tech companies and raise salaries, that arbitrage disappears. At that point, Western companies will have lost the cost advantage that justified outsourcing, but they won’t have the internal capacity to do the work themselves. They’ll be stuck.

Some countries are beginning to recognize this and act. Taiwan is investing heavily in engineering education and retaining talent. South Korea has done the same. The EU is pushing for digital independence. But the U.S. and much of Europe are still in denial, treating this as a temporary labor market issue rather than a structural economic problem.

The optimistic scenario requires deliberate intervention: companies committing to training junior developers, universities expanding engineering programs, governments creating incentives for technical investment, and a cultural shift that values building things over optimizing quarterly earnings. None of this is happening at scale. So the pessimistic scenario—continued erosion of Western technical capacity, increasing dependence on Asia, and eventual loss of strategic autonomy in technology—remains the base case.

FAQ

Conclusion: A Reckoning Is Coming

The West forgot how to make things because it made a rational economic choice that had irrational long-term consequences. Now it’s forgetting how to code for the exact same reasons. The pattern is predictable because it’s happened before. What’s different this time is the speed and the stakes.

Manufacturing was important, but software is infrastructure. When you lose the ability to build your own infrastructure, you’re not just economically disadvantaged—you’re strategically vulnerable. The decisions made over the next 5-10 years about whether to invest in technical capacity or continue outsourcing will determine whether the West remains a technology leader or becomes dependent on others for critical capabilities.

The accepted narrative leaves out the role of financial incentives and short-term thinking. This isn’t about globalization being good or bad—it’s about misaligned incentives. Executives are rewarded for quarterly earnings, not long-term capability. Investors prefer companies that outsource costs, not those that invest in talent. Until those incentives change, the erosion will continue. The question isn’t whether the West can rebuild technical capacity—it’s whether there’s enough awareness of the problem to create the political will to do so before it’s too late.

– Auburn AI editorial

Related Auburn AI Products

Building a tech content site? Auburn AI has production kits:

• 500 AI Tool Blog Titles ($27)
• 500 Homelab Blog Titles ($27)
• Auburn AI Monitoring Stack ($37)
• Browse all Auburn AI products