Community Guidelines

Our department is dedicated to fostering a warm, encouraging, and supportive student community. For many people, learning a new subject can be accompanied by some feelings of uncertainty, anxiety, or even intimidation. We want everyone to know that these feelings are completely natural, and we will work together to make the class and lab an inviting place to learn and grow. These guidelines are on top of Oberlin’s Code of Conduct.

Remember!

  • Everyone is welcome here! Yes, including you!
  • You have a right to your own education! If you have a question, it’s very likely someone else has the same question. No question is ‘stupid’
  • Everyone is coming into this class with different experiences. Most of the class won’t have ever programmed before, so if you have experience, think back to when you were new to programming and be kind in your interactions.
  • Be patient with yourself and others. Learning to code takes time and practice. Mistakes are a natural part of the process, and everyone progresses at their own pace.
  • Don’t forget to celebrate progress: No matter how small, every step forward is a victory. Celebrate your own wins and cheer on your classmates!
  • Be mindful of the words you use when explaining concepts or interacting with others. Inclusive language can make a big difference in making everyone feel like they belong.
  • Don’t hesitate to ask your peers or the instructor for help, and when you’re comfortable, help others when they ask.

Social Rules

  • No feigning surprise: Try to avoid acting shocked when someone doesn’t know something. E.G. “You don’t know who Spiderman is? Have you been living under a rock?”.
  • No well-actuallys: A well-actually happens when someone says something that’s almost - but not entirely - correct, and you say, “well, actually…” and then give a minor correction. This can be very disruptive when the correction has no bearing on the crux of the conversation.
  • No back-seat driving: If you hear someone else who is not a part of your group working through a problem, you shouldn’t give advice unless you are actively participating in their conversation.
  • No subtle -isms: Subtle -isms are small things that make others feel unwelcome, things that we all sometimes do by mistake. These can include but are not limited to: racism, transphobia, homophobia, sexism as well as other kinds of bias.
  • Do to others as you would want done to you: Try to consider how your words would impact you. Would you want someone questioning your right to be in this classroom? No one deserves to feel unwelcome.
  • Respect different learning styles: People absorb information in different ways. Some might need more time or prefer different explanations, so be adaptable and understanding.
  • Avoid interrupting: Let others finish their thoughts before jumping in, especially during group discussions.
  • Assume good intentions: If someone says something you find confusing or off-putting, try to approach the situation with curiosity and kindness rather than judgment.
  • Keep it constructive: When giving feedback or correcting a mistake, focus on being helpful and supportive rather than critical.

ReadMe

A reminder about the Honor Code in CSCI 150: The Warmup is intended to be done with a classmate during the lab section period, and then everything after that (Part 1, Part 2, etc.) is individual work. While you are encouraged to form study groups and discuss the labs in general terms with classmates, you should never copy anyone’s code, and no one else should ever have a copy of your code. The only people who are allowed to look at your code directly are the course instructors, lab helpers hired by the CSCI department, and tutors hired by the AARC. If you do discuss the lab with someone else or look up resources online, please write that you did so in the README file within your repository.

As is outlined in the syllabus, AI use is also forbidden in CSCI 150.

(These guidelines were developed from the established rules by the Recurse Center.)