Industry & Society

Were Software Engineers blue-collar workers all along?

The post recasts software engineering as a skilled trade facing automation, but the discussion suggests the collar label matters less than capital ownership—and AI's actual labor impact remains contested.

66 points99 comments

The post argues that software engineering may be better understood as a skilled trade than as white-collar knowledge work. The author says developers make and fix things in bits, require years of practice rather than necessarily formal education, and are now confronting automation much as tradespeople have.

He suggests this misclassification fuels an AI identity crisis, and that the end of software's protected 'honeymoon' will force developers to adapt to new tools rather than assume immunity.

Key takeaways

  • The author challenges the white-collar label because software developers build and repair systems, albeit in bits rather than atoms.
  • He argues skilled-trade framing credits years of practice and does not depend on formal education.
  • He links the classification to an AI identity crisis: blue-collar trades have historically adapted to technology, while white-collar workers face more disruption.
  • He says software developers enjoyed 30 years of protected time, high pay and deference, and that this honeymoon is ending.
  • Analogies include seamstresses facing looms, lumberjacks facing chainsaws and accountants facing Excel; adaptation is possible.
  • He notes hand sewing and chopping wood persist as hobbies even when no longer paid work.

What people think

Class categories and capital ownership

Replies question whether collar labels matter, arguing worker versus capital owner is more fundamental; some see divide-and-conquer, others warn of ideological collectivization.

AI and job disruption

Debate whether AI mainly threatens white-collar desk work; rob74 says it confirms desk work is white-collar, phyzix5761 expects robotics next, darkwi11ow distinguishes routine coding from invention.

LLM reliability and scaling

Autious argues LLMs rest on loose foundations, limited understanding, misunderstood risk, and no guarantee of linear scaling.

Data theft and legal exposure

The same comment cites data theft and shaky legal grounds as reasons not to accept LLMs.

Class boundaries and interests

epolanski notes workers are often shareholders via pensions; HPsquared says education and training can be capital; cucumber3732842 sees income divergence fracturing worker solidarity.