Editing DUB Seminar (Spring 2022)

<div style="float:right;" class="toclimit-3">__TOC__</div>

:'''Design, Use, Build Seminar''' ('''HCID 590 A''')
:'''Instructor:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu]
:'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") You can view out [https://mako.cc/calendar/ my calendar] and/or [https://harmonizely.com/mako put yourself on it].  If you schedule a meeting, we'll meet in the Jitsi room (<code>makooffice</code>) you'll get a link to through the scheduling app.
:'''Meeting Times:''' Wednesday 12-1pm and several other 90-minute sessions (see [[#Class Schedule|the class schedule below]])
:'''Important Links''':
:* We will use [https://canvas.uw.edu/courses/1547772 Canvas] for [https://canvas.uw.edu/courses/1547772/announcements announcements] and [https://canvas.uw.edu/courses/1547772/assignments assignments] and for giving you grades and feedback
:* We will use [https://app.slack.com/client/T054LSQ4F/C02FVPE4SSY our own Slack Channel] (<code>mhcid590-dub-seminar</code> on the [https://uwdub.slack.com DUB slack] for asynchronous group chat to discuss assignments and talks, ask questions, and share information throughout the week.
:* [https://dub.washington.edu/seminar.html DUB Seminar website] with the calendar, links to information about speakers, etc

== Overview and Learning Objectives ==

[[File:DUB logo.png|500px]]

[https://dub.washington.edu Design, Use, Build group (DUB)] is a grassroots alliance of faculty, students, researchers, and industry partners interested in Human Computer Interaction & Design at the University of Washington. DUB brings together people across a range of departments at the University of Washington, gets HCI folks at UW out of their departmental silos, and exposes them to new ideas and perspectives.

DUB exists primarily in three places: the annual DUB retreat in the fall, small group activities organized 3-6 times throughout the year, and the DUB seminar. For more than 15 years, the DUB seminar has brought some of the leading researchers working at the intersections of people and computing to UW and has provided a venue for HCI researchers at UW to get their work in front of colleagues in other departments. It remains one of the best and easiest ways to connect with the broader HCI community at UW.

I am going to approach HCID 590 as one class stretched out across the year. This means that although the core of the class—the seminar itself—will remain the same, the learning goals will shift a little  each quarter. It also means that the assignments and activities may change so that they we can all build upon what we have learned.

== Spring 2022 Edition ==

In addition to the core learning goal related to '''building up an ability to understand and draw lessons from academic material about HCI''',  the fall quarter was focused on developing your skill in '''developing questions about academic material''' while the winter quarter was designed around '''develoing and communiacting an informed POV'''.  This quarter will be focused on '''applying ideas from academic HCI research to your own work'''.

I will consider this quarter a total success if the following happens:

* Everyone attends the weekly DUB seminars, listens actively, and takes excellent notes.
* Everyone participates thoughtfully and consistently in discussions about the work presented at seminars over the quarter, both synchronously and asynchronously.
* Everyone is able to thoughtfully identify ideas from the talks we see and describe how they might shape their own work.

== Class Schedule ==

=== Seminars ===

The DUB seminar will be hosted from 12-1pm on Wednesdays and (for this quarter once again) will conducted entirely over Zoom. I've listed the planned talks here and linked them on the calendar in Canvas. I don't schedule the DUB seminar and I know things sometimes change over the quarter. The latest version of the calendar will always be [https://dub.washington.edu/seminar.html on the DUB seminar webpage] and changes will be announced on the [https://dub.washington.edu/gettinginvolved.html#tab_mailing_lists_and_slack DUB mailing lists].

'''You must signup for the DUB mailing list to get the Zoom link for the seminar each week.'''

# Wednesday April 6: Charlotte Lee (UW HCDE)
# Wednesday April 13: Nazanin Andalibi (University of Michigan)
# Wednesday April 20: Nicola Dell (Cornell Tech)
# Wednesday April 27: Danielle Olson-Getzen (Apple Research)
# Wednesday May 11: Elaine Schaertl Short (Tufts University)
# Wednesday May 18: Marcelo Worsley (Northwestern University)
# Wednesday May 25: Sean Follmer (Stanford University)

We're skipping May 4th because nothing has been scheduled during that period because it will coincide with the ''ACM Conference on Human-Factors in Computing'' (CHI) which is the largest academic conference on computing.

You'll also notice that there will be small group mixers on [https://dub.washington.edu/seminars/2022-06-01.html June 1]. Although you're not required to attend these, I encourage you to attend these because they are low key, lots of fun, and provide great opportunities to connect with folks working on related stuff at UW. You can follow the links above for more information.

=== Facilitated Group Discussions ===

You are expected to attend the three facilitated group discussion events. These will be at:
 
# Tuesday April 19th from 3:30–5pm (in person in Alumni House classroom)
# Tuesday May 10th from 3:30–5pm (in person in Alumni House classroom)
# Tuesday May 24th from 3:30–5pm (in person in Alumni House classroom)

== Assignments ==

For each week that we have a DUB seminar, all of the assignments are build around a set of one-on-one pair discussions with another member of your	cohort. To help these conversations happen, I'll be randomly pairing folks up with one of their classmates. I'll be posting a list of the pairings for the week on Slack on Wednesday afternoon ''after'' each seminar.

Your assignment involves the following three things:

# Formulate three questions ''for other members of your cohort'' based on the talk. [Individual Deliverable] 
# Share your questions, and talk through one or more of them, with your conversation partner for the week.
# Report back to the group on Slack. [Pair Deliverable]

You are welcome to structure your pair conversation in whatever way makes sense. It can be an in-person discussion, a chat over coffee or lunch, or a short video call in Slack or Zoom. It can also be an asynchronous text chat in a set of private messages on Slack. Do whatever works for you!

I'm imagining that you will spend about half an hour talking through things in a synchronous discussion or some equivalent amount of idea development in a text chat over hours or even days.

=== Questions DUE Thursday at 9pm [Individual Deliverable] ===

Your individual deliverables are the three questions that you will pose to your partner. They will be due in [https://canvas.uw.edu/courses/1547772/discussion_topics the appropriate Canvas discussion] where others can see them the day after each talk. This will be similar to what we did in the Autumn quarter, but without the sketch noting and without the need to frame questions for three different audiences.

=== Reports from Pair Discussion DUE Sunday at 5pm [Group Deliverable] ===

Each group will have two deliverables which will be due at time that due at 5pm on the Sunday after each seminar:

# A short summary of your conversation (shoot for about 200 words).
# Nominate one question (either you brought to the session or one developed up in your conversation) for the facilitated conversation in the full group discussion. Ideally this will be a question that you and your partner believe will provide an illuminating discussion and/or elicit productive disagreement from your classmates.

Each week, '''one member of each pair should do one of these things and the other member should do the other.''' You're welcome to divide this up however you like but do make sure that everybody does some of each over the quarter.

Please complete both of these assignments in Slack in the following way:

# When posting summaries, please just post this as a normal message into Slack (i.e., start a new thread). Of course, be sure to both indicate that this is a reportback and mention the name of your conversation partner!
# For questions, let's try to keep these together under a single thread in Slack. I'll try to pin a message for these questions each week but go ahead and start the thread if I haven't gotten to it first and I'll pin it when I see it.

=== Vote on others' questions DUE Monday at 5pm ===
There is one final assignment:

<ol start=3>
<li>In the period between #2 above is done/due and ''before 5pm on the Monday before we have our facilitated group discussion'', look through the group discussion questions threads in the weeks since our last full group dicussion and nominate any question you are interested in for further discussion. Thumbs-up (:+1:) reactions are a totally fine way to do this!</li>
</ol>

== Grading and Assessment ==

This course is offered credit/no credit. Although you will not receive a numeric grade, passing this class is not automatic and I will assess your work and evidence of learning throughout the quarter. You can find details about my approach to assessment and my very detailed grading rubric on [[User:Benjamin Mako Hill/Assessment|my assessment page]]. Although I don't expect this to be a problem, you'll need to have credit for at least 2/3 of the assignments in the class in order to get credit for the class:

I will assign points for each of following items according to the weights below:

* Weekly Questions: 20%
* Weekly Pair Discussions: 50%
* Facilitated group discussion: 30%

== Administrative Notes ==

=== Dealing with Paywalls ===

As part of this class, you'll be linked to academic articles on a regular basis. Many of these articles are behind paywalls in the sense that you will often be asked to pay for access to the full text. Whatever you do, '''don't pay for the articles!''' UW has already paid for them which means that you have already paid for the, in small part, as part of your tuition!

Although you can often do a web search and find a "preprint" (usually an earlier version of the article available online for free), UW libraries have bought subscriptions to everything (or almost everything) we'll be talking about in this class. As a result, my recommendation is to get the real version from the publisher.

If you're on campus, the paywall will simply not appear because the UW libraries subscription covers free access from on campus. If you're off campus, you should visit [https://www.lib.washington.edu/help/connect the UW libraries page about off-campus access]. That page will direct to you to one of two options: (a) [https://www.lib.washington.edu/help/connect/tools the UW libraries bookmarklet] or (b) use the [https://itconnect.uw.edu/connect/uw-networks/about-husky-onnet/ Husky OnNet VPN] with the “All Internet Traffic” option selected.

Option (a) (the bookmarklet) is a little unusual but it's very easy and it involve adding "button" to your web browser that will "unlock" just about any paywall article you go to. I use it many times every day.

=== Teaching and learning in a pandemic ===

The COVID-19 pandemic will impact this course in various ways, some of them obvious and tangible and others harder to pin down. On the obvious and tangible front, we have things like a mix of remote, synchronous, and asynchronous instruction. These will reshape our collective "classroom" experience in major ways. 

On the "harder to pin down" side, many of us may experience elevated levels of exhaustion, stress, uncertainty and distraction. We may need to provide unexpected support to family, friends, or others in our communities. I have personally experienced all of these things at various times over the pandemic and I expect that some of you have too. It is a difficult time.

I believe it is important to acknowledge these realities of the situation and create the space to discuss and process them in the context of our class throughout the quarter. As your instructor and colleague, I commit to do my best to approach the course in an adaptive, generous, and empathetic way. I will try to be transparent and direct with you throughout—both with respect to the course material as well as the pandemic and the university's evolving response to it. I ask that you try to extend a similar attitude towards everyone in the course. When you have questions, feedback, or concerns, please try to share them in an appropriate way. If you require accommodations of any kind at any time (directly related to the pandemic or not), please contact the teaching team.

:<div style="font-size: 80%; font-style: italic">This text is borrowed and adapted from [[Statistics and Statistical Programming (Fall 2020)|Aaron Shaw's statistics course]].</div>

=== Your Presence in Class ===

As detailed in [[User:Benjamin Mako Hill/Assessment|my detailed page on assessment]], your participation in discussion is an important way that I will assess learning. Obviously, you must be in class in order to participate. If you need to miss the seminar itself, contact me and we can make sure you get a copy of a video. In the event of an absence, you are responsible for obtaining notes, handouts, assignments, etc. 

=== Religious Accommodations ===

Washington state law requires that UW develop a policy for accommodation of student absences or significant hardship due to reasons of faith or conscience, or for organized religious activities. The UW’s policy, including more information about how to request an accommodation, is available at [https://registrar.washington.edu/staffandfaculty/religious-accommodations-policy/ Religious Accommodations Policy]. Accommodations must be requested within the first two weeks of this course using the [https://registrar.washington.edu/students/religious-accommodations-request/ Religious Accommodations Request form].

=== Student Conduct ===

The University of Washington Student Conduct Code (WAC 478-121) defines prohibited academic and behavioral conduct and describes how the University holds students accountable as they pursue their academic goals. Allegations of misconduct by students may be referred to the appropriate campus office for investigation and resolution. More information can be found online at https://www.washington.edu/studentconduct/
Safety

Call SafeCampus at 206-685-7233 anytime–no matter where you work or study–to anonymously discuss safety and well-being concerns for yourself or others. SafeCampus’s team of caring professionals will provide individualized support, while discussing short- and long-term solutions and connecting you with additional resources when requested.

=== Academic Dishonesty ===

This includes: cheating on assignments, plagiarizing (misrepresenting work by another author as your own, paraphrasing or quoting sources without acknowledging the original author, or using information from the internet without proper citation), and submitting the same or similar paper to meet the requirements of more than one course without instructor approval. Academic dishonesty in any part of this course is grounds for failure and further disciplinary action. The first incident of plagiarism will result in the student’s receiving a zero on the plagiarized assignment. The second incident of plagiarism will result in the student’s receiving a zero in the class.

=== Disability Resources ===

If you have already established accommodations with Disability Resources for Students (DRS), please communicate your approved accommodations to uw at your earliest convenience so we can discuss your needs in this course.

If you have not yet established services through DRS, but have a temporary health condition or permanent disability that requires accommodations (conditions include but not limited to; mental health, attention-related, learning, vision, hearing, physical or health impacts), you are welcome to contact DRS at 206-543-8924 or uwdrs@uw.edu or disability.uw.edu. DRS offers resources and coordinates reasonable accommodations for students with disabilities and/or temporary health conditions. Reasonable accommodations are established through an interactive process between you, your instructor(s) and DRS. It is the policy and practice of the University of Washington to create inclusive and accessible learning environments consistent with federal and state law.

=== Other Student Support ===

Any student who has difficulty affording groceries or accessing sufficient food to eat every day, or who lacks a safe and stable place to live, and believes this may affect their performance in the course, is urged to contact the graduate program advisor for support. Furthermore, please notify the professors if you are comfortable in doing so. This will enable us to provide any resources that we may possess (adapted from Sara Goldrick-Rab). Please also note the student food pantry, Any Hungry Husky at the ECC.

== Credit and Notes ==

Much of the design of this class and some text on the syllabus are drawn from previous version of the course taught at UW. In particular, I've drawn from the syllabus created by [https://runjumpandfly.com/ Scott Ichikawa's] Autumn 2020 syllabus for HCID 590 .