CS21:Intro to Computer Science

(Knerr/Fall 2015)

Course Info | Schedule | Grading | Academic Integrity
Student Support | Tips for Success | Code Style | Links
Introduction to Computer Science using Python

Announcements


Course Information

Section 3: MWF 11:30–12:20, Sci Cntr 256 (the Birds' nest)
Professor: Jeff Knerr
Piazza: CS21 Q&A forum
Office: Sci Cntr 238A (at back of 240 and 238)
Office hours: I will definitely try to be around on Mondays from 2-4pm. You can also stop by whenever my door is open. I usually work from home on Thursdays.

Other Sections: Zachary Palmer (TR 8:30am–9:45am)
Richard Wicentowski (TR 9:55–11:10)
Andrew Danner (TR 9:55–11:10)

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 CS 35.

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 CS31 or CS35.

Textbook:

book pic See the Schedule for each week's reading assignment. We will primarily be using the online book How to think like a computer scientist: Learning with Python by Elkner, Downey and Meyers.

Here are a few other useful online python resources:

Goals for the course:

By the end of the course, we hope that you will have developed the following skills:


Schedule

This is a tentative schedule; it may change as we go.
WEEK DAY ANNOUNCEMENTS TOPIC & READING LABS     
1

Aug 31

 

Introduction to Python and Unix

In class: M W F
Lab 00: unix, editing

Sep 02

 

Sep 04

 
2

Sep 07

 

Writing simple programs

In class: M W F
Lab 01: first programs

Sep 09

 

Sep 11

Drop/add ends

3

Sep 14

 

Conditionals

In class: M W F
Lab 02: nums and strings

Sep 16

Quiz 1 Topics

Sep 18

Quiz 1

4

Sep 21

 

First functions, while loops

In class: M W F
Lab 03: if/else

Sep 23

 

Sep 25

 
5

Sep 28

 

Graphics, Using Objects

In class: M W F
Lab 04: while loops and functions

Sep 30

Quiz 2 Topics

Oct 02

Quiz 2

6

Oct 05

 

Fruitful Functions

In class: M W F
Lab 05: graphics

Oct 07

 

Oct 09

 
 

Oct 12

Fall Break

Oct 14

Oct 16

7

Oct 19

 

File IO, Top-Down Design

In class: M W F
Lab 06: lists & functions

Oct 21

Quiz 3 Topics

Oct 23

Quiz 3

8

Oct 26

 

Searching

In class: M W F
Lab 07: word warp design

Oct 28

 

Oct 30

 
9

Nov 02

 

Sorting

In class: M W F
Lab 07: word warp

Nov 04

Quiz 4 Topics

Nov 06

CR/NC/W Deadline

Quiz 4

10

Nov 09

 

Recursion

In class: M W F
Lab 08: twitter

Nov 11

 

Nov 13

 
11

Nov 16

 

Classes and Objects

In class: M W F
Lab 09: recursion

Nov 18

Quiz 5 Topics

Nov 20

Quiz 5

12

Nov 23

 

Classes and Objects

  • more examples

In class: M W
Lab 10: Triad

Nov 25

 

Nov 27

Thanksgiving

13

Nov 30

 

Linked Lists

  • python list vs linked list
  • Node() class
  • LinkedList() class
  • linked list methods
  • analysis of algorithms

  • Ch 18: Linked Lists

In class: M W F
Lab 10: Triad

Dec 02

Quiz 6 Topics

Dec 04

Quiz 6

14

Dec 07

Final Exam Topics

Wrap up

In class: M
Lab 11: LinkedLists

Dec 11

Final: 7-10pm Science Center 101


Grading Policies

Grades will be weighted as follows:
40%Lab assignments
30%Quizzes
25%Final Exam
5%Class Participation

Quiz policy

Quizzes will be given at the beginning of class on the days posted on the Schedule. Please look over these dates carefully and contact the professor in advance if you cannot be in class for a quiz.

Lab Policy

This course features weekly lab assignments which are the largest component of your course grade. Lab attendance is required by all students, unless you have already completed and submitted the lab assignment for the week. You must attend the lab session for which you are enrolled:

Weekly Lab Sessions
CS21 A 1:05—2:35pm Tuesdays Wicentowski Science Center 240
CS21 E 1:05—2:35pm Tuesdays Danner Science Center 256
CS21 B 2:45—4:15pm Tuesdays Kutty Science Center 240
CS21 C 1:15—2:45pm Wednesdays Palmer Science Center 240
CS21 D 3:00—4:30pm Wednesdays Palmer Science Center 240

Lab assignments will typically be assigned in class at the beginning of the week and will be due before midnight on Saturdays. 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, and a history of previous submission will be saved. You are encouraged to submit your work regularly.

Late assignments will only be accepted if you contact the professor at least a day before the deadline with a legitimate reason for needing extra time, such as an illness or needing to leave campus.

Even if you do not fully complete an assignment, you should submit what you have done to receive partial credit.

The cs labs are open 24 hours a day, 7 days a week for you to use for CS21 lab assignments.


Academic Integrity

Academic honesty is required in all your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes, but is not limited to, obtaining solutions from students who previously took the course or code that can be found online. You may not share solutions after the due date of the assignment.

Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else's code or let anyone else read your code. All code you submit must be your own with the following permissible exceptions: code distributed in class, and code found in the course text book. 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.

Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook: "Because plagiarism is considered to be so serious a transgression, it is the opinion of the faculty that for the first offense, failure in the course and, as appropriate, suspension for a semester or deprivation of the degree in that year is suitable; for a second offense, the penalty should normally be expulsion." Be aware that we will be routinely running plagiarism detection software on the lab solutions of students from all sections of CS21.

Please contact me if you have any questions about what is permissible in this course.


Student Support

Lauri Courtenay is the CS Department's Academic Support Coordinator. She will be working closely with our student mentors, also known as Ninjas, to help you learn how to program and think like a computer scientist. The CS21 Ninjas will assist me in class and run evening study sessions in the birds' nest (Sci 256). The CS21 Ninjas (student mentors) are: Rachel Diamond, Daniel Redelmeier, Diana Martschenko, Caleb Ho, Emily Wu, Daniel Pike, Carlo Sivilotti, Charlotte Raty, Michael Song, and Reba Magier.

Study Sessions

You are invited -- and encouraged -- to participate in Ninja evening 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 snacks will be provided at the sessions. The sessions are held:

Weekly Evening Ninja Sessions
Tuesdays 7—9pm Sci Center 256
Wednesdays 7—10pm Sci Center 256

Accessing the CS labs after hours

You can use your ID to gain access to the computer labs at nights and on the weekends. Just wave your ID over the microprox reader next to the lab doors. When the green light goes on, just push the door to get in (the door knob will not turn). If the green light doesn't go on, then we need to enter your microprox number into the system. Email local-staff@cs.swarthmore.edu (or see Bridget) if you have problems with this. If the building is locked, you can use your ID to enter the door between Martin and Cornell library. For this class, your ID will give you access to the labs in rooms 238, 240, and 256.

Academic Accommodations

If you believe that you need accommodations for a disability, please contact Leslie Hempling in the Office of Student Disability Services (Parrish 113) or email lhempli1 to arrange an appointment to discuss your needs. As appropriate, she will issue students with documented disabilities a formal Accommodations Letter. Since accommodations require early planning and are not retroactive, please contact her as soon as possible. For details about the accommodations process, visit the Student Disability Service website.

To receive an accommodation for a course activity, you must have an Accommodation Authorization letter from Leslie Hempling and you need to meet with me to work out the details of your accommodation at least one week prior to the activity.

You are also welcome to contact me privately to discuss your academic needs. However, all disability-related accommodations must be arranged through Leslie Hempling in the Office Of Student Disability Services.


How to Succeed in CS 21


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:

Also, look over the Python Code Style Guide for more details and some examples of good code style.


Links that are related to the course may be posted here. If you have suggestions for links, let me know.

Python Tutor
Vi Quick Reference
Python style guide From Prof. Tia Newhall
Using Unix
Basic Unix Commands
Python Documentation (Note: we are using v2.7)
Graphics reference
How To Think Like a Computer Scientist: Python for Software Design
Dive Into Python
(A Semi-Official) Python FAQ Zone
NodeBox
pythonchallenge
emacs beginner's guide