If it is a spectrum, why keep insisting to put arbitrary labels on parts of it. Every job has a different combination of tasks that make sense to be externaliz

If it is a spectrum, why keep insisting to put arbitrary labels on parts of it. Every job has a different combination of tasks that make sense to be externalized and those that don't. Even the most NIH people will draw a line somewhere and don't do everything from scratch. And the combination changes for the same job over time as the product/project/company evolves. Trying to capture the exact breadth of a given job in the title alone is in my opinion bound to just lead to endless bikeshedding. But I'm wondering, if, long term, it ceases to be a spectrum and becomes clearly distinguishable areas of people writing the infrastructure, libraries, frameworks etc. and those that combine them to the final product.