3 ms·
I agree with the fact that they need to be treated as separate roles, although a lot of organizations just don't understand this well enough and you end up havi
by nerdponx 5y ago
I agree with the fact that they need to be treated as separate roles, although a lot of organizations just don't understand this well enough and you end up having data engineers doing data science, or data scientists doing data engineering, or both, maybe without the teams ever really talking to each other.
However I think that's a somewhat different issue from the one under discussion here. The problem here is that data scientists can end up wasting time trying to apply fancy techniques, when the real impact would come from basic data analysis using old-school statistics.
Interestingly, I have never encountered this in my personal experience. I don't personally know any data scientist who would rather use in neural network win something simpler would suffice.
Also, I disagree with the idea that data scientists don't need long periods of concentration. If anything, data science is more of a "creative" enterprise, whereas coding tends to be somewhat methodical and mechanical. For me at least, that means long periods of time spent trying different things and contemplating, which requires just as much deep focus as writing a complicated piece of software.