Looking for someone to talk to about CSE332? Try the Study Center in CSE room 006! There's a table there just for working on and discussing CSE332!
In Person lectures will be held in Gates Center (i.e. CSE2) room G20 at 12:30pm-1:20pm
Lecture attendance is optional, but strongly encouraged. In the event you are unable to attend a lecture, recordings of lectures are automatically posted to Canvas under the Panopto tool.
| Instructor | TAs | |
|---|---|---|
| Name | Nathan Brunelle | Profiles |
| Location | Allen Center (CSE) 434 | See Calendar |
| Office Hours | MWF 1:30-3:00 | See Calendar |
| Phone | (none) | |
| brunelle@cs.washington.edu | use Ed Discussion Board |
For communication about course content, the Ed Discussion Board is preferred to email. For communication about personal circumstances, email or is preferred. If you email, include either CSE 332
, 332
, or Data Structures
in the subject line to prevent your email from skipping my inbox and never getting read.
Our TAs are students too, with duties and work outside of their TAing. Please do not ask them to act as your TA except at the scheduled on-the-clock times they have listed as their office hours. They are also kind people; please don’t put them in the position of having to say no or (worse) being nice to you at the expense of their own schooling.
(Optional) Data Structures and Algorithm Analysis in Java 3rd Ed., Mark Allen Weiss, Addison Wesley: 2012, ISBN-10: 0132576279. Our course calendar will list sections of the textbook that are most relevant to the topic discussed in class that day. You may find the textbook useful to clarify topics and find more examples as well as to examine Java implementations of the data structures and algorithms discussed during lecture. We will not be assigning problems from the textbook. We will use a set of free on-line notes for the material on parallelism and concurrency.
I do my best to make lectures as valuable, engaging, and enlightening as possible for all students. For a schedule of lecture topics, please see the course webpage. Although we believe nearly all students will benefit from attending all classes, we also respect that as mature (ideally) college students, you are entrusted to figure out how best to learn and make use of your time here. Hence, I will not have any in-class activities which impact your grade with the exception of the already-posted in-class exams (midterm and final). I will make a best effort to post all lecture materials (recordings, slides documents, etc.) on the course webpage, including video recordings of lectures. Be advised that there are occasional technical difficulties which sometimes cause the recordings to fail, and even when they do succeed these recordings may not be an adequate substitute for attending class live.
All assignments will be posted and submitted either in class (for exams) or on Gradescope. All grading will be conducted on Gradescope. You will be asked to perform three kinds of evaluations:
We will consider the grade assigned by the following weighted average to be a guideline for calculating grades.
| Task | Weight | Comments |
|---|---|---|
| Exercises | 25% | There will be about 13 total, the lowest 3 will be dropped. |
| Programming Projects | 35% | There will be 3 total |
| Exams | 40% | Midterm weighted 15%, Final weighted 25% |
This numerical calculation is to be considered a guideline on your score in the course. Final grades may take other factors into account so that your grade is the most accurate reflection of your understanding of course materials.
We will keep track of any extra features you implement for programming projects (the Above and Beyond
parts). You won’t see these affecting your grades for individual projects, but they will be accumulated over all projects and used to bump up borderline grades at the end of the quarter. The bottom line is that these will only have a small effect on your overall grade, most notably a much smaller effect that the required portions of the assignments. For this reason, I suggest that you consider the extra credit to be purely extra, i.e. do not do extra credit in lieu of required work in this class or any of your other classes.
Exercises may not be turned in late. (Although when calculating final grades, we will drop your lowest two exercise scores.)
You are allotted four late days that may be used to gain an extra 24 hours for a programming project (or checkpoint). If you have used up your late days, a penalty of 10% per day will be assessed. Programming projects will not be accepted beyond 48 hours from the original due date.
We acknowledge that professors and TAs are people (glad to get that confession off of my chest!), and people make mistakes. For this reason, you are able to request regrades on assignments within either one week of your grade being returned or by 11:59pm on Dec 12, which ever date is sooner.
Please only submit a regrade request if you believe the rubric was misapplied to your submission or if there was a keying error for the task. In the case of a misapplication of the rubric, identify specifically what in your submission demonstrates the misapplication and suggest how you believe the rubric should be correctly applied. In the case of a keying error, state and justify why you believe your answer should be considered correct. Disagreement with the existance or weighting of a rubric item is not considered a valid reason for a regrade request.
Behave professionally.
Never abuse anyone, including the emotional abuse of blaming others for your mistakes. Kindness is more important than correctness.
Let our TAs be students when they are not on the clock as TAs.
Lack of professionalism has an overall detrimental impact on our community of learning.
I always hope everyone will behave honestly. I know we all are sometimes tempted by the easy path that dishonesty can enable; if you do something you regret, the sooner you tell me the sooner (and more leniently) we can correct it.
For Exercises and Programming Projects you may use external materials with the following restrictions:
stuck.
I collaborated with Brett Wortzman on the implementation of the peek method, I consulted for help with java print syntax, Miya Natsuhara helped me to debug the for loop that begins on line 107 of my code.
whiteboard only(defined below).
hintsor entire solutions to the problems. Limit your searching to background information only. (For example, do not consult a GitHub repository posted by a former student.)
Whiteboard Only
collaboration is meant to convey the type of discussion where participants gather around a whiteboard to solve a problem together, without taking any notes from their discussion, and then erasing the whiteboard before they disperse.
In particular, you may discuss tasks and their solutions, but the only thing you may take away from your discussion is your brain. This means you may not produce any records or artifacts from your collaborations, including: notes, screenshots, photos, figures, code, audio/video recordings, documents (inluding google docs), links, or any other digital or tangible thing. Nor may you share any files, links, etc. with other students outside of a collaboration session. Any substantially similar expression of the same solution can only occur if collaboration extends beyond whiteboard only
, and so will be considered as evidence of a policy violation.
The University of Washington strives to provide accessibility to all students. If you require an accommodation to fully access this course, please work with the Disability Resources for Students (DRS). If you are unsure if you require an accommodation, or to learn more about their services, begin by visiting the DRS website. For this course, we ask that students with special circumstances let us know as soon as possible, preferably during the first week of class or as soon as accomodations are approved.
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 Religious Accommodations Policy. Accommodations must be requested within the first two weeks of this course using the Religious Accommodations Request form.
I am dedicated to providing a safe and equitable learning enironment for all students. To that end, it is vital that you know two values that I hold as critically important:
If you or someone you know has been affected by power-based personal violence, I encourage you to use Safecampus as a resource. As your professor and a human, know that I care about you and your well-being and stand ready to provide support and resources to the best of my ability.
Additionally, if at any point you are made to feel uncomfortable, disrespected, or excluded by a staff member or fellow student, please report the incident so that we may address the issue and maintain a supportive and inclusive learning environment. Should you feel uncomfortable bringing up an issue with a me or another staff member directly, you may consider contacting the Office of the Ombud.
Bad things happen. People forget things and make mistakes. Bad days coincide with due dates. Etc.
If you believe that circumstances warrant a change in deadline, a second chance, or some other accommodation in order to more accurately synchronize grade with knowledge, come talk to me and we’ll resolve the situation as best we can.
If you are feeling overwhelmed, stressed, or isolated, there are many individuals here who are ready and wanting to help. The University of Washington Counseling Center offers short-term counseling students and crisis service for urgent situations. Call 206-543-1240 (or 866-427-4747 for after hours and weekend crisis assistance) to get started and schedule an appointment.