The Displaced Minds: What Happens to a Generation of Problem-Solvers When the Problems Get Solved Without Them?

There's a type of person you'll recognize if you've spent any time in software engineering. They love taking a messy, ambiguous situation and breaking it into pieces. They get a quiet thrill from finding the elegant solution — the one that's simpler than it has any right to be. They try new tools the way some people try new restaurants: compulsively, with opinions. They're mostly introverted, often happiest in a state of deep focus, and they've built their entire professional identity around being the person who figures things out.

I'm an engineering manager. I lead a team of people like this. And I can already see what's coming — because I'm living it. With AI in my daily workflow, I'm not writing most of the code anymore. I'm directing it. Orchestrating it. Reviewing it. The output has gone up. The number of humans required to produce it is going down.

If this trajectory holds — and I believe it will — a significant portion of the people currently working as software engineers will be without that specific job within a few years. Not because they're bad at it. Because the task itself is being absorbed by the machine.

This article isn't about whether that will happen. I think it will. This is about what happens after. Specifically: what happens to all that mental energy? What happens to hundreds of thousands of analytical, problem-solving, tool-loving minds when the container that held their cognitive identity breaks?

I don't have the answer. But I think history has something to say about the question.

The Cognitive Profile, Not Just the Job Title

Before we get to history, it's worth naming what we're actually talking about. The people at risk aren't just "workers who write code." They're a type of mind. Analytical. Systematic. Drawn to complexity. Often introverted. They chose software engineering not because they saw a salary table — or at least, not only because of that — but because it was one of the rare careers that offered high autonomy, deep problem-solving, good pay, and a culture that genuinely respected introversion.

Very few career paths offer all four simultaneously. That's what made software engineering so magnetic for this personality type, and it's what makes the coming displacement so disorienting. The question isn't just "what can they do next?" It's "what preserves the feeling of the work?"

Because here's the thing about these people: their restlessness is productive. They don't just want a job. They want a problem. Take the problem away, and you don't get a relaxed person — you get a lost one.

History Doesn't Repeat, But It Spirals

History doesn't repeat itself, but it moves in spirals — looping through similar patterns at different altitudes, with enough similarities that we can reason about what's coming and enough differences that we can't just copy the playbook. The Industrial Revolution offers three cases that are structurally parallel to what's happening now, and each one maps to a different scenario that could play out for software engineers.

Case 1: The Handloom Weavers (1800s–1840s) — The Closest Parallel

This is the one that should keep people up at night.

Before displacement, handloom weavers lived lives that would be strikingly familiar to any remote software engineer. They worked from home or in small workshops, often alongside family. They set their own pace. They controlled the details of their labor. Their identity was inseparable from their craft. They were skilled, autonomous, and respected in their communities.¹²

The disruption came in two waves — and the difference between them is critical.

First, spinning machines in the 1770s disrupted hand spinners. But those displaced workers were able to transition into another growing cottage industry: weaving the now more abundant and cheaper yarn into cloth.³ For about two decades, weaving actually boomed. The first wave of displaced workers did find new work, in an adjacent skill that was growing precisely because of the new technology.

This is the phase we're in right now with AI and software engineering. The first wave of AI tools — Copilot, ChatGPT, Claude — is disrupting some tasks but creating more demand for the adjacent skill: orchestrating, reviewing, architecting, directing AI output. If you're an engineer who's leaned into these tools, you've probably felt this. You're not writing less code. You're directing more of it.

Then came the power loom. A single power loom could produce more cotton than 10 to 20 handweavers working from home, and the machines were so large they had to be housed in factory buildings, taking cottage industry weaving off the table entirely. The displaced workers had no place to go, because power looms created relatively few new jobs in the factories.³

The wage collapse was devastating. Handloom workers in the English cotton industry averaged 240 pence per week in 1806. By 1820, they were making less than 100 pence weekly — a fall of more than half in barely fifteen years.³⁴

What happened to them? The honest answer is brutal. Most surviving Luddites returned to whatever work they could find, often under worse conditions than before. Others, unable to adapt, sank into long-term poverty.⁵ The historian E.P. Thompson suggested that many handloom weavers simply died off — from old age or prematurely due to impoverishment. From being probably the most numerous single group of workers in manufacturing in the 1820s, they dwindled within thirty years into what one historian called "a picturesque anachronism, encountered only in small numbers and in odd localities."⁶

The question for software engineers is whether the next wave of AI is the spinning jenny (disruptive but navigable) or the power loom (catastrophic for the incumbents). My gut says we're still in the spinning jenny phase, but the power loom is visible on the horizon.

Case 2: The Croppers of Yorkshire — When Even the Elite Specialists Fall

Within the broader Luddite story, there's a subtler case worth examining. In Yorkshire, the Luddite movement was led by the croppers — highly skilled finishers of woolen cloth who commanded much higher wages than other workers and were highly organized.⁷ These weren't generic laborers. They were the equivalent of senior or staff engineers: years of apprenticeship, deep expertise, significant bargaining power.

Before the machines came, a cropper's life was defined by skill and autonomy. They began their trade young, through formal apprenticeship, learning a complex craft under the supervision of a master. This training took years and produced a sense of identity inseparable from the tools they used and the quality of the goods they produced.¹

They faced displacement by shearing frames and gig mills that could perform their work more quickly and cheaply.¹ Their response was more organized than the weavers': they petitioned Parliament, tried legal channels, organized collectively. When those failed, they escalated to direct action. At one point, there were as many British soldiers fighting the Luddites as there were fighting Napoleon.⁸

But the outcome was the same. The artisans whose livelihoods the Luddites sought to protect were mainly displaced, and their crafts were reduced to nostalgia or niche production.¹ At the York Assizes, twelve convicted Luddites were executed. The rest returned to whatever work they could find.⁵

The croppers' mistake — if you can call it that — was fighting to preserve the exact nature of their work rather than translating their underlying cognitive abilities into new domains. Their real skill was understanding materials and quality at a deep level. But they defined themselves as "croppers." The ones who survived were likely those who redefined themselves before being forced to.

The parallel for senior engineers is uncomfortable: deep expertise in a specific technical domain is not the same as safety. If the domain itself becomes automatable, the expertise becomes a sunk cost.

Case 3: The Second Industrial Revolution (1870–1914) — The Hopeful Counter-Example

This is where the spiral gets interesting, because the second big wave played out differently from the first.

The transition from steam to electricity didn't just destroy jobs — it created entirely new categories of work. Second Industrial Revolution automation technologies increased the efficiency and scope of mechanized production, requiring fewer operators but more engineers, managers, and other new occupations.⁹ The displaced farmers who reskilled became boiler makers, ironsmiths, mechanics — roles that had previously been in low demand but were now essential.¹⁰

The most striking statistic: about 60% of workers in 2018 held occupations that did not exist in 1940.⁹ The jobs that absorbed displaced workers weren't just "slightly different versions of the old jobs." They were fundamentally new. No handloom weaver in 1810 could have predicted "office clerk" or "telegraph operator" as career paths. No factory worker in 1920 could have imagined "software engineer."

But there's a critical nuance that the optimistic reading misses. Younger workers led switching into growing occupations, while older workers were more vulnerable to being displaced by the changing technological landscape.⁹ Age was the single biggest predictor of who successfully transitioned and who didn't. The macro story of "it worked out eventually" was cold comfort to the individuals living through the transition.

The Gap Between Productivity and Prosperity

Across every major technological revolution, there's a painful lag between "productivity goes up" and "workers actually benefit." In the early decades of the first Industrial Revolution, even as output per worker rose, real wages stagnated. Wages began to rise in line with productivity only after the middle of the 19th century — a gap of roughly 60 to 80 years.¹¹

In the second Industrial Revolution, institutions like unions, public education, and progressive taxation helped compress that gap to maybe 20-30 years. The third revolution — computerization, starting in the 1980s — is arguably still in its gap period: productivity has risen steadily while real wages for most workers in many Western economies have been essentially flat.¹¹

So what's the gap this time? My intuition says 10-20 years. Faster than the first Industrial Revolution because information moves faster and we've learned how to build institutions. Slower than optimists claim because the institutional response — regulation, education reform, safety nets — always lags behind the technology by a full political cycle or two.

And 10-20 years is an entire career phase. For someone who's 35 right now, that's their prime working years. The economy did eventually create more jobs than the power loom destroyed. But those specific weavers never benefited from it. They were already gone.

But Will the New Jobs Actually Emerge This Time?

Here's where the historical spiral might genuinely break rather than repeat.

In every previous technological revolution, the displacement happened in a domain-specific way. The power loom replaced weaving. The combustion engine replaced horse-related work. Computers replaced calculation and filing. In each case, the technology was very good at one type of task, which meant there were always adjacent domains where human capability was still needed — escape hatches where displaced workers could migrate.

AI is different. It's not domain-specific. It's a general-purpose cognitive technology. It doesn't just automate weaving or arithmetic; it automates the act of processing information and generating solutions across domains. When the thing being automated is the general skill rather than the specific application, the usual escape hatch narrows dramatically. Some economists have put this starkly: the key distinction from past technological changes is that AGI would be capable of performing any cognitive task, potentially leaving few unique economic roles for human workers — unless governments intervene.³

That said, "no new jobs will emerge" is probably also wrong. What's more likely is that new roles will cluster around things AI is structurally bad at: work that requires physical presence, work that requires genuine accountability (someone who can be sued, fired, or held responsible), work that requires navigating ambiguity where the cost of being wrong is catastrophic, and work where the human-ness of the provider is the actual product — therapy, care, teaching, leadership.³

The question is whether those roles can absorb the volume of displaced knowledge workers, and whether they pay comparably. Historically, they haven't.

The Deeper Question: Is Analytical Thinking a Root Skill or a Delegatable One?

This is what keeps me up at night — and it's a question that goes beyond economics into something closer to philosophy.

We've delegated skills before. We delegated counting to calculators and memorizing to books and databases. Those felt like fundamental human skills until we had machines that could do them, at which point we realized they were just tools that supported deeper thinking. Nobody mourns the loss of human-as-calculator. We moved on.

Is analytical thinking — the thing that engineers are so proud of, the thing I'm so proud of in my team — the same kind of delegatable skill?

I think the answer is: it depends on what you mean.

If "analytical" means "the ability to take a well-defined problem, break it into components, and systematically work toward a solution" — yes, that's delegatable. That's essentially what AI already does, faster and more consistently than humans. This is counting and memorizing all over again.

But there's a layer underneath that I don't think is delegatable. Not yet. Maybe not ever. It's the capacity to notice that a problem exists in the first place. To feel that something is off before you can articulate what. To hold contradictory information in your head and sit with the discomfort long enough to find a synthesis rather than defaulting to the first plausible resolution. To ask "wait, should we even be solving this problem?" before optimizing the solution.

The handloom weavers' skill was narrow: they knew how to move thread through a loom in specific patterns. But the best weavers had something else — an aesthetic judgment, a feel for materials, an ability to see the whole cloth while working thread by thread. That meta-skill didn't die with the power loom. It reappeared in textile design, in industrial quality control, in fashion, in architecture. It just took a generation to find its new container.

What engineers have that's genuinely rare isn't "I can write a for loop" or "I can design a database schema." Those are the weaving patterns — specific, trainable, automatable. What's underneath is something more like: the ability to hold a complex system in your head, reason about second-order effects, maintain intellectual honesty when the easy answer is wrong, and enjoy the feeling of being stuck on something hard.

That's closer to a root cognitive orientation than a trainable skill. But — and this is where I have to be honest with myself — engineers are not unique in having it. They've just been in an unusual historical moment where this cognitive style was directly and lucratively monetizable. A farmer reasoning about crop rotation, a mechanic diagnosing an engine by sound, a nurse reading a patient's trajectory from subtle signs — these are all expressions of the same analytical root capacity. Engineers didn't invent systematic thinking. They just had the best-paying venue for it for the last 30 years.

The Luddite Lesson We Keep Getting Wrong

There's one more thing from the historical record that matters here, and it's about timing.

The Luddites organized after their displacement had already begun, when they had already started to lose their negotiating leverage.¹² They weren't anti-technology zealots — that's a myth. They were skilled artisans who saw their autonomy, income, and community being destroyed, and they fought back with the tools they had. They petitioned Parliament. They organized collectively. They tried legal channels. When all of that failed, they smashed machines. And then the British Army was deployed against them.⁸

They were right about the problem. They were right that the technology would devastate their livelihoods and working conditions.¹² They were even right that the factory-produced goods were often inferior — cheap, shoddy, prone to falling apart.¹³ But they lost, because by the time they organized, the economic and political power had already shifted.

The lesson isn't "resistance is futile." The lesson is that the window for negotiation closes faster than you think, and it closes before most people realize it's closing. Today's software engineers still have leverage: the technology is not yet fully deployed, companies still need human expertise to build and refine AI systems, and the economic transition hasn't fully occurred. But that window won't stay open forever.¹²

The Luddites also teach us something about what's lost beyond wages. One researcher studying the parallels between industrial and AI displacement put it starkly: if people are displaced from the work that gives them meaning in life by automation, there are potentially very significant negative effects for how we feel about our lives.¹⁴ The identity crisis isn't a side effect of the economic disruption. It is the disruption, for the people living through it.

Where the Energy Could Go

I don't want to end this with a neat list of "alternative careers for displaced engineers." That would be dishonest — the same way telling a handloom weaver in 1815 to "just become a telegraph operator" would have been meaningless, since the telegraph hadn't been invented yet.

But I do think there are directions worth exploring, not as guaranteed solutions but as hypotheses:

Moving up the abstraction stack. The people who thrive won't be writing CRUD endpoints — they'll be the ones who can architect systems, define constraints, and evaluate AI-generated output critically. The role becomes "technical decision-maker who can validate and orchestrate AI agents." This is the spinning-jenny-to-weaving transition: viable now, but possibly temporary.

Adjacent domains with higher human-judgment ceilings. Security, infrastructure reliability, developer tooling — fields where contextual judgment, adversarial thinking, and organizational risk appetite matter more than raw code output. These have a longer runway, though not an infinite one.

The translation layer. There's a growing need for people who think in systems but can articulate tradeoffs to non-technical stakeholders. Solutions architects, technical product managers, developer advocates. These roles reward the analytical mind but add a human communication layer.

Open-source infrastructure for non-tech domains. Imagine the analytical horsepower of thousands of displaced engineers pointed at problems in agriculture, local government, healthcare logistics, or education. Not SaaS startups — actual public goods. The motivation structure (solve hard problems, build things, meritocratic contribution, async collaboration) maps perfectly to the introvert-engineer personality.

Cooperative technical consultancies. Instead of everyone scrambling for fewer full-time roles, small cooperatives of 3-5 people who share clients and specialize in AI-augmented delivery. Each person maintains autonomy and deep work. Think of the studio model from architecture or design, applied to technical work.

Skilled trades and physical-world problem solving. This sounds like a curveball, but electricians, HVAC technicians, CNC machinists — these are fields where the same analytical, systematic thinking applies but the work has a physical component AI can't touch. The pay is increasingly competitive, the demand is enormous, and the personality fit (solve problems, work independently, use tools) is surprisingly good.

Apprenticeship-style transitions into adjacent fields. The biggest barrier for an engineer switching to biotech or climate tech isn't ability — it's domain knowledge. Structured 6-month apprenticeships where engineers pair with domain experts could unlock enormous value. The engineer brings systems thinking; the domain expert brings context.

The Questions I Can't Answer

I started this piece by saying I don't have the answer. I still don't. But I've arrived at a set of questions that I think matter more than any answer I could offer:

Who builds the new containers? If the specific expression of analytical thinking (writing software) is what's at risk, but the underlying cognitive capacity is still there — who designs the new venues for this type of mind to do meaningful work? Do we wait for the market to eventually create them, as it did after the Industrial Revolution, at great human cost over decades? Or is there a way to proactively build them?

Can we compress the gap? Every technological revolution has had a painful lag between productivity gains and worker benefit. Can we make that gap shorter this time — and if so, how? Through policy? Through new institutions? Through something we haven't invented yet?

What do we owe each other during the transition? The handloom weavers were largely abandoned. The government didn't intervene. Their communities disintegrated. Most of them simply vanished from the historical record. We know more now. We've seen this pattern. Does that knowledge create a responsibility to act differently?

And the most personal question of all: if you're one of these analytical, problem-solving, introverted minds — what do you want? Not what the market will reward. Not what the career advisors suggest. What kind of problem do you want to spend your days solving, if you could choose freely?

I'm asking these as genuine open questions. Not as rhetorical devices, not as prompts for engagement, but because I honestly don't know the answers and I don't think any single person does. The displaced minds of this generation deserve better than a TED talk about "embracing change." They deserve a real conversation about what comes next.

And even if we could delegate that conversation to AI — even if we could ask a machine to design the optimal transition path — it wouldn't absolve us of the responsibility to choose. The croppers of Yorkshire didn't get to choose. The handloom weavers didn't get to choose. We still can.

Let's not waste that.

Sources & Further Reading

Additional references

• "What Happens to the Weavers?" — The Wire (India). Expanded coverage of the Knowable Magazine analysis with additional context on AGI implications. thewire.in

• "Stranded Spinsters" — The British Academy. On the overlooked displacement of female hand spinners — hundreds of thousands of jobs lost with no policy intervention. thebritishacademy.ac.uk

• "Technological Unemployment" — Wikipedia. Comprehensive overview of the historical debate from Aristotle through generative AI, including the 2025 predictions from Ford CEO Jim Farley and Senator Bernie Sanders' proposed "robot tax." wikipedia.org

• "What Are the Causes and Consequences of Industrialization?" — Council on Foreign Relations. On the transition from artisan workshops to factories and the resistance that followed. education.cfr.org

• "Industrial Revolution" — Britannica. On how workers' relation to their tasks shifted from craftsmen with hand tools to machine operators subject to factory discipline. britannica.com

• "We Are Becoming the 'Workless' Generation" — CETHE. On software engineers as "the new Luddites" and the identity crisis of knowledge workers facing displacement. cethe.world

• "When Robots Take All of Our Jobs, Remember the Luddites" — Smithsonian Magazine. On the Luddites' autonomy and leisure before displacement, and economists' debate about transition timelines. smithsonianmag.com

• "Industrial Evolution: Revisiting Labor Displacement in Historical and Modern Contexts" — Meyka. On patterns of adaptation across industrial revolutions and the role of retraining. meyka.com

• "Luddite" — Wikipedia. Comprehensive history of the movement, including the Nottingham origins, the Combination Act, and the Luddite executions. wikipedia.org

• "Power Loom" — Wikipedia. Technical and social history of the power loom's development and its impact on handweavers' wages and employment. wikipedia.org