Syllabus

This is CS50's introduction to computer science for business professionals, designed for managers, product managers, founders, and decision-makers more generally. Whereas CS50 itself takes a bottom-up approach, emphasizing mastery of low-level concepts and implementation details thereof, this course takes a top-down approach, emphasizing mastery of high-level concepts and design decisions related thereto. Through lectures on computational thinking, programming languages, internet technologies, web development, technology stacks, and cloud computing, this course empowers you to make technological decisions even if not a technologist yourself. You’ll emerge from this course with first-hand appreciation of how it all works and all the more confident in the factors that should guide your decision-making.

Instructor

Expectations

You are expected to

  • watch six lectures online and

  • submit six assignments online.

Website

Certificates

To be eligible for a verified certificate from edX, you must receive a satisfactory score (at least 70%) on each of the course’s six assignments.

Lectures

The course’s lectures were filmed at Harvard University.

A summary of lectures appears below.

Assignments

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 assignments 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 work to classmates and others, but you may not view theirs, so long as you and they respect this policy’s other constraints.

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. If the course determines that you have commited an act that is not reasonable, you may be deemed ineligible for a certificate. If you commit some act that is not reasonable but bring it to the attention of the course’s instructor within 72 hours, the course may reconsider that outcome.

Reasonable

  • Communicating with classmates about assignments 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 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 snippets are not themselves solutions to assigned problems and that you cite the snippets' origins.

  • Sending or showing an answer or code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a mistake.

  • Sharing snippets of your own answers or code online so that others might help you identify and fix a mistake.

  • 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 assignments.

  • Whiteboarding solutions to assignments with others outside of your team 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

  • Asking a classmate to see his or her answer or code before (re-)submitting your own.

  • 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 an answer or code when it is he or she, and not you, who is struggling with their own.

  • Paying or offering to pay an individual for work that you may submit as (part of) your own.

  • Providing or making available answers or code to individuals who might take this course in the future.

  • Searching for or soliciting outright solutions to assignments online or elsewhere.

  • Submitting (after possibly modifying) another’s words without attribution for some assignment.

  • 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 instructor.

  • Viewing another’s solution to an assignment and basing your own solution on it.