Fun facts:

1. grew up in San Clemente (~1hr south of Claremont, on the beach)
2. 7 years in the navy
   1. nuclear submarine officer, personally converted >10g of uranium into pure energy
   2. worked at National Security Agency (NSA)
   3. left Navy as a conscientious objector
3. phd/postdoc at UC Riverside
4. taught in DPRK (i.e. North Korea)
5. my wife is pregnant and due to have a baby April 18th
   1. I will take 2 weeks off for paternity leave when the baby comes

Data structures is the most important course in computer science, and many of the "classic" CS interview questions come from this course. Mastering this material is the first step towards getting a high-paying CS job. See:

1. Salaries: https://www.levels.fyi
2. Benefits: https://www.levels.fyi/benefits/Paternity-Leave/
3. This is despite tech employers illegally colluding to reduce salaries

Who should take this course?

1. This is a second-semester course in computer science designed for students who have previously taken either CS40 (CMC), CS5 (Mudd), or CS51 (Pomona).

2. You cannot take this course if:

   1. you have already taken a data structures course (e.g. Pomona: CS62; HMC: CS60, CS70), or
   2. you are a CS major through Mudd or Pomona.

3. This course is required for CMC's data science major and the computer science sequence. It is optional for the data science sequence.

Learning Objectives:

1. Learn the basics of

   1. linux terminal
   2. git
   3. open source software

2. Be able to answer the following three questions about an algorithm:

   1. Is it correct?
   2. How much resources does it consume? (time, memory, money, etc.)
   3. Can we do better?

This course is NOT an algorithms course. Algorithms courses form the "other half" of classic CS interview questions, and you should consider taking CS148 - Graph Algorithms after this course.

Textbook:

All of our textbooks are both free as in beer and free as in speech:

1. Problem Solving with Algorithms and Data Structures using Python by Brad Miller and David Ranum

2. Official Python Documentation

Grades:

Your grade will be composed of:

1. Weekly labs (worth 2**1 points)
2. Weekly quizzes (worth 2**2 or 2**3 or 2**4 points)
3. Weekly projects (worth 2**3 or 2**4 or 2**5 points)
4. No exams!!!
   1. Non-graduating students will complete a final project due during finals week.
5. Occasional extra credit assignments

Historically, the average student needs to spend about 10 hours per week (outside of class) to get an A. About 25% of students will either: spend 15-20 hours per week and get an A, or spend 10 hours per week and get a B/C.

Late Work Policy:

You lose 2**i points on every assignment, where i is the number of days late minus 1.

Example: Homeworks will be due on Tuesdays, so if you submit on Wednesday then i=0 and you receive a 2**0 (i.e. 1) point penalty. If you submit on Friday, you receive a 2**2 (i.e. 4) point penalty.

It is usually better to submit a correct assignment late than an incorrect one on time.

I expect that most students will be submit late assignments at some point.

Grade Schedule:

Your final grade will be computed according to the following table, with one caveat.

Caveats:

There are 2 "caveat tasks" in this course. These tasks should be easy, and everyone will get full credit on the task just for completing the task. If you don't complete one of the tasks, however, your grade (from the table above) will be docked 10%. (For example, an A- grade would become a B- grade.) You have the entire semester (until I submit grades) to complete these tasks.

You can find the details about the caveat tasks at:

1. caveat_tasks/typespeed.md
2. caveat_tasks/culture.md

Technology Policy:

1. You MUST complete all programming assignments on the lambda server.

2. You MUST use either vim or emacs to complete all programming assignments. In particular, you may not use the GitHub text editor, VSCode, IDLE, or PyCharm for any reason.

   In particular: You MAY NOT use the GitHub interface to edit files for a pull request.

3. You MAY NOT share your lambda server credentials with anyone else.

Violations of any of these policies will be treated as academic integrity violations.

Collaboration Policy

1. There are no restrictions on what you can post to GitHub Issues. In particular, you are highly encouraged to post detailed questions/answers/comments with lots of code.

2. You are highly encouraged to collaborate with students

   1. in class/lab,

   2. in the QCL,

   3. and in office hours.

3. You MAY NOT look at another student's code (or have another human look at your code) in any other context.

4. You MAY NOT look at another student's code on github.

   All projects are developed as open source projects, and so the code is published openly online. The benefits of this model include: (1) you actually learn how to develop/contribute to open source projects; (2) future employers see you have github activity. Please do not abuse this privilege.

I've tried to design the course to be as accessible as possible for people with disabilities. (We'll talk a bit about how to design accessible software in class too!) If you need any further accommodations, please ask.

I want you to succeed, and I'll make every effort to ensure that you can.