Editing DUB Seminar (Fall 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 4: Line 4:
:'''Instructor:''' [https://mako.cc/academic/ Benjamin Mako Hill] / [mailto:makohill@uw.edu makohill@uw.edu]
:'''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.
:'''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-1:20pm and three Mondays 3:30-5pm (see [[#Class Schedule|the class schedule below]])
:'''Meeting Times:''' Mondays 12-1pm and three Mondays 3:30-5pm (see [[#Class Schedule|the class schedule below]])
:'''Important Links''':
:'''Important Links''':
:* We will use Canvas for [https://canvas.uw.edu/courses/1479641/announcements announcements]
:* We will use Canvas for [https://canvas.uw.edu/courses/1479641/announcements announcements]
:* 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.
:* 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 readings, 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
:* [https://dub.washington.edu/seminar.html DUB Seminar website] with the calendar, links to information about speakers, etc


Line 14: Line 14:
[[File:DUB logo.png|500px]]
[[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.
[https://dub.washington.edu DUB] is a grassroots alliance of faculty, students, researchers, and industry partners interested in Human Computer Interaction & Design at the University of Washington.  


DUB exists primarily in three places: the annual DUB retreat, 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.
Design, Use, Build group (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 parimarily in three places: the annual DUB retreat, small group activities organized several 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 UW community.


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.
I am going to approach HCID 590 as one slow-burn class stretched out across the year. That means that there won't be a final exam at the end of the quarter. It also means that each quarter the learning goals will shift. It also means that the assignments and activities may change so that they we can all build upon what we have learned. The first quarter of DUB, will be an opportunity for you to learn about the DUB community, practice formulating questions, and reflecting on what you have heard.  
 
I'm approach ''this quarter'' (#1) as an opportunity for you to learn about the DUB community, practice formulating questions, and reflecting on what you have heard.  
   
   
I will consider this quarter a total success if the following happens:
I will consider this quarter a success if following happens:


* Everyone attends the weekly DUB seminars, listens actively, and takes excellent notes.
* Everyone attends in 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 participates thoughtfully and consistently in discussions about the work presented at seminars over the quarter, both synchronously and asynchronously.
* Everyone is able to routinely form thoughtful questions about the academic work presented that would be appropriate to academic speakers, your classmates, and folks in industry.
* Everyone is able to routinely form thoughtful questions about the academic work presented that would be appropriate to academic speakers, your classmates, and industry.


== Class Schedule ==
== Class Schedule ==
Line 32: Line 30:
=== Seminars ===
=== Seminars ===


The DUB seminar will be hosted from 12-1pm on Wednesdays and (for this quarter at least) 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].
The DUB seminar will be hosted from 12-1pm on Wednesdays and (AFAIK) 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 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.'''
''''You must signup for the DUB mailing list to get the Zoom link for the seminar each week.''''


# Wednesday October 6: Marshini Chetty (University of Chicago)
# Wednesday October 6: Marshini Chetty (University of Chicago)
Line 44: Line 42:
# Wednesday December 1 Martez Mott (Microsoft Research)
# Wednesday December 1 Martez Mott (Microsoft Research)


You'll notice that we're skipping October 13 because we'll all be attending the DUB retreat that week and November 26 because it is the day before Thanksgiving. There will be no seminar either week. You'll also notice that there will be small group mixers on both [https://dub.washington.edu/seminars/2021-09-29.html September 29] and [https://dub.washington.edu/seminars/2021-12-08.html December 8th]. Although you're not required to attend these, I strongly 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.
You'll notice that we're skipping October 13 because we'll all be attending the DUB retreat that day and November 26 because it is the day before Thanksgiving. You'll also notice that there will be small group mixers on both [https://dub.washington.edu/seminars/2021-09-29.html September 29] and [https://dub.washington.edu/seminars/2021-12-08.html December 8th]. Although you're not required to attend these, I strongly 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.


=== Class Group Discussions ===
=== Class Group Discussions ===
Line 56: Line 54:
== Assignments ==
== Assignments ==


For each week that we have a DUB seminar, I'm asking folks to do at do two things each week.
=== Responses: Visual Notes & Questions; Class Discussions ===


=== Post visual notes and questions [Due each Thursday following seminar @ 9pm ] ===
For each week that we have a DUB seminar, your assignment will be to participate in a Canvas discussion. I'm asking folks to do at do two things:


By 9pm on Friday following a talk, please post to the relevant place in the [https://canvas.uw.edu/courses/1479641/discussion_topics Canvas discussion forum] with the following two things:
==== Post visual notes and a question [Due each Thursday @ 9pm following seminar] ====


;(1) A visual note capturing a single idea from the presentation: You are welcome to reflect on how the talk fits into the design challenges that you are currently addressing, highlight a research methods that you can use in the context of your projects or capture your key takeaway. Please do not try to visualize the whole presentation within your one visual note! The best notes will focus on one key point.  
By 9pm on Friday following a talk, please post a message to the [FIXME Canvas discussion forum]] I'll create for each week with the following items:
 
;(1) A visual note capturing a single idea from the presentation: You are welcome to reflect on how the talk fits into the design challenges that you are currently addressing, highlight a research methods that you can use in the context of your projects or capture your key takeaway. Please do not try to visualize the whole presentation within your one visual note! The best notes can focus on one key point.  


I'm actually pretty new to visual note-taking myself but I'm not a particularly great at drawing. I know that both experience and skills will vary quite a lot across the group so don't feel bad if you're new to this too. I found these videos pretty useful:
I'm actually pretty new to visual note-taking myself but I'm not a particularly great at drawing. I know that both experience and skills will vary quite a lot across the group so don't feel bad if you're new to this too. I found these videos pretty useful:
Line 78: Line 78:
I am asking you all to turn these in using a Canvas discussion because I want you all to be able to see each others notes and questions. I am ''not'' expecting that you will be responding to each other on Canvas. In fact, I strongly recommend that if you've got a good question for the cohort, you copy-and-paste that question into Slack in ways that are described below.
I am asking you all to turn these in using a Canvas discussion because I want you all to be able to see each others notes and questions. I am ''not'' expecting that you will be responding to each other on Canvas. In fact, I strongly recommend that if you've got a good question for the cohort, you copy-and-paste that question into Slack in ways that are described below.


[[File:Canvas insert image menu.png|thumb]]
==== Discussion on Slack [Due Monday @ 3:30pm following seminar] ====
 
When you turn these in on Canvas, please attach your image with the ''Insert → Image → Upload Image'' menu as shown in this image. This will make is to that it's easier for your classmates to browse all the sketchnotes that folks are uploading.
 
=== Discussion on Slack [Due Monday following seminar @ 3:30pm] ===


I am expecting that everybody will spend 30 minutes each week discussing each seminar on Slack, roughly split between reading others messages and posting your own thoughtful responses.
I am expecting that everybody will spend 30 minutes discussing each seminar on Slack and I expect that everyone will spend 10-15 minutes reading others messages and about 15-20 minutes writing out their own thoughtful responses.


A simple starting point will be to simply pose your question for the cohort in the slack itself! If you don't feel the desire to share your question or if there are already an interesting set of question posted, you can spend time answering others.
A simple starting point will be to simply pose your question for the cohort in the slack itself! If you don't feel the desire to share your question, you can spend time answering others.


For the purposes of tracking participation, I am logging our Slack channel and will generate statistics each week of who has participated and when/how much they posted. I don't have a target word count that I'm looking for and I definitely understand that sometimes a thoughtful short message may reflect a bunch of research. That said, I do expect that (a) everybody will post every week, and (b) the posts will be substantial enough to suggest something in the range of 15-20 minutes of thoughtful effort.
For the purposes of tracking participation, I have written a program that is logging our Slack channel and all threads that occur within it and I will use the system to keep track of each time anybody in the class posts and whether and how much they post when they do so. I don't have a target word count that I'm looking for and I understand that sometimes a thoughtful short message may reflect a bunch of research. That said, I do expect that (a) everybody will post every week, and (b) the posts will be substantial enough to suggest something in the range of 15-20 minutes of thoughtful effort. If you're just phoning it in, I'll be able to see that.


== Grading and Assessment ==
== 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]].
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 participation 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]]. Please read it carefully. I will assign points for each of following items according to the weights below:
 
I will assign points for each of following items according to the weights below:


* Asynchronous discussion on Slack: 40%
* Asynchronous discussion on Slack: 40%
Line 101: Line 95:


== Administrative Notes ==
== 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 ===
=== Teaching and learning in a pandemic ===
Line 124: Line 108:
=== Your Presence in Class ===
=== 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. <!--<strike>If you need to miss class for any reason, please fill out the [https://forms.gle/KSDJiptVwusBWw4BA course absence form] so that we know you are not coming and do not include you in our cold call list.</strike>--> In the event of an absence, you are responsible for obtaining notes, handouts, assignments, etc.  
As detailed in [[#Case discussion|section on case studies]] and 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. <!--<strike>If you need to miss class for any reason, please fill out the [https://forms.gle/KSDJiptVwusBWw4BA course absence form] so that we know you are not coming and do not include you in our cold call list.</strike>--> In the event of an absence, you are responsible for obtaining notes, handouts, assignments, etc.  


<!-- There are many students who have eagerly requested to join the class, but there are not enough seats. I want to include as many students in the class as possible, we will automatically drop anyone who misses the first two class sessions and try to replace them with unenrolled students who do attend. This is consistent with college policy and with the course description in the catalog.
<!-- There are many students who have eagerly requested to join the class, but there are not enough seats. I want to include as many students in the class as possible, we will automatically drop anyone who misses the first two class sessions and try to replace them with unenrolled students who do attend. This is consistent with college policy and with the course description in the catalog.
Line 136: Line 120:


'''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 ===
 
The best way to get in touch with me about issues in class will in the DUB Slack server via messages sent directly to me. 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 as described above. If my planned office hours do not work for you, please contact me to arrange a meeting at another time.


=== Religious Accommodations ===
=== Religious Accommodations ===
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)