Structural Unemployment is Here: Blame the Software Engineers

September 6, 2011

Here in the U.S. we just concluded our Labor Day holiday, and I spent it thinking about labor. 

More specifically, I was intrigued by the difference between the labor required to design something versus actually building that thing.

For example, in almost every engineering discipline, an engineer cannot his or herself physically build the entirety of their design. One person alone usually cannot build a house or an automobile or a bridge. I’m obviously not including outliers like small rural shacks which can be envisioned and built by the same person. I’m talking about things that bring lasting value to a significant number of people.

In contrast, software engineering stands out as one of the only, if not the only engineering discipline where one person could conceivably build out their entire vision, no matter how large.

In fact, it’s no secret that Facebook founder Mark Zuckerberg coded almost the entire site himself. [1] Bear in mind that Facebook is web software that’s roughly equivalent to a large urban agglomeration in the physical world. To think that one man could singlehandedly build a city of that size would be absurd. But in the realm of software, one individual could build a proverbial palace of software with nothing more than their own intellect and rapid-fire typing.

This amazes me, but it also leads to deep questions about the long-term sustainability of our labor market.

The evidence has been mounting lately about the structural nature of post-recession U.S. unemployment. [2] As the Federal Reserve contemplates QE3 (“Operation Twist”) and Treasury officials scratch their heads over possible fiscal or monetary fixes, it’s become clear that deeper underlying conditions are keeping more and more Americans jobless.

[3]

The labor efficiency of software engineers and related high-technology workers is likely a culprit in the structural unemployment problem. As more highly utilized products and services are digitized, more things are built by fewer people. This isn’t even about robots and automation, but the changing nature of what we’re building and how it’s built.

This could be the end of the theory: software is less labor-intensive than previous economic output and therefore labor demand will continue to drop as software demand rises.

But stopping here would be naive. The digital revolution has just begun. We are only now beginning to build out the “application layer” of the technology stack upon all the infrastructure that was built out in the 90s and 00s. [4] This means that while overall demand for labor may not increase, demand for software engineering and related fields will continue to skyrocket as a larger chunk of economic output is dominated by software.

This makes our economics problem an education problem: making sure enough of the labor force is trained in software engineering, computer science and related fields. There should be a twofold focus on both technical retraining for adult workers and strong reform of K-12 programs that emphasize these disciplines. The former received a creative proposal by Jason Calacanis a month ago entitled “A New New Deal” that’s worth taking a little seriously in times like these. [5]

Hopefully by Labor Day 2012, policymakers have realized this and allow me to enjoy the holiday without such intellectual exercises. We can only hope (or learn to code).

[1] – Most of the early product, at least, was coded solely by Zuckerberg. Shortly after launching, other top programmers like Adam D’Angelo joined the effort and it scaled up from there.

[2] – A recent report on investing blog Seeking Alpha contemplates “Quantitive Easing 3″ in light of structural unemployment concerns. It quotes an FOMC member as stating that, “the current high level of long-term unemployment, which as of July accounts for about 44% of all the unemployed, might signal a mismatch between the skills of the unemployed and the jobs currently available.”

[3] – Structural unemployment chart from Felix Salmon’s warning in June.

[4] – See Carlota Perez’s book Technological Revolutions and Financial Capital: The Dynamics of Bubbles and Golden Ages

7 Responses to “Structural Unemployment is Here: Blame the Software Engineers”

  1. Sosholozo Says:

    Not everyone can program:

    http://www.codinghorror.com/blog/2006/07/separating-programming-
    sheep-from-non-programming-goats.html

    > All teachers of programming find that their results display a ‘double hump’. It is as if there are two populations: those who can [program], and those who cannot [program], each with its own independent bell curve. Almost all research into programming teaching and learning have concentrated on teaching: change the language, change the application area, use an IDE and work on motivation. None of it works, and the double hump persists. We have a test which picks out the population that can program, before the course begins.


    • This is very interesting indeed: that some people simply can’t be taught to program. This is why any reform policy must take into account the “related fields” I discuss. I don’t mention it specifically, but there’s things like graphic design, UX/UI design, etc… that will also be needed.

  2. Harold Says:

    “the current high level of long-term unemployment … might signal a mismatch between the skills of the unemployed and the jobs currently available.” (an FMOC member).

    As I understand it, it is thought the biggest problem here is that relatively unskilled labor, priced out of manufacturing in the US (while our manufacturing output has continued to go up) switched to construction, which of course has now gone bust. That’s structural and is insolvable in the current political environment which is driving up the cost of labor ever higher (e.g. Obamacare), and I don’t see how it relates to software development.

    You are of course right that software development is an incredibly leveraged activity (although far too many organization are far too effective at negating that…). But why blame us for not solving a problem we didn’t cause? That’s not even a sin of omission.

  3. pete w Says:

    You might really enjoy a book written by Kurt Vonnegut called “player piano”. It was written in 1952 but it was a futuristic depiction of software programmers and robot builder replacing every human occupation possible. Even the lesser programmers are replaced by robots as more intelligence arises. While the premise of the book is supposed to be hyperbolic science fiction, it really agrees with the premise of your article.

  4. Mathanas Says:

    This is a facts displaying post. software engineering is the only engineering discipline where one person could conceivably build out their entire vision no matter how large it may seem to be. This is largely contributing to the high level of unemployment experienced currently in the world. The labor market will keep on increasing its demand, as long we don’t concentrate on other engineering disciplines.

    Thanks for this brilliant and well elaborated post.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 139 other followers