Syllabus

The primary goal of this class is to get you to love computer science! I want you to come away understanding how empowering and fun it can be to think about and design algorithms. Even if you don't choose to be a CS major, this class will teach you some very useful skills, both procedural (how to program a computer) and conceptual (how to break down solving a problem into simple steps), that you can apply to other areas of your life.

In terms of content, in this class you will learn basic principles of computer science, and get practical experience with them by writing programs. Along the way, you'll also learn how to write programs in our language of choice: Python.

My intention is that you should be able to do the following by the end of this course:

• Formulate, test, and implement step-by-step general solutions (algorithms) to a variety of problems.
• Analyze algorithms and programs written by others to predict their behavior and understand how they work.
• Recognize and use basic best practices for software development: naming conventions, program structure, comments, etc.
• Understand the basic elements of a computer system: hardware, software, data representation in memory, compilers, interpreters, etc.
• Move on to more advanced courses in the CS department, or continue your own independent work learning about programming or computer science.

• Class Time. Each week of this class is organized around a single “case study” — a high-level problem that we'd like to solve. (These generally correspond to chapters of the book, and highlight particular technical concepts.) We'll spend most of our time in class working on these problems. If all goes well, the majority of our class time will not be just me talking at the front of the room, but instead you working with your classmates to solve some problems.
• Readings. Instead of listening to me lecture a bunch, you will learn most of the primary course material by doing daily reading assignments. There is a reading assignment that you are required to complete before each class meeting. During the class itself, we will dive right into applying the concepts covered in the reading.
• Reading Exercises. Each reading assignment includes a small set of exercises that you are required to complete before each class meeting. These exercises count toward your grade, and I will also be spot-checking them to help plan what we'll do in the upcoming class. Note that the earlier you hand them in, the better I can prepare for class and address any lingering points of confusion, so it's to your benefit to not leave them until the last minute. I will grade them on effort and not correctness, so there is no penalty for trying and failing, which is crucial to learning effectively!
• Quizzes. Starting in the second week, there is a short weekly quiz each Wednesday at the start of class. Quizzes are generally just four to six questions long, and are meant as a check-in for your understanding of the concepts we've recently worked with.
• Projects. On average, there will be about one small project assigned per week. At the end of the term, there is a big final project, which counts as a separate component of your grade.

For explicit details about what's assigned when, please see the Schedule.

• Attendance. I expect that you will attend every class meeting possible. Since our class time is mostly about doing things together, you really miss out if you're not here. If you miss class, no explanation is necessary or desired; I trust you'll do your best to be here and that you have a good reason if you're not. If you're sick on a particular day, please stay home; it's important that you take care of yourself.

  I won't always take roll, but I reserve the right to do so during any class. You may be absent up to twice when I take roll without it affecting your grade. Unless you've made formal arrangements with me in advance*, there are no excused absences beyond this; the two-absence budget given above is designed to accommodate sicknesses or other everyday things that come up.

• Presence. “Presence” is more than just physically being there. Turn off your phone, do not text during class, do not use your computer for anything other than in-class activities and note-taking, etc. We've only got a short time together, so let's make the most of it.
• Asking Questions. That's right, you are required to ask questions if you have them! (Not that I can enforce that.) Raise your hand, interrupt me if you need to, but don't stay silent! If you have a question, your classmates are probably wondering about it too. If my answer to your question isn't helpful, let me know; I'd much rather take the time to answer your question right than to leave you and your classmates confused.
• Assignments. Readings, reading exercises, projects — they're all critical to your continued progress in the course. It's almost always better to take a good stab at something and turn it in on time than to turn it in late but complete; see below for more details.
• Talking to Me. Keep me in the loop. Stop by my office hours or email me to schedule a time to talk, particularly if you're struggling. The whole reason I'm here is to help you learn.

If you need help with an assignment, you can consult the book, post to Piazza, consult with other students, consult with a teddy bear (really! It works!), search online, talk to the prefect, ask a lab assistant (in CMC 102 or 306, evenings and weekends), or come to me. We'll talk some in class about good strategies for searching for answers online, and how best to ask people for help.

If you'd like help from me, please come see me! In particular, many questions are easier to answer as a back-and-forth discussion in person. I also try to answer questions promptly on Piazza. Generally I don't answer questions late in the evening or on weekends.

If you have a question or concern about grading, please talk to me first rather than going to the grader.

In this class, as with all classes at Carleton, there are a number of college-wide resources that can be of help: the library, the Write Place, the department's online resources. Feel free to talk to the lab assistants in the CS labs on the 3rd floor of the CMC in the evenings; they are often CS majors and may be able to help. The Math Skills Center may be able to help you with some aspects of the course. Finally, the college has a tutoring program available too.

Your grade will be computed as follows:

Using the above weights, a total of 90% and up will earn you some level of A, 80% and up at least some level of B, 70% and up at least some level of C, 60% and up at least some level of D.

Late Policy

Learning and coding are both collaborative arts, and in this class you will do a lot of the work in pairs, which I will assign. All reading exercises (and quizzes) are individual assignments. For all the projects and in-class activities this term, however, we will be using a technique called pair programming: you and your partner work side-by-side. Both partners actively collaborate in generating ideas and thinking through problems. When it comes time to write code, you still work side-by-side at a single machine. At any given time, one person is typing and the other is observing, making suggestions and pointing out bugs. You should switch roles frequently, and make sure to keep a 50/50 balance of who serves what role.

The work that you create with your partner is a joint effort and you will both receive the same grade. It is your responsibility to contribute fully to the final product, and to let your partner contribute fully too.

Any work you turn in must be your own work (or the work of you and your partner together). You are free to consult with any of the resources mentioned above, but you are required to credit any assistance you receive, in writing, in what you turn in. You should be prepared to explain any part of anything you submit, without the assistance of your partner. It is your responsibility to make sure that you fully understand the work that you create in your team.

Collaboration and Plagiarism

I am obligated by Carleton policy to report to the Dean of Students any suspected plagiarism or violations of the College's academic integrity policy. The Dean, in turn, brings it to the Academic Standing Committee. The academic penalty for a finding of responsibility can range from a grade of zero in the specific assignment to an F for the course. Please familiarize yourself, if you haven't already, with the Dean of the College's detailed guide to academic integrity.