Editing Intro to Programming and Data Science (Spring 2020) (section)

= Course logistics =

== Note About This Syllabus ==

This is a brand new course and this syllabus will be a dynamic document. Although the core expectations for this class are fixed, the details of readings and assignments may shift based on how the class goes. As a result, there are three important things to keep in mind:

# Although details on this syllabus will change, I will not change readings or assignments less than one week before they are due. If I don't fill in a "''To Be Determined''" one week before it's due, it is dropped. If you plan to read more than one week ahead, contact me first.
# Closely monitor your email. Because this a wiki, you will be able to track every change by clicking the ''history'' button on this page. I will also summarize these changes in an announcement that will be emailed to everybody in the class.
# I will ask the class for voluntary anonymous feedback frequently. Please let me know what is working and what can be improved.

== Office hours and email ==

* I will hold office hours Thursday afternoons and by appointment. 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 at least two classmates. 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 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 (~9-5) but during the week I will generally respond within 24 hours.