Let’s play a quick puzzle game.
Question: Name the company.
Clue 1: This company is one of the big 4 technology companies on the globe along with Amazon, Apple, and Google.
Clue 2: It sprouted out in 2004.
Clue 3: It reported global revenue of $55.8 billion as of 2018.
That should’ve been a piece of cake! (I have no presents for you, though :/).
The answer: Facebook.
Apart from these well-known facts about Facebook, I’d like to take you back to a few years.
It was 2004 when Mark Zuckerburg along with his four Harvard University friends founded Facebook. Two years went by and the team was pulling out all the stops to grow their company. In 2006, Zuckerburg hired the first Data Scientist — Jeff Hammerbacher, a math nerd who was fresh out of college. He was given a princely title of a research scientist, whose role was to primarily find out how people use social networking service.
Five Data Preparation Blunders You Need to Get Rid
In a Bloomberg interview, Jeff shared his experience on crunching data and building a new class of analytical technology when Facebook had no tools to do these yet. He later channelized his data science proficiency to provide better cancer treatments by analyzing large biological datasets after leaving facebook.
All Data Scientists like Jeff, end up spending a lot of their time on data preparation rather than channelizing their time and technical know-how into modeling, computation, and training.
Why Faulty Data Makes Your Castles Wonky
Data preparation is a tedious task. It involves a ton of time and effort and is required to be error-free to make ingenious inventions. Data Science is taking a direction towards applications of data in transforming infrastructure, transportation, environment, medicine, and many other significant arenas for a better and advanced living.
Today, I’m going to take you through certain common data preparation mistakes that are costly and cause serious repercussions like wrong insights and strategy, iterations of complex models, and dysfunction of analytical models.
Five Data Preparation Blunders You Need to Get Rid off
1. Losing the context of the use case — Why deviation is dangerous
The technical expertise vested with the IT departments enables operations and implementation of data preparation. While a combination of this control between IT and business departments gives a healthy blend of business know-how and technical expertise, data preparation completely vested with the IT department has a minor setback.
To continue reading, head to DZone where this article was originally published.
[wd_hustle id=”Subscription-1″ type=”embedded”/]