Were software engineers blue-collar workers all along?
Software developers’ status is being reexamined as AI tools and layoffs erode the sense that programming is an elite, quasi-professional career. Commenters argue over whether labels like “white collar” and “blue collar” are useful at all, suggesting the more important divide is between workers who must sell their labor and owners of capital who benefit from automation. Many note that software work often resembles skilled trade or “machine operation,” lacks the legal protections of traditional professions, and may be especially exposed to technological displacement—prompting renewed calls for worker organization and class consciousness in tech.
Scope of the “blue‑collar vs white‑collar” distinction
- Many argue the dichotomy is outdated or mostly rhetorical.
- Several say the more meaningful axis is worker vs capital owner (those living on wages vs. those living on passive income / capital).
- Others counter that collapsing everything into “labor vs capital” misses important differences between professions and how technology affects them.
- Some note that historically “blue vs white” mapped to physical vs office work, not income level.
Are software engineers essentially blue‑collar?
- A strong contingent says yes: most coding is likened to skilled manual work (plumbing, mechanics, bricklaying, “code farmers”), assembling and maintaining systems rather than doing high theory.
- Others push back: real “software engineering” is about requirements, design, tradeoffs, and discovery, closer to traditional engineering and thus white‑collar.
- Several note that the industry blurred roles (architect vs coder) and avoided licensing, leaving software workers without the legal protections doctors, lawyers, or PEs have.
Class, power, and ownership
- Repeated theme: anyone dependent on a paycheck is working class, whether making $40k or $200k; owning sufficient capital to live off returns is a different class.
- Some dispute that higher‑paid workers share interests with low‑paid ones; others call that “level −1 of class consciousness” and argue both are closer to each other than to billionaires.
- There is debate over how easy it really is to move from labor to capital owner; many say “freely” is a myth.
AI, automation, and job disruption
- Broad agreement that software roles are now heavily exposed to LLMs; some say the “I just code tickets” subset will be squeezed hardest.
- Some see LLMs as just another tool (like the loom or Excel) that skilled workers will learn to use; others argue LLM‑driven code increases tech debt and erodes human understanding.
- Disagreement over whether white‑collar or blue‑collar workers historically suffer more from technological change; manufacturing decline and “rust belt” examples are cited against the claim that blue‑collar workers have “ridden the wave.”
Unionization and class consciousness in tech
- Multiple comments argue that software workers are realizing they are not future billionaires but workers, and should organize like other trades.
- Tech’s failure to unionize during boom times is framed as a major strategic mistake.