seattle_chicago_ds_051120

Welcome to the Flatiron Data Science Bootcamp. We are so excited to lead you through this expansive journey. We will update this repo with links to your lecture and warmup material.

Cohort Link - Chicago

This is a zoom meeting space for your corhort to use. Consider this your virtual table :)

Cohort Link - Seattle

This is a zoom meeting space for your corhort to use. Consider this your virtual table :)

Calendar (Central Time)

Calendar (Pacific Time)

chi_sea_ds
├── module_1/ 
│   ├── week_1/ 
│   ├── week_2/ 
│   └── week_3/ 
├── module_2/ 
│   ├── week_4/ 
│   ├── week_5/ 
│   └── week_6/ 
├── module_3/ 
│   ├── week_7/ 
│   ├── week_8/ 
│   └── week_9/ 
├── module_4/ 
│   ├── week_10/    
│   ├── week_11/ 
│   └── week_12/ 
└── module_5/ 
    ├── week_13/ 
    ├── week_14/ 
    └── week_15/

How you want to interact with the repositories is also up to you, but we suggest to fork each repo onto your personal github account, then clone the forked version onto your local computer. Once you have cloned the fork, you may want to set the upstream remote to the original.

$ git remote add upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git

Once you have run the above command, run:

git remote -v

You should see two remotes, the origin pointing towards your forked repo, and an upstream pointing towards the original.

origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (fetch)
origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (push)
upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (pull)

This way, you can make changes to the notebooks on your local computer, then push your changes to your fork.

Quick note: When creating your repo structure, do not initialize or clone reposistories within folders that are themselves git repos.

Module 1, Week 1