Resources
Useful Documents
- Course Syllabus
- Code Clarity, Design, and Testing Guide
- Pyret Editor (CPO) Guide
- Pyret Table Documentation
Where to Get Various Kinds of Help
| Problem | Ed | Debugging Hours (SignMeUp) |
Conceptual Hours |
Professor Hours or Appt |
|---|---|---|---|---|
| Fix/Debug Code | small issue | larger issue | ||
| Understand Error Message | yes | yes | yes | yes |
| Conceptual Question | yes | yes | yes | |
| Review Study Skills | yes | yes | ||
| Questions on Drills | yes | yes | yes | |
| Private Issue | appt (email them) |
Labs (required) run each week to practice programming material.
In general, we strongly encourage you to use Ed for small/quick questions. You can post code to Ed in private posts. If you feel you need to post a lot of code, your question is probably better suited to face-to-face SignMeUp office hours (schedule is in the calendar). We have a good-size team of TAs handling Ed in the hopes of getting answers to you quickly.
If you have a clarification question, we prefer you to make a public post (can be anonymous) on Ed. If we feel a private question is of general interest, we may turn it into an anonymous public post, so more people can see the answers.
Milda and Kathi’s office hours will be open, not one-on-one. This means you are welcome to join the session anytime and ask questions or discuss material (whether from class, homework, or CS in general). These hours are not meant for helping individual students with code.
If you feel you need individual help with how you approach problems in general, make an appointment with Milda or Kathi. Also make an appt with Milda or Kathi if you have a concerns of a personal nature.
Preparing-for-One-on-one-Office-Hours
You have only 15 minutes for one-on-one appointments, so being prepared is important (and it keeps the line moving for other students).
In class, we will be learning a design process in which you write your code after written other artifacts (such as behavior examples or task plans, which we will teach during the class). These other artifacts are critical to figuring out where you are actually stuck on a problem. We therefore expect you to show these artifacts to your TA when you come in for debugging hours, unless your question is not about figuring out why your code isn't working.
Having you learn design skills is one of the goals of this course (we're not here just to show you how to produce code). This policy supports this goal.
We’ll talk about design steps in lecture throughout weeks 2-4 of the course.
Department Resources
- Diversity and Inclusion
- Student Advocates for Diversity and Inclusion
- Women in Computer Science
- MOSAIC+
Health and Wellness
If you need accommodation for your physical and mental health, please feel free to reach out to Kathi or Milda - we want to support you as much as we can in the most comfortable way for you. It is important to note that TAs should not be handling health and accomodations information, so inquiries should be directed towards Kathi or Milda only.
Please check out the following links for resources on physical and mental health in Computer Science.