In order to get an idea of what our data looks like, we need to look at it! The Jupyter Notebook, embedded below, will show steps to load your data into Python and find some basic statistics to use them to identify potentially issues with new data that arrives.
This process is simply the exploratory step, we will build part of the pipeline in the next step. It’s imporant to have notebooks involved once in a while in order to make sure we know what we’re looking at.
Keep in mind, this is the first look at the data and we’re checking out some very basic testing. These tests will become more robust and meaningful as we continue to build out this pipeline.
ETL (Extract, Transform, Load) is not always the favorite part of a data scientist’s job but it’s an absolute necessity in the real world. If you don’t understand this process, you will have a basic grasp on it by the time you’re done with these lessons. I will be covering:
Understanding your data
Looking for red flags
Utilizing both statistics and data visualization
Checking your data for issues
Identifying things outside of the “normal” range
Deciding what to do with NaN or missing values
Discovering data with the wrong data type
How to clean and transform your data
Utilize the pandas library
Getting data into tidy format
Dealing with your database
Determining whether or not you actually need a database
Stoltzmaniac Fans – It’s time for a #100DaysOfCode update.
I have completed 11 days of the challenge. Let me tell you, it has been a blast and I have already learned a lot. In this post I’ll walk you through what I’ve done thus far. Here is a link to the code on my GitHub repository.
As you may recall from my previous post I set out to create a flask application to host data science projects for the Meetup group that I organize (Fort Collins Data Science Meetup). My goal is to provide people with an outlet to run code online where they will get the benefits of having a server and a dynamic UI. This will improve the group’s collaboration and Git skills along with allowing people to showcase their work without having to build infrastructure. In case you’re wondering, I built this using Docker Compose, Flask, NGINX, PostgreSQL, and MongoDB.
In order to keep from boring myself to sleep while writing this, I’m going to keep it short and to the point. You might be asking, “what does this application look like?” That’s a great question. It’s a normal website where people contribute Python scripts to do some sort of data processing or analysis. For example, here’s a word cloud generator where the user inserts a Twitter handle with a link to a logo of some sort and then a word cloud is created from all of the most recent tweets! Here is @realdonaldtrump as the Republican elephant and @barackobama as the Democrat donkey.
Starting the 100 Days of Code ( #100DaysOfCode ) challenge
I am always looking to boost my coding skills and as I watch everyone make resolutions for the year, I couldn’t help but think I should try this challenge. In case you don’t know what I’m referring to, one resource is https://www.100daysofcode.com/ – which really gives you a good overview of what the challenge involves.
What will I be building?
I am a project-oriented person, so I will be building a web application that runs sentiment analysis on text data from APIs.
The basic topics I hope to cover:
Store data from external APIs
Utilize PostgreSQL and MongoDB
Back end API development
Luigi ETL pipeline
I will try and send out a blog update every week or two with highlights! I will also be updating GitHub as I go along. Part of the challenge is also posting on Twitter, so each day I’ll be using the hashtag #100DaysOfCode and you can follow me @stoltzmaniac