CS21 — Intro. to Computer Science
Succeeding | Style | Accommodations | Integrity | Links
Introduction
Welcome to CS21! This course will introduce fundamental ideas in computer science while also teaching you how to write computer programs. We will study algorithms for solving problems and implement solutions in the Python programming language. Python is an interpreted language that is known for its ease of use. We also introduce object-oriented programming and data structures. A deeper coverage of these topics will be presented in CS35.
This course is appropriate for all students who want to learn how to write computer programs and think like computer scientists. It is the usual first course for computer science majors and minors. Students with advanced placement credit or extensive programming experience should place out of this course and instead begin with CS35. If you have no prior computer science or programming experience, this course is designed for you.
Goals for the Course
By the end of the course, we hope that you will have developed the following skills:
- Given a problem, be able to design a clear, concise, and correct pseudo code algorithm to solve it.
- Be able to use top-down design to sub-divide a large problem into reasonably-sized modular sub-problems.
- Given several algorithms for solving the same problem, be able to analyze which algorithm would be more efficient in terms of running time.
- Given a program, be able to simulate on paper how a computer would execute the program, and show the results that would be produced.
- Given a pseudo code algorithm, be able to successfully implement it in Python.
- Develop debugging and unit testing skills. Consistently use these skills while implementing programs.
- Learn to work as part of a team to solve problems starting from design and continuing through to implementation.
Class info
Room: Science Center 240Time: MWF 10:30–11:20am
Text:There is no required text for this course, however, if you would like a reference, here are two we recommend (the weekly schedule lists related material from both):
- (D): Think Python: How to Think Like a Computer Scientist by Allen B. Downey
- (Z): Python Programming: an Introduction to Computer Science by John Zelle
(Zelle is on reserve at Cornell Library and there are a few copies available to use in CS lab)
Instructional staff
Professor: Andrew DannerOffice: Science Center 253
Phone: (610) 328-8665
Office hours: by appointment
Student Support: Betsy Horner
Office: Science Center 255
Phone: 957-6062
Student Mentors:Maria Kelly, Sarah Chasins, Frank Chien, John Dinh, Kwame Osei
Other Sections: Jeff Knerr (MWF 11:30am–12:20pm) | Tia Newhall (TR 11:20am–12:35pm)
Study sessions
Several student mentors will assist me in class and run study sessions in the main CS lab (Science Center 240) on the following evenings:
| Day | Time | Location |
|---|---|---|
| Sunday | 7:00–9:00pm | Sci Center 240 |
| Wednesday | 7:00–9:00pm | Sci Center 240 |
You are invited – and encouraged – to participate in these study sessions to prepare for quizzes, to discuss programming concepts, and to get friendly assistance in working on lab assignments. Our CS mentoring team is dedicated to helping students, who have no prior knowledge of computer science, learn to program in Python while keeping their senses of humor intact. As an added bonus, free food is often provided at the sessions.
Lab Sessions
The CS lab is open 24 hours a day, 7 days a week for you to use for CS21 lab assignments. In addition, the CS21 professors will be in the main CS labs to help CS21 students with their lab assignments. You are not required to attend any of these sessions, but you should take advantage of them to get assistance with your lab assignments. Any CS21 student is welcome to attend any session.| Time | Professor | Location |
|---|---|---|
| Monday 2:30–4:00pm | Danner | Sci Center 240 |
| Monday 3:30–5:00pm | Newhall | Sci Center 240 |
| Friday 1:00–2:00pm * | Knerr | Sci Center 252 |
* if there's a campus collection, the Friday lab will be 2-3pm
Schedule
| WEEK | DAY | ANNOUNCEMENTS | TOPIC & REFERENCES | INCLASS & ASSIGNMENTS |
| 1 | Aug 31 | Introduction to Python and Unix Ch. 1-2 (Z), Ch. 1-Ch. 2 (D) |
In class: week 1 Assn: lab 0 Assn: lab 1 |
|
| Sep 02 | ||||
| Sep 04 | ||||
| 2 | Sep 07 | Numbers and Strings Ch. 3-4 (Z), Ch. 2 (D) |
In class: week 2 Assn: lab 2 |
|
| Sep 09 | Practice Quiz 1 (pdf) | |||
| Sep 11 | Drop/Add Ends | |||
| 3 | Sep 14 | Booleans Ch. 7 and p. 247 (Z), Ch. 5.1-5.7, Ch. 7 (D) |
In class: week 3 Assn: lab 3 |
|
| Sep 16 | ||||
| Sep 18 | ||||
| 4 | Sep 21 | Graphics, objects The Graphics Library Ch. 5 Online copy (Z) |
In class: week 4 Assn: lab 4 |
|
| Sep 23 | ||||
| Sep 25 | Practice Quiz 2 (pdf) | |||
| 5 | Sep 28 | Functions, objects Ch. 6 (Z), Ch. 3, Ch. 6 (D) |
In class: week 5 Assn: lab 5 |
|
| Sep 30 | ||||
| Oct 02 | ||||
| 6 | Oct 05 | Loops, Top Down Design Ch. 8, 9 (Z), Ch. 7 (D) |
In class: week 6 Assn: lab 6 |
|
| Oct 07 | Practice Quiz 3 (pdf) | |||
| Oct 09 | ||||
Oct 12 |
Fall Break |
|||
Oct 14 |
||||
Oct 16 |
||||
| 7 | Oct 19 | Top Down Design, File I/O Ch. 9, 4.6 (Z), Ch. 14 (D) |
In class: week 7 Assn: lab 7 |
|
| Oct 21 | ||||
| Oct 23 | ||||
| 8 | Oct 26 | Searching, Analysis of Algorithms Ch. 13.1 (Z), Ch. 9 (D) |
In class: week 8 | |
| Oct 28 | Practice Quiz 4 (pdf) | |||
| Oct 30 | ||||
| 9 | Nov 02 | Recursion, Sorting Ch. 13.2-13.3 (Z), Ch. 5.8-5.10, 9 (D) |
In class: week 9 Assn: lab 8 |
|
| Nov 04 | ||||
| Nov 06 | CR/NC/W Deadline | |||
| 10 | Nov 09 | More Searching, Sorting and Recursion Ch. 13.1-13.3 (Z) |
In class: week 10 Assn: lab 9 |
|
| Nov 11 | Practice Quiz 5 (pdf) | |||
| Nov 13 | ||||
| 11 | Nov 16 | Defining new classes Ch. 10 (Z), Ch. 15-17 (D) |
In class: week 11 Assn: lab 10 |
|
| Nov 18 | ||||
| Nov 20 | ||||
| 12 | Nov 23 | Linked lists intro handout |
In class: week 12 | |
| Nov 25 | ||||
Nov 27 |
Thanksgiving Break |
|||
| 13 | Nov 30 | Linked lists handout |
In class: week 13 | |
| Dec 02 | ||||
| Dec 04 | ||||
| 14 | Dec 07 | Wrapup |
In class: | |
Dec 17 |
Final Exam 7pm Sci 101 |
|||
Grading
Grades will be weighted as follows:| 40% | Lab assignments |
| 30% | Quizzes |
| 5% | Class Participation |
| 25% | Final Exam |
Lab and Homework policy
Programming assignments will typically be assigned in class at the beginning of the week and will be due before midnight the following Tuesday night. You are strongly encouraged to start early and to attend the study sessions for extra practice.
You will submit you assignments electronically using the handin21 program. You may submit your assignment multiple times, but each submission overwrites the previous one and only the final submission will be graded. Late assignments will not be accepted except in extreme situations and only if you contact me before the deadline. Even if you do not fully complete an assignment, you may submit what you have done to receive partial credit.
How to Succeed in CS21
-
Read the material before you come to class.
Don't worry about total comprehension, but at least get a feel for what we will be covering that week. If you have some understanding of the material coming into class, it will be easier for you to ask questions during class, rather than later when help may not be available. Additionally, we often do lab exercises during class. This is an important part of the learning process, as these exercises give you immediate experience with the material we are covering. If you read the book before you come to class, you'll be able to complete these exercises more easily. -
Ask questions if you don't understand.
This means both during class and while doing your lab exercises. This class continually builds on previous material, so if you don't understand something one week, it will continue to be a problem the next week, and the week after that, and so on. If you need help, ask your classmates, attend the study sessions, come talk with me during my office hours, or email me your question. -
Start the lab assignments early.
I realize this one is not always easy to do, but if you can get in the habit of doing this, you will be much better off. If you get stuck early (i.e., not two hours before it is due), there will be time to look for help. In addition, if you start early enough, you can take a break, go do something else, and come back later. I find I always have at least a few new ideas when I come back to a problem after a break. If you wait until the last minute, you can't do this. -
Practice, practice, practice.
The only effective way to learn the material and pass the quizes and exams is to consistently do the lab projects. Finish all of the assigned programs (and do some extras, for fun!). Even if you don't get them done on time, they will still help you learn the material. -
Seek help early and often.
Because course material builds on previous material, it is essential to your success in this class that you keep up with the course material. If you are having difficulty with a programming assignment, if you didn't follow something covered in lecture, if you feel you need some extra help understanding or practicing some of the course material, or if you just want to discuss something from a lecture, an assignment, or the text, please come to my office hours. -
Attend CS21 Study Sessions.
The CS21 Student Mentors (Ninjas) hold evening study sessions each week. You are encouraged to participate in these sessions. The Ninjas will help you prepare for quizzes, will provide additional instruction in programming concepts, and will provide friendly assistance on your lab assignments. -
Work with a partner.
Several of the assignments will optionally allow you to work with a partner. This is highly recommended. Working in groups can help you progress further through the assignment more quickly. Partners can often catch silly coding mistakes that may leave you frustrated for hours if working alone. Explaining concepts and ideas to a partner is a great way to help you learn the material and clarify your thinking. If you are interested in working with a partner but do not know who to ask, contact me and I can try to pair you up with a compatible student.
Programming Style
Programming is not a dry mechanical process, but a form of art. Well written code has an aesthetic appeal while poor form can make other programmers and instructors cringe. Programming assignments will be graded based on style and correctness. Good programming practices usually include many of the following principles:
- A comment at the top of the program that includes:
- Program authors
- Date or Dates
- A brief description of what the program does
- Concise comments that summarize major sections of your code
- Meaningful variable and function names
- Function comments that include:
- description of what function does
- description of input parameters
- description of return value or values
- Well organized code
- White space or comments to improve legibility
- Avoidance of large blocks of copy-pasted code
Academic Accommodations
Academic accommodations are available for students with disabilities who are registered with Student Disability Services in the Dean's office. Students in need of disability accommodations should schedule an appointment with me early in the semester to discuss accommodations for this course that have been approved by the Dean's office. All requests must come through an accommodation letter from the Dean's office. To receive an accommodation for a course activity, your meeting with me must be at least one week prior to the activity.Contact Tracey Rush at the Dean's office and follow these steps for obtaining accommodations.
Academic Integrity
Academic honesty is required in all work you submit to be graded. You may not submit work done with (or by) someone else. You may not examine or use work done by others to complete your own work. You may discuss assignment specifications and requirements with others in the class to be sure you understand the problem. In addition, you are allowed to work with others to help learn the course material. However, with the exception of the student mentors and your partner on group assignments, you may not work with others on your assignments.
All code you submit must be your own with the following permissible exceptions: code distributed in class, code found in the course text book, and code worked on with an partner. In these cases, you should always include detailed comments that indicates on which parts of the assignment you received help, and what your sources were.
"It is the opinion of the faculty that for an intentional first offense, failure in the course normally is appropriate. Suspension for a semester or deprivation of the degree in that year may also be appropriate when warranted by the seriousness of the offense." - Student Handbook (2009-2010, pg18 Section I.B.3.b.i)
Please see me if there are any questions about what is permissible.
External Links
Links that are related to the course may be posted here. If you have suggestions for links, let me know.
Vi Quick Reference
Python style guide From Prof. Tia Newhall
Using Unix Improved
Basic Unix
Commands
Python Documentation
Zelle Textbook site
How To Think Like a Computer Scientist: Learning with Python