CS21:Intro to Computer Science

(Spring 2018)

Course Info | Schedule | Grading | Academic Integrity
Student Support | Tips for Success | Code Style | Piazza | Links

Announcements

  • Lab 12 is available. This is an optional lab using dictionaries, and provides a good way for you to review many of the topics covered this semester.
  • The final exam will be Sunday, May 13, from 2-5pm in SCI 101.
  • The final exam study guide is available. There will be two review sessions, both in SC 256: Wednesday, May 9 from 2-3:30pm and Friday, May 11 from 12:30-2pm.

Course Information

Jump to this week
Section 1: MWF 9:30–10:20, Sci 256
Professor: Ameet Soni
Office: Sci 253
Office hours: Thursdays, 2-4pm
In class polling: pollev.com/ameetsoni277
Lab Instructor: David Mauskop
Office: Sci 262A
Office hours: Thursday, 3-5pm

Piazza: CS21 Q&A forum

Links to all sections:

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 We will primarily be using the online book How to think like a computer scientist: Learning with Python by Elkner, Downey and Meyers.


See the Schedule for each week's reading assignment.

Here are a few other useful online resources:

Goals for the course:

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


Schedule

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

Jan 22

 

Course Introduction

Feedback Response: Mon, Wed

InClass Exercises: Wed,Fri

Lab 0: unix, editing

Jan 24

 

Jan 26

 
2

Jan 29

 

Numbers, Strings, and Loops

Feedback Response: Wed

In Class Exercises

Lab 1: First Programs

Jan 31

 

Feb 02

Drop/add ends

3

Feb 05

Quiz study guide

Conditions and Boolean Logic

Feedback Response: Mon

In Class Exercises

Lab 2: numbers and strings

Feb 07

Quiz 1

Feb 09

 
4

Feb 12

 

First Functions, while Loops

Feedback Response: Mon; Fri

In Class Exercises

Lab 3: if/else

Feb 14

 

Feb 16

 
5

Feb 19

Q2 study guide

Fruitful Functions

In Class Exercises

Lab 4: while loops/functions

Feb 21

Quiz 2

Feb 23

 
6

Feb 26

 

Graphics, Using Objects

Feedback Response: Wed, Fri

In Class Exercises

Lab 5: more functions

Feb 28

 

Mar 02

 
7

Mar 05

Q3 study guide

Top-Down Design

In Class Exercises

Lab 6: graphics

Mar 07

Quiz 3

Mar 09

 
 

Mar 12

Spring Break

Mar 14

Mar 16

8

Mar 19

 

Top-Down Design

(continued)

In Class Exercises: Week 8 - TDD #2
In Class Exercises: Week 9 - Search
Feedback Response: Fri-Wk9

Lab 7: top-down design

Mar 21

 

Mar 23

 
9

Mar 26

Q4 study guide

Searching

Mar 28

Quiz 4

Mar 30

CR/NC/W Deadline

10

Apr 02

 

Sorting

In Class Exercises
Feedback Response

Lab 8: Searching

Apr 04

 

Apr 06

 
11

Apr 09

Q5 study guide

Recursion

In Class Exercises

Lab 9: Sorting

Apr 11

Quiz 5

Apr 13

 
12

Apr 16

 

Classes and Objects

In Class Exercises
Feedback Response: Mon,Fri

Lab 10: recursion

Apr 18

 

Apr 20

 
13

Apr 23

Q6 study guide

In Class Exercises: Week 13
Feedback Response: Fri

In Class Exercises: Week 14
Feedback Response: Wed

Lab 11: classes
Optional Lab 12: Dictionaries

Apr 25

Quiz 6

Apr 27

 
14

Apr 30

 

Dictionaries and Wrap-up

May 02

 

May 04

Final exam study guide

 

May 13

Final Exam: May 13 2-5pm, Sci Cen 101


Grading Policies

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

Exam and Quizzes

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.

If you are not present on the day of a quiz, and do not let me know ahead of time that you are missing class, you will receive a zero for that quiz.

There will be one final exam for the semester. Details and dates will be released during the semester. Please read the section on accommodations if you are in need of extra time. You must inform me of accommodations or conflicts at least 2 weeks in advance of the exam.

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 David Mauskop Sci 240
CS21 B 2:45—4:15pm Tuesdays Lisa Meeden Sci 240
CS21 C 1:15—2:45pm Wednesdays Lila Fontes Sci 256
CS21 D 3:00—4:30pm Wednesdays Ameet Soni Sci 256

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 Policy:

Late assignments are not accepted and will receive zero credit (see exceptions below). 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.

If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition (e.g., extended illness, concussion, hospitalization) or other emergency, you must contact the dean's office and your instructors. Faculty will coordinate with the deans to determine and provide the appropriate accommodations. Note that for illnesses, the College's medical excuse policy, states that you must be seen and diagnosed by the Worth Health Center if you would like them to contact your class dean with corroborating medical information.


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: Anya Chaudhri, Christina Holmgren, Tristan Cates, Jeff Novak, Shayne Rothman, Zachary Viscusi, Michael Kourakos, Haochen Wang, Daniel Chaiken, Bayliss Wagner, Tai Thonghai, Yash Kewalramani.

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
Fridays 7—9pm 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 and Clothier 16.

Academic Accommodations

If you believe that you need accommodations for a disability, please contact the Office of Student Disability Services (Parrish 113W) or email studentdisabilityservices at swarthmore.edu to arrange an appointment to discuss your needs. As appropriate, the Office will issue students with documented disabilities a formal Accommodations Letter. Since accommodations require early planning and are not retroactive, please contact the Office 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 the Office of Student Disability Services 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 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:


Piazza

This semester we’ll be using Piazza, an online Q&A forum for class discussion, help with labs, clarifications, and announcements that pertain to all sections of cs21. You should have received an email invitation to join CS21 on Piazza. If you didn't, please let us know.

Piazza is meant for questions outside of regular meeting times such as office hours, ninja sessions, class, and lab. Please do not hesitate to ask and answer questions on Piazza, but keep in mind the following guidelines:

  1. Piazza should be used for ALL content and logistics questions outside of class, lab, office hours, and ninja sessions. Please do not email instructors or ninjas with your code or questions about the assignments.
  2. If there is a personal issue that relates only to you, please email your instructor.
  3. We encourage non-anonymous posts, but you may post anonymously (to your classmates, not the instructors).
  4. Do NOT post long blocks of code on Piazza - if you can distill the problem to 1-2 lines of code and an error message, that’s fine, but try to avoid giving out key components of your work.
  5. By the same token, when answering a question, try to give some guiding help but do not post code fixes or explicit solutions to the problem.
  6. Posting on Piazza counts toward your participation grade, both asking and answering!

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

Using Unix
Basic Unix Commands
Remote access with atom