Communications & Office Hours#
Warning
Due to Dept Seminar Office hours on 11/10 will be at 5pm instead of 4pm.
Announcements#
Announcements will be made via GitHub Release. You can view them online in the releases page or you can get notifications by watching the repository, choosing “Releases” under custom see GitHub docs for instructions with screenshots. You can choose GitHub only or e-mail notificaiton from the notification settings page
Help Hours#
| Day | Time | Location | Host |
|---|---|---|---|
| Monday | 12pm-2pm | Zoom | Mark |
| Monday | 4-5pm | Zoom | Dr. Brown |
| Friday | 4-5pm | 134 Tyler | Dr. Brown |
Zoom links are on the course organization page of GitHub
To reach out, By usage#
We have several different ways to communicate in this course. This section summarizes them
| usage | platform | area | note |
|---|---|---|---|
| in class | prismia | chat | outside of class time this is not monitored closely |
| any time | prismia | download transcript | use after class to get preliminary notes eg if you miss a class |
| private questions to your assignment | github | issue on assignment repo | eg bugs in your code" |
| for general questions that can help others | github | issue on course website | eg what the instructions of an assignment mean or questions about the syllabus |
| to share resources or ask general questions in a semi-private forum | github | discussion on community repo | include links in your portfolio |
| matters that don't fit into another category | to brownsarahm@uri.edu | remember to include `[CSC310]` or `[DSP310]` (note `verbatim` no space) |
Note
e-mail is last because it’s not collaborative; other platforms allow us (Proessor + TA) to collaborate on who responds to things more easily.
Tips#
For assignment help#
send in advance, leave time for a response I check e-mail/github a small number of times per day, during work hours, almost exclusively. You might see me post to this site, post to BrightSpace, or comment on your assignments outside of my normal working hours, but I will not reliably see emails that arrive during those hours. This means that it is important to start assignments early.
Using issues#
use issues for content directly related to assignments. If you push your code to the repository and then open an issue, I can see your code and your question at the same time and download it to run it if I need to debug it
use issues for questions about this syllabus or class notes. At the top right there’s a GitHub logo that allows you to open a issue (for a question) or suggest an edit (eg if you think there’s a typo or you find an additional helpful resource related to something)
For E-email#
use e-mail for general inquiries or notifications
Please include
[CSC310]or[DSP310]in the subject line of your email along with the topic of your message. This is important, because your messages are important, but I also get a lot of e-mail. Consider these a cheat code to my inbox: I have setup a filter that will flag your e-mail if you use one of those in the subject to ensure that I see it.