Policy on Collaboration (for DC1 and beyond)
I would like to more actively encourage collaboration in class - especially informal collaboration. This is especially tricky in the remote setting, since some of the best mechanisms for informal collaboration (meeting before after class, running into people in the halls, …) aren’t happening.
There is always a tricky tensions between academic conduct and collaboration. For this class, I want to make the policies encourage collaboration: I trust students to be honest and not abuse collaboration. Collaboration is so valuable, and fragile, that I want to encourage it.
This posting will clarify policies that should help you understand that collaboration is acceptable, and give you some suggestions to encourage it.
Short version: I encourage you to find ways to talk to your classmates to discuss class things (including providing feedback on DC drafts).
Collaboration Policy
Students are still subject to the Academic Conduct and Misconduct policies. Unless explicitly specified, all work must be done independently. When you turn something in, it should be your work.
However, it is acceptable to discuss the class with other students (unless you are explicitly asked not to). With some caveats:
You should not appropriate someone else’s work as your own, and your assignments should be substantially your own creation. If you feel like someone made a contribution to your work, giving them attribution is appropriate. (e.g. “I got the idea to try a tree map because I saw it in Julie’s.” or “Jane provided a critique of a draft of this design and really helped me.” or “I got the idea from this feature from the public example from last year’s project.”)
Collaboration should involve explicit consent in both directions. You should not look at someone else’s work without their permission, and you shouldn’t show someone your work unless they want to see it. For example, don’t broadcast your design because someone might want to figure out the solution on their own (and not want to see yours until they do).
It is better to err on the side of disclosing collaboration.
You are ultimately responsible for the work you turn in. If your classmate gives you bad advice (and you choose to follow it), it is still your assignment.
If you are in doubt, ask the course staff.
Some Examples:
It is acceptable (encouraged) for you to provide critique / constructive criticism for a classmates’ designs (for example, for Design Challenge 1). You shouldn’t copy their designs.
It is acceptable (encouraged) for you to ask a classmate to review your code with you, or talk through your logic when you are trying to find a bug. You should not ask them to write your programs for you.
It is acceptable (encouraged) for you to ask or give advice on tools or ideas.
It is acceptable (encouraged) for you to work with a reading/study group to go over the readings or review the class materials. But, ultimately, everyone must write their own assignments.
Fostering Collaboration
In person, class (and being around the department in general) builds connections between students for collaboration. I don’t know how to re-create this, but some example ideas:
Use Piazza to find people to talk to. Organize a meet-up to critique each others’ designs.
If you do plan something, invite others. Again, you can use Piazza to announce “some of us are getting together to talk about X”.
While you shouldn’t post your design to Piazza (see caveat 2 above), you can ask if anyone is willing to have a discussion.
Posting to ask “does someone have a few minutes to help me work through a bug” may actually get a response. We’ve all had the “I wish I had someone here to help” feeling, and may be willing to “pay it forward” because next time it might be us asking.
I am really curious if people are able to find things that work. So, please (1) experiment, and (2) let me know what works (and doesn’t). The risk of annoying people on Piazza is worth the potential of building a more collaborative class.