[Retric]

All jobs past and present involve some very specific domain knowledge and a range of more general skills.

A car salesman needs to know a lot about the product, more general sales tactics, more general skills like email, and even more general skills like just speaking. But, as you narrow down into the ultra specific niche the percent of time working in that domain decreases. What percentage of the time is the sales guy dredging up specific horsepower numbers etc related just to the car they are selling?

Over time what we could consider generalists jobs like secretary have been cut while the tasks have not. So, by handing out those tasks to others those other jobs have in turn become more generalist on a day to day basis. Dev-Ops for example is in many ways the opposite of specialization.

PS: Put another way, if my last job had been using Java instead of C# I would have done the same thing with ~80% of my time. You would be reading the same requirements of the code was in another language.

[SketchySeaBeast]

> Put another way, if my last job had been using Java instead of C# I would have done the same thing with ~80% of my time. You would be reading the same requirements of the code was in another language.

That works well for languages, yes, but what about data scientists, business intelligence, cyber security, and machine learning experts? Those are all jobs that launched off the dev backbone, but are very different, have unique, specific knowledge and require training past what a normal degree requires. Dev-Ops may be a generalist position, but you'd need see someone who does Dev-Ops do those jobs.

[Retric]

'Data scientists' is one of those interdisciplinary fields that does not have an ultra deep dive into any one silo. Rather it's a collection of several skills that are all useful for doing other things which is not really specialization. People can dip into and out of that role with minimal transition unlike say becoming a Doctor.