5387 Computer Sciences
5394 Computer Sciences
FINALS WEEK: Tue 9am – 11am
|Office Hours: Tue 10:00am – noon, Wed 2:30pm – 4:30pm, or by appt.|
TuTh 9:30AM – 10:45AM
TuTh 1:00PM – 2:15PM
MWF 1:20PM – 2:10PM
MWF 9:55AM – 10:45AM
Consultants (Teaching and Lab Assistants):
- Getting Started:
- What are the goals of the problem?
- What are the inputs?
- What are the outputs?
- What is their relationship?
- Can you solve a small example by hand?
- Is there a part of the problem you could write code for? (and worry about the rest later?)
- Can you describe the algorithm in words?
- Compiling Code
- What line is the syntax error on?
- What does the text of the error mean?
- Can you simplify your code to eliminate this problem and confirm its precise location?
- Getting Code to Function
- What evidence do you have that the code doesn’t work?
- What test case doesn’t work and what incorrect behavior or output results?
- Could you come up with a simpler example that demonstrates the error?
- What lines of code might be producing the bug?
- Why hypotheses do you have for what might be causing the problem?
- How can you test these hypotheses? (e.g. writing new test cases, adding print statements, using a debugger)
- Could you walk through an example that doesn’t work: by hand? with a debugger?
(Derived from CS Teaching Tips)
The consultants are available to help you with CS302. They are students who also help conduct lab sections. During regularly scheduled consulting hours the consultants will be on duty in 1350 CS or 1370 CS. Each consultant wears a name tag and, if working at one of the computers, will have a sign on their computer. Please feel free to ask consultants for help even when they’re working at a computer.
- Finding documentation within the course website about course policies (please use piazza or contact faculty members directly about any policy concerns that are not addressed on the website).
- Finding documentation within the course website about assignment specifications (please use piazza to ask for clarifications about what is required for assignments).
- Interpreting compile-time errors in your programs, such as incorrect braces and missing semicolons.
- Identifying steps to troubleshoot run-time errors, such as those resulting from the misuse of the logical operators, loops, or input statements.
- Finding documentation within the course website about the CS302 style and commenting standards (please use piazza to ask for clarification about what is required in these standards).
- Resolving basic issues with installing Eclipse or Java on your laptop computer.
- Resolving issues with lab computers such as: How do I print my file? Where are my printouts? How do I check my email? Where’s the web browser?
Note: Consultants are NOT expected to fix or write your code for you. They are available to assist you in identifying strategies to test you own assumptions and debug code that you are otherwise struggling with. Please do NOT ask them to ensure that you code works correctly, that is your job. Consultants are not personal tutors and often will need to help other students. They’ll try to help as many students as possible, and may direct you to complete a particular task before providing you with further assistance.
CS Learning Center
- Sunday: 2-5pm
- Monday: 3-6pm
- Tuesday: 3-6pm
- Wednesday: 3-9pm
The Computer Sciences Learning Center (CSLC) is located in the lobby of the CS building (1210 W Dayton) above the entrance facing Union South. There are tables, comfy chairs, and lots of bright, open space for you to work.
Drop-in tutoring will be available Sunday-Thursday, 6:30 – 9 PM, Tong Auditorium 1003 Engineering Centers Building. Offered by the College of Engineering’s Undergraduate Learning Center.