There's definitely overlap between those concepts. There are also some differences. I guess it depends on the nature of that specific job if it's "blue collar" or not.

I get the feeling from the poster that they are in a "blue collar" environment. Fully managed, working a specialized assembly line. No time for anything else but whipping up the next widget.

There are also SE jobs where you have to be everything. Tweaking servers, calling customers, designing and implementing backends, some frontend work, maybe even helping out with the company website. Meeting with CEOs of partnering companies. I don't see typical blue collar workers doing well in that sort of situations.

> There are also SE jobs where you have to be everything. Tweaking servers, calling customers, designing and implementing backends, some frontend work, maybe even helping out with the company website. Meeting with CEOs of partnering companies. I don't see typical blue collar workers doing well in that sort of situations.

Generally I don't know, I certainly did fine in that type of environment (has been most of my career) - I don't think it's that dis-similar to a contractor (construction not soft-eng) who has to essentially run their own business and do similar types of things.

Some of the smartest (not necessarily academically) people I've worked with where in traditionally "blue collar" roles - most developers aren't that special or that smart (and I include myself in this) - at best we have an aptitude for computers that others lack.

For small construction companies, you get this type of thing all the time with more senior tradespeople.

The problem with an apprenticeship model is that the field is moving so quickly. In many cases the younger programmers are better than the older ones whose experience is already going obsolete. The tech they learned is no longer used, and the best practices of yesteryear are now frowned upon.