Editing Community Data Science Course (Spring 2023)
From CommunityData
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 4: | Line 4: | ||
:'''Instructors:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu] and [https://kayleachampion.com/ Kaylea Champion] / she / [mailto:kaylea@uw.edu kaylea@uw.edu] (TA: you can call me Kaylea) | :'''Instructors:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu] and [https://kayleachampion.com/ Kaylea Champion] / she / [mailto:kaylea@uw.edu kaylea@uw.edu] (TA: you can call me Kaylea) | ||
:'''Course Website''': We will use Canvas for [https://canvas.uw.edu/courses/1633288/assignments assignments] and [https://canvas.uw.edu/courses/1633288/announcements announcements]. Everything else will be linked on this page. | :'''Course Website''': We will use Canvas for [https://canvas.uw.edu/courses/1633288/assignments assignments] and [https://canvas.uw.edu/courses/1633288/announcements announcements]. Everything else will be linked on this page. | ||
:'''Course Playlist''': [https://open.spotify.com/playlist/4iM6wz4GYRX7O2S7Z2oyXj?si= | :'''Course Playlist''': [https://open.spotify.com/playlist/4iM6wz4GYRX7O2S7Z2oyXj?si=61e66a02b303488b&pt=ba5cc2809c1035b38d22753143c0fb67 Feel free to add what's moving you lately] | ||
:Course Catalog Description (from '''Communication Leadership):''' | :Course Catalog Description (from '''Communication Leadership):''' | ||
Line 52: | Line 52: | ||
* If you need access to a computer, please reach out to me as soon as possible. The Department has laptops you can borrow for the course, but it's important to have that laptop in the first week. | * If you need access to a computer, please reach out to me as soon as possible. The Department has laptops you can borrow for the course, but it's important to have that laptop in the first week. | ||
== Staying in Touch == | == Staying in Touch {{tbd}} == | ||
The | The teaching team is still working out details on how we're going to stay in touch outside of class and what the best ways to reach us will be. We are committed to building some sort of chat system. The most likely situation is that we'll use a Discord server for this purpose but we'll confirm this at the first class. | ||
== Assignments == | == Assignments == | ||
Line 81: | Line 62: | ||
=== Weekly Coding Challenges === | === Weekly Coding Challenges === | ||
:'''Due Date:''' Sundays at 11:59 p.m. on most weeks | :'''Due Date:''' Sundays at 11:59 p.m. on most weeks | ||
:'''Turning in:''' | :'''Turning in:''' {{tbd}} | ||
Most weeks I will give you all a set of weekly coding challenges before the end of class that will involve changing or adding to code that I've given you as part of the projects in the final parts of class to solve new problems. We expect you to make substantial progress on your weekly assignment each week and we expect that many or most of you will have (mostly) working solutions or at least some code code for every single problem. These coding challenges will be turned in but will not be graded on effort, not on full correctness. They will be graded as ''complete/incomplete''. | Most weeks I will give you all a set of weekly coding challenges before the end of class that will involve changing or adding to code that I've given you as part of the projects in the final parts of class to solve new problems. We expect you to make substantial progress on your weekly assignment each week and we expect that many or most of you will have (mostly) working solutions or at least some code code for every single problem. These coding challenges will be turned in but will not be graded on effort, not on full correctness. They will be graded as ''complete/incomplete''. | ||
Line 96: | Line 77: | ||
:'''Maximum Length:''' 600 words (~2 pages double spaced) | :'''Maximum Length:''' 600 words (~2 pages double spaced) | ||
:'''Due Date:''' Week 3 (April 10) | :'''Due Date:''' Week 3 (April 10) | ||
:'''Turning in:''' Turn in PDF in | :'''Turning in:''' Turn in PDF in [https://canvas.uw.edu/courses/1633288/assignments/8231677 the Canvas dropbox] | ||
In this assignment, you should identify an area of interest, at least one sources of relevant data, and at least 3-4 questions that you plan to explore. We will discuss appropriate data sources for your project in the first and second week of the course. I am hoping that each of you will pick an area that you are intellectually committed to and invested in (e.g., in your business or personal life). You will be successful if you describe the scope of the problem and explain why you think the data sources you've identified are relevant. | In this assignment, you should identify an area of interest, at least one sources of relevant data, and at least 3-4 questions that you plan to explore. We will discuss appropriate data sources for your project in the first and second week of the course. I am hoping that each of you will pick an area that you are intellectually committed to and invested in (e.g., in your business or personal life). You will be successful if you describe the scope of the problem and explain why you think the data sources you've identified are relevant. | ||
Line 115: | Line 96: | ||
Your proposal should frame your final analysis, but it's also a chance to "sanity check" your plan. I will give you feedback on these proposals and suggest changes or modifications that are more likely to make them successful or compelling. I will also work with you to make sure that you have the resources and support necessary to carry out your project successfully. | Your proposal should frame your final analysis, but it's also a chance to "sanity check" your plan. I will give you feedback on these proposals and suggest changes or modifications that are more likely to make them successful or compelling. I will also work with you to make sure that you have the resources and support necessary to carry out your project successfully. | ||
Be as specific as possible about the data available on the sources you've chosen. I expect that you will have written at least some of the final code that you will use in this course. | Be as specific as possible about the data available on the sources you've chosen. I expect that you will have written at least some of the final code that you will use in this course. Identify the documentation and the API endpoints where required. If there are libraries that you think may help with access, note them. | ||
=== Final Project === | === Final Project === | ||
Line 123: | Line 102: | ||
For your final project, I expect you to build on the first two assignments to describe what they have done and what you have found. I'll expect every student to give both: | For your final project, I expect you to build on the first two assignments to describe what they have done and what you have found. I'll expect every student to give both: | ||
# A short presentation ( | # A short presentation (7 minutes) | ||
# A final report that is not more than 4500 words (~18 pages) | # A final report that is not more than 4500 words (~18 pages) | ||
Line 132: | Line 111: | ||
==== Final Presentation ==== | ==== Final Presentation ==== | ||
:'''Presentation Date:''' At some point during the beginning of the last week of the quarter (the week of May 29). Details will be {{forthcoming}}. | |||
:'''Turning in:''' Details are {{tentative}} but we will very likely ask you upload a video to Canvas and will provide information and links on how to do this. | |||
Your presentation should provide the teaching team and your classmates with a very clear idea of what to expect in your final paper. However, don't treat it as a comprehensive overview of your paper: I would rather you tell a subset of the story well than the whole story in a rushed fashion. For instance, you can give a completely successful presentation by describing the motivation and walking through one plot in your paper. I'm going to give you all at least a paragraph of feedback after your talk. This will be an opportunity for me to see a preview of your paper and give you a sense for what I think you can improve. It's to your advantage to both give a compelling talk and to give me a sense for your project. | |||
The current plan is: | |||
;Length: All presentations will need to be '''a maximum of | ;Length: All presentations will need to be '''a maximum of 7 minutes long'''. Do not exceed 7 minutes and 0 seconds; don't edit your video to speed it up if you go too long. Concisely communicating an idea in the time allotted is an important skill in its own right. | ||
;Slides: You are encouraged to use slides for your talk. Please keep in mind that your slides are meant to be additive, not a teleprompter. | ;Slides: You are encouraged to use slides for your talk. Please keep in mind that your slides are meant to be additive, not a teleprompter. | ||
; | ;Modality: We will not meet during the final week due to the Memorial Day holiday. As a result, we plan to conduct these virtually. | ||
==== Final Paper (and Code!) ==== | ==== Final Paper (and Code!) ==== | ||
:'''Due Date:''' Thursday June 8 at 11:59 p.m. | :'''Due Date:''' Thursday June 8 at 11:59 p.m. | ||
:'''Turning in:''' Turn in a PDF of your paper to [https://canvas.uw.edu/courses/1633288/assignments/8231894 the Canvas dropbox]; | :'''Turning in:''' Turn in a PDF of your paper to [https://canvas.uw.edu/courses/1633288/assignments/8231894 the Canvas dropbox]; Details on how to turn in your code will be {{forthcoming}}. | ||
Your final project should include detailed information on: | Your final project should include detailed information on: | ||
Line 177: | Line 141: | ||
Keep in mind that most stories on Five Thirty Eight are under 1000 words and I'm giving up to 4,500 words to show me what you've learned. As a result, you should do ''more'' than FiveThirtyEight does in a single story. You can ask and answer more questions, you can provide more background, context, and justification, you can provide more details on your methods and data sources, you can show us more graphs, you can discuss the implications of your findings more. Use the space I've given you to show off what you've done and what you've learned! | Keep in mind that most stories on Five Thirty Eight are under 1000 words and I'm giving up to 4,500 words to show me what you've learned. As a result, you should do ''more'' than FiveThirtyEight does in a single story. You can ask and answer more questions, you can provide more background, context, and justification, you can provide more details on your methods and data sources, you can show us more graphs, you can discuss the implications of your findings more. Use the space I've given you to show off what you've done and what you've learned! | ||
Finally, you should also share with me the full Python source code you used to collect the data as well as the data set itself. Your code | Finally, you should also share with me the full Python source code you used to collect the data as well as the data set itself. Your code along will not form a large portion of your final grade. Rather, I will focus on the degree to which you have been successful at answering the ''substantive'' questions you have identified. | ||
Visualization is critical to storytelling, so 25% of your grade for this project will be determined by the visualizations and tables in your report. Good visualizations should "stand alone" and motivate the core results in your paper all by themselves. A good question to keep in mind is "could I tell this story with the visualizations and a tweet?" | Visualization is critical to storytelling, so 25% of your grade for this project will be determined by the visualizations and tables in your report. Good visualizations should "stand alone" and motivate the core results in your paper all by themselves. A good question to keep in mind is "could I tell this story with the visualizations and a tweet?" | ||
Line 186: | Line 150: | ||
Nearly every week, we will begin by discussing challenges and problem sets that we'll define as a group at the end of the previous class. Please speak up and engage in this part of the class as well as asking questions anytime there is anything confusing. If you are feel confused about a new Python concept, it's highly unlikely that you are the only one. If there is anything I can do to help you participate in class, please let me know in the anonymous feedback. | Nearly every week, we will begin by discussing challenges and problem sets that we'll define as a group at the end of the previous class. Please speak up and engage in this part of the class as well as asking questions anytime there is anything confusing. If you are feel confused about a new Python concept, it's highly unlikely that you are the only one. If there is anything I can do to help you participate in class, please let me know in the anonymous feedback. | ||
In general, my teaching style is more conversational than a formal lecture. I prefer that students feel they can "politely interrupt" at any time to seek clarification or make a well-informed point. | |||
== Grades == | == Grades == | ||
Assignments will accrue to your final grade in the following way: | Assignments will accrue to your final grade in the following way: | ||
* 10% will be class participation including attendance, participation in discussions, and group work | * 10% will be class participation including attendance, participation in discussions, and group work | ||
* 30% significant effort towards weekly | * 30% significant effort towards weekly assignments | ||
* 5% will be the Final Project Idea | * 5% will be the Final Project Idea | ||
* 10% will be the Final Project Proposal | * 10% will be the Final Project Proposal | ||
Line 202: | Line 166: | ||
== Schedule == | == Schedule == | ||
{{notice|This section will be modified throughout the course to introduce the week's material | {{notice|This section will be modified throughout the course to introduce the week's material and any hand-ins.}} | ||
=== Week 1: March 27 === | === Week 1: March 27 === | ||
Line 215: | Line 179: | ||
** We'll introduce the teaching team. | ** We'll introduce the teaching team. | ||
** We'll discuss an example of a successful final project from a previous version of the class. | ** We'll discuss an example of a successful final project from a previous version of the class. | ||
* [[/Week 1 Exercise]] — You'll install software including the Python programming language and run through a series of exercises. | * [[/Week 1 Exercise]] — You'll install software including the Python programming language and run through a series of exercises. ('''This is still under construction so please don't start yet!''') | ||
* Introduce [[/Week 1 coding challenges]] | * Introduce [[/Week 1 coding challenges]] | ||
'''By the end of class you will:''' | '''By the end of class you will:''' | ||
* Have a working Python environment on your personal laptop. | * Have a working Python environment on your personal laptop. | ||
* Have a GitHub account for turning in your coding challenges. | * Have a GitHub account for turning in your coding challenges. | ||
Line 227: | Line 190: | ||
* Have learned a few basics about programming in Python including variables and lists. | * Have learned a few basics about programming in Python including variables and lists. | ||
* Be ready to start on Week 1 coding challenges. If all goes well, you'll start on them! | * Be ready to start on Week 1 coding challenges. If all goes well, you'll start on them! | ||
=== Week 2: April 3 === | === Week 2: April 3 === | ||
Today we'll be doing a crash course | Today we'll be doing a crash course is basic programming in Python. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* Read chapters 2 and 3 of ''Python for Everyone'': | |||
** Chapter 2, Variables | |||
** Chapter 3, Conditionals | |||
* Complete the Code Academy assignment from class last week | |||
* Finish and turn in your [[/Week 1 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 1 coding challenges]] (Due Sunday before class) | ||
'''Class schedule:''' | '''Class schedule:''' | ||
* Answer any questions that folks have about the final projects. | |||
* Answer any questions that folks have about the final projects | * Review material from last week: variables, assignment, if statements | ||
* Review answers to last week's coding challenges | * Review answers to last week's coding challenges | ||
* [[/Week 2 lecture]] <!-- [[Community_Data_Science_Course_%28Spring_2019%29/Day_2_Lecture|Lecture notes]] --> introducing new material including loops and lists | |||
* [[/Week 2 lecture notes]] | * Introduce the [[/Week 2 coding challenges]] <!-- [[Community Data Science Course (Spring 2019)/Day 3 Coding Challenges|Day 3 Coding Challenges]] --> | ||
* Introduce the [[/Week 2 coding challenges]] and the | * Project time — We'll begin working on [[Wordplay]] and the [[/Week 2 coding challenges]] independently or in small groups. | ||
'''By the end of class you will:''' | '''By the end of class you will:''' | ||
* Have a better understanding of the expectations for your final project, | * Have written your first program with loops and lists. | ||
* Have a better understanding of the expectations for your final project, and be ready to hand in your initial assignment. | |||
=== Week 3: April 10 === | === Week 3: April 10 === | ||
Today we'll be doing introducing some additional programming concepts in Python including aggregating and counting with dictionaries | Today we'll be doing introducing some additional programming concepts in Python including aggregating and counting with dictionaries. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* [[#Final Project Idea|Final project idea]] (Due at 5pm on Monday, | * [[#Final Project Idea|Final project idea]] (Due at 5pm on Monday) | ||
* Read chapter 4, 5 of ''Python for Everyone'': {{tentative}} | |||
** Functions (this is mostly new) | |||
** Iteration (this is mostly review) | |||
** Dictionaries {{tbd}} | |||
* Finish and turn in your [[/Week 2 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 2 coding challenges]] (Due Sunday before class) | ||
'''Class schedule:''' | '''Class schedule:''' | ||
* Go over last week's assignments | * Go over last week's assignments | ||
* [[/Week 3 lecture notes]] introducing new material on dictionaries and aggregations plus average, | * [[/Week 3 lecture]] <!-- [[Community_Data_Science_Course_%28Spring_2019%29/Day_2_Lecture|Lecture notes]] --> introducing new material on dictionaries and aggregations plus average, median (using the Wordplay data) | ||
* | * A break | ||
* Introduce the [[/Week 3 coding challenges]] based on the [ | * Introduce the [[/Week 3 coding challenges]] based on the [http://mako.cc/teaching/2015/cdsw-autumn/babynames.zip Baby names] project. <!-- [[Community Data Science Course (Spring 2019)/Day 3 Coding Challenges|Day 3 Coding Challenges]] --> | ||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
'''Resources:''' | |||
* [[Python data types cheat sheet]] A cheat sheet with everything we've covered in class so far including today. | * [[Python data types cheat sheet]] A cheat sheet with everything we've covered in class so far including today. | ||
<!-- '''By the end of class you will:''' | |||
* Have written your first program with loops and lists. | |||
* Have a better understanding of the expectations for your final project, and be ready to hand in your initial assignment. | |||
--> | --> | ||
Line 315: | Line 250: | ||
=== Week 4: April 17 === | === Week 4: April 17 === | ||
Today we'll be learning | Today we'll be using Python to read and write files from disk and be learning to do some basic tricks with a very useful Python module called Pandas. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* Read chapters 8 and 10 of '''Python for Informatics''': | |||
** Dictionaries | |||
** Files | |||
* Finish and turn in your [[/Week 3 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 3 coding challenges]] (Due Sunday before class) | ||
'''Class schedule:''' | '''Class schedule:''' | ||
* Go over the [[/Week 3 coding challenges]] | * Go over the [[/Week 3 coding challenges]] | ||
* [[/Week 4 lecture | * [[/Week 4 lecture]] introducing new material, plus building some basic histograms in Python. | ||
* Introduce the [[/Week 4 coding challenges]] | * Introduce the [[/Week 4 coding challenges]], which will also be based on the [http://mako.cc/teaching/2015/cdsw-autumn/babynames.zip Baby names] project. | ||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
<!-- * [[/Day 4 coding challenges]] [[Community Data Science Course (Spring 2019)/Day 4 Coding Challenges|Day 4 Coding Challenges]] --> | |||
=== Week 5: April 24 === | === Week 5: April 24 === | ||
Today we'll be | Today we'll be learning about the basic of web APIs and JSON. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* Readings {{tbd}} | |||
* Finish and turn in your [[/Week 4 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 4 coding challenges]] (Due Sunday before class) | ||
'''Class schedule:''' | '''Class schedule:''' | ||
* Go over the [[/Week 4 coding challenges]] | * Go over the [[/Week 4 coding challenges]] and review some histograms | ||
* [[/Week 5 lecture | * [[/Week 5 lecture]] introducing new material on APIs and JSON <!-- [[Community Data Science Course (Spring 2019)/Day 5 Notes|Day 5 Notes]] --> | ||
* Introduce the [[/Week 5 coding challenges]] | * Introduce the [[/Week 5 coding challenges]] <!-- [[Community Data Science Course (Spring 2019)/Day 5 Coding Challenges|Day 5 Coding Challenges]] --> | ||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
=== Week 6: May 1 === | === Week 6: May 1 === | ||
Today we'll be putting everything together and walking through a project that builds a dataset from the Wikipedia API from start-to-finish, with a focus on cleaning and getting data into tools like Excel or Google Sheets, and introducing a set of tricks along the way. | Today we'll be putting everything together and walking through a project that builds a dataset from the Wikipedia API from start-to-finish, with a focus on cleaning and getting data into tools like Excel or Google Sheets, and introducing a set of tricks along the way. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* Readings {{tbd}} | |||
* Finish and turn in your [[/Week 5 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 5 coding challenges]] (Due Sunday before class) | ||
Line 396: | Line 298: | ||
* Let's discuss remaining schedule | * Let's discuss remaining schedule | ||
* Go over the [[/Week 5 coding challenges]] | * Go over the [[/Week 5 coding challenges]] | ||
* [[/Week 6 lecture | * [[/Week 6 lecture]] introducing new material on APIs and JSON <!-- [[Community Data Science Course (Spring 2019)/Day 5 Notes|Day 5 Notes]] --><!-- [[Community Data Science Course (Sprint 2019)/Day 7 Notes|Day 7 Notes]] --> | ||
* Introduce the [[/Week 6 coding challenges]] | * Introduce the [[/Week 6 coding challenges]] <!-- [[Community Data Science Course (Spring 2019)/Day 7 Coding Challenges|Day 7 Coding Challenges]] --> | ||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
<!-- | <!-- | ||
Line 410: | Line 312: | ||
=== Week 7: May 8 === | === Week 7: May 8 === | ||
Today we'll | Today we'll be introducing two additional web APIs in parallel. We'll run a poll of the class to get a sense of what folks want to learn but we're considering Yelp, Reddit, Twitter, and data.seattle.gov. | ||
' | |||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* Readings {{tbd}} | |||
* Finish and turn in your [[/Week 6 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 6 coding challenges]] (Due Sunday before class) | ||
Line 429: | Line 322: | ||
* Go over the [[/Week 6 coding challenges]] | * Go over the [[/Week 6 coding challenges]] | ||
* [[/Week 7 lecture | * [[/Week 7 lecture]] introducing new material on new APIs | ||
* Introduce the [[/Week 7 coding challenges]] | * Introduce the [[/Week 7 coding challenges]] | ||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
Line 435: | Line 328: | ||
=== Week 8: May 15 === | === Week 8: May 15 === | ||
We'll | Today we'll be introducing two additional web APIs in parallel. We'll run a poll of the class to get a sense of what folks want to learn but we're considering Yelp, Reddit, Twitter, and data.seattle.gov. | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* [[#Final Project Proposal]] | * [[#Final Project Proposal]] | ||
* Readings {{tbd}} | |||
* Finish and turn in your [[/Week 7 coding challenges]] (Due Sunday before class) | * Finish and turn in your [[/Week 7 coding challenges]] (Due Sunday before class) | ||
Line 457: | Line 340: | ||
* Let's discuss remaining schedule | * Let's discuss remaining schedule | ||
* Go over the [[/Week 7 coding challenges]] | * Go over the [[/Week 7 coding challenges]] | ||
* | * [[/Week 8 lecture]] | ||
* Introduce the [[/Week 8 coding challenges]] | |||
* Project time—We'll work through projects | * Project time—We'll work through projects | ||
Line 466: | Line 350: | ||
'''Assignment Due:''' | '''Assignment Due:''' | ||
* | * Readings {{tbd}} | ||
* Finish and turn in your [[/Week 8 coding challenges]] (Due Sunday before class) | |||
'''Class schedule:''' | '''Class schedule:''' | ||
* Project time—We'll | * Let's discuss remaining schedule | ||
* | * Go over the [[/Week 8 coding challenges]] | ||
* [[/Week 9 lecture]] | |||
* Project time—We'll work through projects | |||
'''Resources:''' | |||
* Visualization dos and don'ts. We'll discuss the European Environmental Agency's [https://www.eea.europa.eu/data-and-maps/daviz/learn-more/chart-dos-and-donts list of advice for making charts]. **I will refer to this guide as a grade your final projects.** | |||
* Two options for remainder of class. You can work through this introductory guide to visualization in python or you can work on your final project. I'll be here to answer any questions. | |||
* Self-guided visualization tutorial in python. [https://raw.githubusercontent.com/guyrt/teaching/master/2019/Com520B/VisualizationNotebook.ipynb Download here]. Save the file in a new directory in your desktop and open it with Jupyter Notebook. (If you are on Windows, you may run into an issue with missing path variables. [https://stackoverflow.com/questions/52821162/jupyter-notebook-failed-to-load-dll This SO post helped me solve it.]) | |||
=== Week 10: May 29 (NO MEETING) === | === Week 10: May 29 (NO MEETING) === | ||
Line 506: | Line 399: | ||
'''Except during these parts of class — which — I ask that you refrain from using your laptops, tablets, phones, and pretty much any (digital) device with a screen.''' | '''Except during these parts of class — which — I ask that you refrain from using your laptops, tablets, phones, and pretty much any (digital) device with a screen.''' | ||
--> | --> | ||
=== Office Hours === | |||
{{tbd}} | |||
<!-- The best way to get in touch with me about issues in class will in the Discord server via asychronous messages sent to one of the text channels. This is preferable because any questions you have can be answered in a way that is visible to others in the class. | |||
I will hold synchronous, in-person, office hours once a week: | |||
:'''Thursdays 3:30-4:30pm''' in the '''Office Hours''' voice channel on Discord. | |||
If my planned office hours do not work for you, please contact me in the Discord server or over email to arrange a meeting at another time. | |||
--> | |||
=== Religious Accommodations === | === Religious Accommodations === | ||