DEV Community

Gabriel Pickard
Gabriel Pickard

Posted on

Data Science is dying out

As a Data Scientist you usually do one of two things:

  1. You comb through a pile of numbers derived from a SQL database, S3 or an HDFS cluster, in order to answer questions like "what keeps customers from converting?" and make predictions like "How much is a given user worth?".
  2. You build Machine Learning models that do actual ongoing work in deployed applications.

For both of these task groups there exists a different job title with similar job description:

  1. If you replace the SQL with Excel spreadsheets, then Analysts have been and still are answering the same kind of questions.
  2. Software Engineers have been doing Machine Learning for a long time. Long enough that there now is such a thing as a Machine Learning Engineer.

Data Scientists distinguish themselves from Analysts by knowing a bit more about programming. They distinguish themselves from Software Engineers by knowing less about programming. They differ from both in that Data Scientists usually are expected to have gone to grad school and know a thing or two more about math.

The "Data Scientist" job title was a way for industry to hire academics to do the kind of computational modeling that PhD candidates usually do in academia.
Also, it was a way for managers to feel cool, hip and with it.

But it's dying.

Why you say? Well, hear me out:

  1. Analysts can and do learn how to write SQL queries. Often (not always) the math involved in answering business questions can actually be kept relatively simple, you often don't need a PhD to do it. Doesn't hurt though, I guess.
  2. Machine learning is getting commodified. You no longer need a PhD and write your own backpropagation algorithm in order to do Deep Learning. (It's sad, I know.) All you need is GPUs and money to burn. -- Well, and feature engineering, you do need feature engineering from time to time. And some experience in the field and domain knowledge. But all those can be acquired by any bright individual. Also, if your models are to do real work, they usually need to be integrated into real code. Here it comes in handy to know a thing or two about Software Engineering. Hence the rise in popularity of the ML Engineer.

Now I know for a fact that once you give a group of people in the professional class a title and a decent salary, they'll make sure their field will continue to be needed, come hell or high water. So, in fact: I lied.

Data Science is going nowhere, it's just that if you happen to not have Data Scientists on hand at your organization, don't fret, you still can get stuff done.

But if you decide you do desperately need someone to make sweet, sweet Science to your Data, you might be in luck: I'm a Sciencer of Data myself, possibly accepting clients. -- Or maybe I'm an ML Engineer, or something like that... Just give me a ring.

Top comments (2)

Collapse
 
davidjames profile image
DavidJames

I've been doing this (programming, developing, whatever) for 20+ years and I think it's generally a very bad idea to hire someone with a PHD for anything related to enterprise computing unless your business is writing embedded OS's (or something like that) AND you can't find someone familiar with the topic. In my experience all you have after a few years is a code base that's incredibly convoluted, fragile, and impossible to follow (but it's 'clever!'). Work on simplifying everything; everything CAN be simplified (I promise!).

Collapse
 
waylonwalker profile image
Waylon Walker

I think the biggest value that data science is bringing to our organization is having someone with more subject matter expertise who knows how to write some code to get things done. Call us what you will, but before the recent boom of data science our organization was quite limited to excel and MS access. Having a team of folks who could aggregate down a massive dataset for other subject matter experts to use is quite valuable. It can also be done quick enough that you barely notice the time lost to the big projects.