Editing Data Into Insights (Spring 2021)
From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
:'''Instructor:''' [https://jeremydfoote.com Jeremy Foote] | :'''Instructor:''' [https://jeremydfoote.com Jeremy Foote] | ||
:'''Email:''' jdfoote@purdue.edu | :'''Email:''' jdfoote@purdue.edu | ||
:''' | :'''Office Hours:''' Fridays 10am-noon and by appointment | ||
<div style="float:right;">__TOC__</div> | <div style="float:right;">__TOC__</div> | ||
Line 37: | Line 37: | ||
* Other readings: Readings will be linked to from this page. Where necessary, they will be put on Brightspace | * Other readings: Readings will be linked to from this page. Where necessary, they will be put on Brightspace | ||
= Course logistics = | = Course logistics = | ||
Line 56: | Line 52: | ||
This course will follow "flipped" classroom model. I expect you to learn most of the content of the course asynchronously. The goal of our time together is not to tell you new things, but to consolidate knowledge and to clear up misconceptions. | This course will follow "flipped" classroom model. I expect you to learn most of the content of the course asynchronously. The goal of our time together is not to tell you new things, but to consolidate knowledge and to clear up misconceptions. | ||
The Tuesday meeting will be a collaborative, discussion-centric session. Typically, about half of each session will be devoted to going over assignments and the other half will be a discussion of the readings and videos from that week | The Tuesday meeting will be a collaborative, discussion-centric session. Typically, about half of each session will be devoted to going over assignments and the other half will be a discussion of the readings and videos from that week. | ||
The Thursday meetings will be more like a lab. Some of these sessions will include synchronous activities but they will often be more of a co-working time, where you can work synchronously on assignments and I can be available to answer questions. | The Thursday meetings will be more like a lab. Some of these sessions will include synchronous activities but they will often be more of a co-working time, where you can work synchronously on assignments and I can be available to answer questions. | ||
Line 66: | Line 60: | ||
Your first place to look for help should be each other. By asking and answering questions on Discord, you will not only help to build a repository of shared information, but to reinforce our learning community. | Your first place to look for help should be each other. By asking and answering questions on Discord, you will not only help to build a repository of shared information, but to reinforce our learning community. | ||
I will also hold office hours Friday mornings on Discord ([[ | I will also hold office hours Friday mornings on Discord ([[JFoote Office Hours|Sign up here]]). If you come with a programming question, I will expect that you have already tried to solve it yourself in multiple ways and that you have discussed it with a classmate (e.g., on Discord). This policy lets me have time to help more students, but it's also a useful strategy. Often [https://en.wikipedia.org/wiki/Rubber_duck_debugging just trying to explain your code] can help you to recognize where you've gone wrong. | ||
I will also keep an eye on Discord during normal business hours. I encourage you to post questions there, and to use it as a space where we can help and instruct each other. In general, you should contact me there. I am also available by email. You can reach me at [mailto:jdfoote@purdue.edu jdfoote@purdue.edu]. I try hard to maintain a boundary between work and home and I typically respond only on weekdays during business hours. | I will also keep an eye on Discord during normal business hours. I encourage you to post questions there, and to use it as a space where we can help and instruct each other. In general, you should contact me there. I am also available by email. You can reach me at [mailto:jdfoote@purdue.edu jdfoote@purdue.edu]. I try hard to maintain a boundary between work and home and I typically respond only on weekdays during business hours. | ||
Line 221: | Line 215: | ||
* Effective Data Storytelling (EDS) Ch. 1--3 ([https://purdue-primo-prod.hosted.exlibrisgroup.com/permalink/f/vjfldl/PURDUE_ALMA51860241510001081 Purdue libraries copy]) | * Effective Data Storytelling (EDS) Ch. 1--3 ([https://purdue-primo-prod.hosted.exlibrisgroup.com/permalink/f/vjfldl/PURDUE_ALMA51860241510001081 Purdue libraries copy]) | ||
* Matei, S. [https://purdue.brightspace.com/d2l/le/content/208726/viewContent/4750659/View What is a (data) story?] | * Matei, S. [https://purdue.brightspace.com/d2l/le/content/208726/viewContent/4750659/View What is a (data) story?] | ||
* | * Levy, J. (2015). [https://www-tandfonline-com.ezproxy.lib.purdue.edu/doi/full/10.1080/09636412.2015.1070602 Counterfactuals, Causal Inference, and Historical Analysis] | ||
* (Optional) [https://towardsdatascience.com/storytelling-for-data-scientists-317c2723aa31 Storytelling for Data Scientists] | * (Optional) [https://towardsdatascience.com/storytelling-for-data-scientists-317c2723aa31 Storytelling for Data Scientists] | ||
* (Optional) [https://towardsdatascience.com/how-to-properly-tell-a-story-with-data-and-common-pitfalls-to-avoid-317d8817e0c9 How to properly tell a story with data — and common pitfalls to avoid] | * (Optional) [https://towardsdatascience.com/how-to-properly-tell-a-story-with-data-and-common-pitfalls-to-avoid-317d8817e0c9 How to properly tell a story with data — and common pitfalls to avoid] |