> Most "computer scientists" are not scientists. They are engineers. They engineer (build) something abstract, software, but that doesn't make them scientists.
Engineering is also a scientific discipline; there is a reason why in German the umbrella term for all engineering disciplines is "Ingenieurwissenschaften".
While physics is about finding the laws that govern nature, engineering (say, mechanical or electrical engineering) is about accepting these laws as foundation, and using these laws to build or improve things. This is not less scientific than physics; (classic) engineers are just experts in a special, more applied sub-discipline of physics.
Similarly, software engineering is about applying the foundations that mathematics, electrical engineering or computer science brought in a similar scientific way.
On the other hand, many people who call themselves "software engineers" don't apply rigorous principles based on the mentioned foundations in a scientific way. Such people are not engineers, but scammers, and should be named this way. :-(
> Now, don't get me started on "data scientists"...
Data science is actually a serious science. It was based on the observation that statistics is just one part of the whole data workflow, so we need people who have a good knowledge about all of the phases of this workflow.
On the other hand, many people who call themselves "data scientists" are rather scammers, and should be named this way. :-(
>While physics is about finding the laws that govern nature, engineering (say, mechanical or electrical engineering) is about accepting these laws as foundation, and using these laws to build or improve things. This is not less scientific than physics; (classic) engineers are just experts in a special, more applied sub-discipline of physics.
>Similarly, software engineering is about applying the foundations that mathematics, electrical engineering or computer science brought in a similar scientific way.
Exactly my point, that's why most of IT professionals should be called "software engineers" and not "computer scientists", just like electrical engineering is not "electrical science" or "physics" even though they it's obviously applied physics.
A graduate with physics degree will not work as electrical engineer, what's with all the "computer science" degrees required to get into software engineering?
Now do UX Researchers.
It's just a label on a box to put people in. I don't really know what "science" or "engineering" is anymore--my SO is a neuroscience phd and has maintained "science is not synonymous with the scientific method; a lot of 'research' science is just collecting and publishing data and it does not need to be reproducible" which makes enough sense but challenges a lot of my priors.
Engineers don't traditionally even "build" anything and there are both upper-case and lower-case engineers in title and legal designation.
Comparatively and in sum the distinction between computer scientist and programmer is actually somewhat simple and quaint.
>It's just a label on a box to put people in.
What we call things is important because that's how we convey meaning/definition of things. Because when we say "computer scientists" people will start comparing them to other scientists which is completely inaccurate.
>Engineers don't traditionally even "build" anything and there are both upper-case and lower-case engineers in title and legal designation.
Not sure what the difference is between Engineer and engineer (again, definitions are important), but I would be ok with equating programmers with other trades...people, like electricians, car mechanics, carpenters, etc. And then higher-end IT professionals (infra/data/application architects) would be akin to engineers, designing, but not building (for the most part).
But neither category would still be scientists.