I don't understand “data scientist”.
What “scientist” is not a “data” scientist?
If the focus is on extracting patterns and insight from large datasets, without expert knowledge about the particular domains, to assist decision-making, a might be what you need.
I'm happy to be educated by any reading this, though.


@tripu it's a very bad umbrella name for a series of very serious jobs. I prefer to split into different roles, but we don't have names for all of them yet.

Basically, either you are a data engineer (ETL, deploy, monitoring) or a machine learning engineer (one shot ETL, modeling, analysis), but there's a continuum between the two roles and one can very well be a mix between the two

In large companies one might even be dedicated to visualization and dashboard and would still be a data scientist

@tripu so a data scientist might very well be a statistician or a physicist for instance, but ideally a data scientist would be better at coding than the previous two.

I stress ideally, because I've seen many and most of them just code, in the sense that they are users of a language and don't really know how to build software

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!

We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.

Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!