Not sure all jobs in software are white collar. Some are blue.
Consider a hierarchy:
- coder: translates requirements into code
- developer: comes up with software to meet specified goals
- engineer: decides what why and how to do, buy vs. build, do this with humans or software, approach and materials ... understands the multi modality stuff of which the outcome is made and deploys it effectively
"Devs" or "Engineers" who are actually "Coders" are at risk, as that work is not really "white collar". Turning requirements into code is piece work on an assembly line, blue collar at a keyboard.
LLMs are already better than most of those, even though it's engineers here who are saying LLMs don't cut it. Both things are true.
What engineers might want to wrap their head around is using LLMs as apprentices, leverage, force multipliers, so a "team lead" is leading a team of junior coders, LLMs that type.
Consider a hierarchy:
- coder: translates requirements into code
- developer: comes up with software to meet specified goals
- engineer: decides what why and how to do, buy vs. build, do this with humans or software, approach and materials ... understands the multi modality stuff of which the outcome is made and deploys it effectively
"Devs" or "Engineers" who are actually "Coders" are at risk, as that work is not really "white collar". Turning requirements into code is piece work on an assembly line, blue collar at a keyboard.
LLMs are already better than most of those, even though it's engineers here who are saying LLMs don't cut it. Both things are true.
What engineers might want to wrap their head around is using LLMs as apprentices, leverage, force multipliers, so a "team lead" is leading a team of junior coders, LLMs that type.