CSCI E-50a Syllabus
Introduction to the intellectual enterprises of computer science and the art of programming. This course teaches students how to think algorithmically and solve problems efficiently. Topics include abstraction, algorithms, data structures, encapsulation, resource management, security, software engineering, and web development. Languages include C, Python, and JavaScript plus SQL, CSS, and HTML. Problem sets inspired by real-world domains of biology, cryptography, finance, forensics, and gaming. Designed for concentrators and non-concentrators alike, with or without prior programming experience
This course represents the first half of CSCI E-50. When taken in conjunction with CSCI E-50b, this course effectively allows students twice as much time to work through CSCI E-50’s curriculum. When taken in coordination with a high school offering Advanced Placement courses, this course aligns to the AP Computer Science Principles curriculum framework, and students who earn satisfactory grades in the course may be able to earn AP credit.
Expectations
You are expected to
-
submit fifteen programming problems,
-
submit five written problems, and
-
take two quizzes.
Grades
All students must ordinarily submit all assigned problems and take the two quizzes in order to be eligible for a satisfactory grade unless granted an exception in writing by the course’s heads.
Final grades are determined using the following weights:
Programming Problems |
50% |
Written Problems |
20% |
Quiz 0 |
10% |
Quiz 1 |
20% |
Programming problems are evaluated primarily along axes of scope, correctness, design, and style, with scores ordinarily determined by scope × (3 × correctness + 2 × design + 1 × style). Scores are normalized across TFs at term’s end, so mid-semester comparisons among students of scores are not reliable indicators of standing. Written problems are evaluated holistically.
Know that CS50 draws quite the spectrum of students, including "those less comfortable," "those more comfortable," and those somewhere in between. However, what ultimately matters in this course is not so much where you end up relative to your classmates but where you, in Week 14, end up relative to yourself in Week 0.
The course is not graded on a curve. The course does not have pre-determined cutoffs for final grades. Those less comfortable and somewhere in between are not at a disadvantage vis-à-vis those more comfortable. Each student’s final grade is individually determined at term’s end after input from the teaching fellows. Remarkable effort and upward trending are considered.
Books
No books are required or recommended for this course. However, you might find the below books of interest. Realize that free, if not superior, resources can be found on the course’s website.
C Programming Absolute Beginner’s Guide, Third Edition
Greg Perry, Dean Miller
Pearson Education, 2014
ISBN 0-789-75198-4
Hacker’s Delight, Second Edition
Henry S. Warren Jr.
Pearson Education, 2013
ISBN 0-321-84268-5
How Computers Work, Tenth Edition
Ron White
Que Publishing, 2014
ISBN 0-7897-4984-X
Programming in C, Fourth Edition
Stephen G. Kochan
Pearson Education, 2015
ISBN 0-321-77641-0
Lectures
Most lectures were recorded at Harvard in Sanders Theatre in Fall 2015. (A few lectures were recorded at Yale.)
For students taking CSCI E-50a, the pace of the course differs from CSCI E-50, which runs each semester in parallel. Below are dates on which lecture content will be made available to view through the course’s website.
Lecture |
Released |
|
Week 0 |
Computers and computing. Hardware. Memory. Binary. ASCII. Algorithms. |
Wed 8/31, Fri 9/2 |
Week 1 |
Tue 9/6, Fri 9/9 |
|
Week 2 |
Tue 9/13, Fri 9/16 |
|
Week 3 |
Tue 9/20, Fri 9/23 |
|
Week 4 |
Tue 9/27, Fri 9/30 |
|
Week 5 |
no lecture, Quiz 0 |
|
Week 6 |
Fri 10/14 |
|
Week 7 |
Tue 10/18, Fri 10/21 |
|
Week 8 |
Tue 10/25 |
|
Week 9 |
Linear search. Bubble sort. Selection sort. Insertion sort. Binary search. Time complexity. |
Tue 11/1, Fri 11/4 |
Week 10 |
Unsolvable problems. Principles of good design. ncurses. Structures. Encapsulation. |
Tue 11/8, Fri 11/11 |
Week 11 |
Tue 11/15, Fri 11/18 |
|
Week 12 |
no lecture, Thanksgiving |
|
Week 13 |
Tue 11/29, Fri 12/2 |
|
Week 14 |
no lecture, Quiz 1 |
Sections
Lectures are supplemented by twice-weekly, 45 to 60-minute sections led by the teaching fellows. Sections provide you with opportunities to explore the course’s material in a more intimate environment.
Sectioning begins in Week 1. Sections themselves begin in Week 2.
After sectioning is complete, a schedule of sections will appear below.
Office Hours
Office hours are online opportunities for assistance on problem sets with the course’s teaching fellows and course assistants. A schedule of office hours will appear on the course’s website. Office hours will begin in Week 2.
Walkthroughs
Integrated into a number of the course’s problems are "walkthroughs," videos via which the course’s staff offer direction on where to begin and how to approach a challenge. You are expected to watch walkthroughs before asking questions about problem sets at office hours or via CS50 Discuss.
Postmortems
Available after many problems' deadlines are "postmortems," videos via which the course’s staff explore actual solutions to problem sets. You are expected to watch postmortems for insights into how else you could have (or should have!) implemented your own solutions.
Problems
Twenty problems are assigned during the semester, each one a subset of what would be considered a "problem set" in CSCI E-50. Each is due by noon on either a Wednesday or a Saturday. Lateness of electronic submissions is determined down to the minute by submissions' timestamps. Submitting more than seven minutes late is equivalent to submitting twenty-four hours late. Late work is not ordinarily accepted, except in cases of medical emergency.
A schedule of problems, subject to change, appears below.
Problem | Type | Released | Due |
---|---|---|---|
Written |
Fri 9/2 |
Wed 9/7 |
|
Programming |
Tue 9/6 |
Sat 9/10 |
|
Programming |
Fri 9/9 |
Wed 9/14 |
|
Programming |
Tue 9/13 |
Sat 9/17 |
|
Programming |
Fri 9/16 |
Wed 9/21 |
|
Programming |
Tue 9/20 |
Sat 9/24 |
|
Written |
Fri 9/23 |
Wed 9/28 |
|
Programming |
Tue 9/27 |
Sat 10/1 |
|
Written |
Tue 10/11 |
Sat 10/15 |
|
Programming |
Sat 10/15 |
Wed 10/19 |
|
Programming |
Tue 10/18 |
Sat 10/22 |
|
Programming |
Fri 10/21 |
Wed 10/26 |
|
Written |
Tue 10/25 |
Sat 10/29 |
|
Programming |
Fri 10/28 |
Wed 11/2 |
|
Programming |
Tue 11/1 |
Sat 11/5 |
|
Programming |
Fri 11/4 |
Sat 11/12 |
|
Programming |
Fri 11/11 |
Sat 11/19 |
|
Written |
Fri 11/18 |
Wed 11/23 |
|
Programming |
Wed 11/23 |
Sat 12/3 |
|
Programming |
Fri 12/2 |
Wed 12/7 |
Quizzes
The course has two 60-minute quizzes. These quizzes are "closed-book," but you may utilize during each quiz one two-sided page (8.5" × 11") of handwritten or typed notes, blank scrap paper, and a pen or pencil, nothing else.
Unless arranged with the course’s heads in advance, the quiz cannot ordinarily be taken at alternative times even if missed by accident, except in cases of medical emergency.
The quizzes take place online for a period of 24 hours (you may begin at any time within the window, but have 60 minutes from when you start), with the due dates outlined below.
Quiz | Released | Due |
---|---|---|
Quiz 0 |
Thu 10/6, noon |
Fri 10/7, noon |
Quiz 1 |
Thu 12/8, noon |
Fri 12/9, noon |
Academic Honesty
This course’s philosophy on academic honesty is best stated as "be reasonable." The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on problem sets is not permitted except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on the course’s test and quiz is not permitted at all. Collaboration on the course’s final project is permitted to the extent prescribed by its specification.
Below are rules of thumb that (inexhaustively) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from the course’s heads. Acts considered not reasonable by the course are handled harshly. If the course refers some matter for disciplinary action and the outcome is punitive, the course reserves the right to impose local sanctions on top of that outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself. The course ordinarily recommends exclusion (i.e., required withdrawal) from the course itself.
If you commit some act that is not reasonable but bring it to the attention of the course’s heads within 72 hours, the course may impose local sanctions that may include an unsatisfactory or failing grade for work submitted, but the course will not refer the matter for further disciplinary action except in cases of repeated acts.
Reasonable
-
Communicating with classmates about problem sets' problems in English (or some other spoken language).
-
Discussing the course’s material with others in order to understand it better.
-
Helping a classmate identify a bug in his or her code at office hours, elsewhere, or even online, as by viewing, compiling, or running his or her code, even on your own computer.
-
Incorporating a few lines of code that you find online or elsewhere into your own code, provided that those lines are not themselves solutions to assigned problems and that you cite the lines' origins.
-
Reviewing past semesters' quizzes and solutions thereto.
-
Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug.
-
Sharing a few lines of your own code online so that others might help you identify and fix a bug.
-
Turning to the course’s heads for help or receiving help from the course’s heads during the quiz or test.
-
Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to problem set’s problems or your own final project.
-
Whiteboarding solutions to problem sets with others using diagrams or pseudocode but not actual code.
-
Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
Not Reasonable
-
Accessing a solution to some problem prior to (re-)submitting your own.
-
Asking a classmate to see his or her solution to a problem set’s problem before (re-)submitting your own.
-
Decompiling, deobfuscating, or disassembling the staff’s solutions to problem sets.
-
Failing to cite (as with comments) the origins of code or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
-
Giving or showing to a classmate a solution to a problem set’s problem when it is he or she, and not you, who is struggling to solve it.
-
Looking at another individual’s work during the test or quiz.
-
Paying or offering to pay an individual for work that you may submit as (part of) your own.
-
Providing or making available solutions to problem sets to individuals who might take this course in the future.
-
Searching for or soliciting outright solutions to problem sets online or elsewhere.
-
Splitting a problem set’s workload with another individual and combining your work.
-
Submitting (after possibly modifying) the work of another individual beyond the few lines allowed herein.
-
Submitting the same or similar work to this course that you have submitted or will submit to another.
-
Submitting work to this course that you intend to use outside of the course (e.g., for a job) without prior approval from the course’s heads.
-
Turning to humans (besides the course’s heads) for help or receiving help from humans (besides the course’s heads) during the quiz or test.
-
Viewing another’s solution to a problem set’s problem and basing your own solution on it.
Acknowledgement and Authorization
Harvard plans to record audio, photos, and video of Computer Science 50 (CS50) lectures, sections, office hours, seminars, and other events and activities related to CS50 (the "Recordings"), with the aims of making the content of the course more widely available and contributing to public understanding of innovative learning (the "Projects"). The Recordings, or edited versions of them, may be made available to other Harvard students, to students at other educational institutions, and to the broader public via edX, the Internet, television, theatrical distribution, digital media, or other means. It is also possible that the Recordings may be used to make other derivative works in the future. Students may elect not to appear in photos and video used in the Projects and may still participate fully in CS50.
When you submit Problem Set 0, you will need to sign online an Acknowledgement and Authorization in the following form:
I understand that, if I do not wish any photos or video of me to be used as part of the Projects, I should so inform the course’s instructor by emailing recordings@cs50.harvard.edu within one week of enrolling in CS50. In that event, I understand that I should sit in the designated "no-film" zone of CS50 classrooms and should not walk in the field of view of the cameras. I understand that Harvard will take reasonable steps, with my cooperation, to avoid including identifiable images of me in the Projects' photos and video shot in classrooms and other course locations after I opt out as just described. I understand that I am free to opt out of the Projects' photos and video in this way, and that doing so will not affect my grade or my ability to participate in course activities.
Unless I opt out of the Projects' photos and video as described above and take the steps that will be outlined by the instructor to avoid being filmed, I authorize Harvard and its designees to record and use photos and video of my participation in CS50 and activities related to CS50 (the "Recordings"). I understand and agree that the Recordings may include my image, name, and voice. I also understand and agree that, even if I opt out of the Projects' photos and video, my spoken name and voice may be picked up by microphones outside the "no-film" zone and may be included in the Recordings.
I understand and agree that Harvard and its designees will have the irrevocable, worldwide right to make, edit, modify, copy, publish, transmit, distribute, sell, publicly display, publicly perform, and otherwise use and make available its respective Recordings and any other works that may be derived from those Recordings, in any manner or medium now known or later invented, and to authorize others to do so as well. I hereby transfer to Harvard any rights, including copyrights, I may have in the Recordings that Harvard makes. I will remain free to use and disseminate any ideas, remarks, or other material that I may contribute to course discussions.
I acknowledge and agree that I will not be entitled to any payment, now or in the future, in connection with the Recordings or any works derived from them. This Acknowledgment and Authorization is a binding agreement, and is signed as a document under seal governed by the laws of the Commonwealth of Massachusetts.
Unless you opt out as described in the Acknowledgment and Authorization, you are agreeing, by attending CS50, that your participation in CS50 and related activities may be recorded and used by Harvard in connection with the Projects without further obligation or liability to you, even if you do not sign any authorization.
If you have any questions about the above, contact recordings@cs50.harvard.edu.