Instructor: Marco Morales, Columbia University
Co-Instructor: Nana Yaw Essuman, Columbia University
TA: Alisha Gurnani, Columbia University
This repository is a companion to the course Applied Data Science for Social Scientists taught at the Quantitative Methods in the Social Sciences program over the Spring of 2021.
It contains curated reference materials, slides and sample code. You can find the most updated version of the course syllabus here. Make sure to check regularly for updates.
In his now classic Venn diagram, Drew Conway described Data Science as sitting at the intersection between good hacking skills, math / statistics knowledge, and substantive expertise. Standard quantitative training in the social sciences supplies a fluid combination of all three, but tailored to understanding human behavior, and to explaining why things happen the way they do. Social scientists are, thus, a particular kind of data scientist.
This course is a collection of topics that fill very specific gaps identified over the years on what a social scientist should know at minimum when entering Data Science, and what a data scientist should be skilled at to add immediate value to their teams.
To do that, this course aims to:
-
teach processes and practices at the intersection of Data Science and Data Engineering that are central to the data product cycle. Data Scientists typically start being exposed to Data Engineering on the job. There's much to be gained from early exposure to concepts and practices in this field;
-
sharpen technical skills not only in fitting models, but particularly in building knowledge and generating insights from the data. While this may seem obvious for a Data Scientist, it is not always the focus of training,
-
train in working effectively in teams to build projects and products. Data Science is collaborative in nature and constantly evolving in best practices that enhance efficient collaboration. Collaboration for school projects/assignments is vastly different from the highly-structured collaboration that happens in DS teams, but is not always the focus of training, and
-
enhance soft skills that are key to a successful interaction with business stakeholders. The most important - and often neglected - activity of a data scientist is to obtain expert knowledge from and communicate with non-technical audiences. The greatest insight/project/product is moot if no one outside the Data Science team understands it or its value.
All of these are highly valued skills in the Data Science job market, but not always considered explicitly as part of an integral Data Science curriculum.
It is assumed that students have basic to intermediate knowledge of object-oriented programming - e.g R or Python - including experience using it for data manipulation, visualizations, and model estimation. Some mathematics, statistics and algebra are also assumed.
There are no required textbooks for this course. The course will rely on a combination of curated reading materials, recorded lectures, live video-conferencing weekly sessions, in-class workshops and take-home exercises that will leverage the following tools:
- Canvas
- Zoom
- Flipgrid
- GitHub / GitHub classroom
- Slack
- AWS Educate
- Databricks
Registered students will receive instructions through Canvas to access to the weekly Zoom session, Flipgrid, GitHub classroom, Slack, AWS Educate, and Databricks.
Make sure to have the latest versions of R/RStudio, and/or Anaconda, as well as git installed on your computer. Sign up for a GitHub account if you don't have one already. Atom is recommended to simplify your interaction with git and GitHub.
-
install git in your local machine
-
from the command line, got to the directory where you want to clone this repo
$ cd <dir>
-
clone
this repository to get a local copy in your machine$ git clone https://github.com/marco-morales/QMSS-GR5069_Spring2021.git
-
pull
every week before class to sync your local copy with the changes pushed to the remote repo$ git pull origin master
-
subscribe to the repository to get notifications each time new changes are pushed to the repository