ossu/computer-science: four admission rules, four stages, and a spreadsheet the page warns you about

Four admission rules decide what goes in, and a book covers what fails them

A course is in this curriculum because it clears four conditions: it must be open for enrollment, it must run regularly, ideally in self-paced format and otherwise several times a year, it must be of generally high quality in teaching materials and pedagogical principles, and it must match the curricular standards of CS 2013, the Curriculum Guidelines for Undergraduate Degree Programs in Computer Science, which the repository ships as CURRICULAR_GUIDELINES.md. Courses drawn from places such as Harvard, Princeton, and MIT are included on the strength of those conditions rather than on reputation. When no course meets the criteria, the coursework is supplemented with a book, and material that is good but does not fit belongs in extras/courses.md or extras/readings.md. Consequence for the reader: you can check any course against the four rules yourself, but the rules are applied when the list is written, so nothing here tells you whether a course you liked last year still takes enrollments.

The four stages end in peer review, not in anything anyone grades

The curriculum is organised as a ladder. Intro CS is for students to try the field out and see whether it suits them. Core CS maps to roughly the first three years of a degree, the material every major is expected to take. Advanced CS maps to roughly the final year and is elective. The Final Project is the last step, a project that lets students validate, consolidate, and display what they learned, evaluated by peers worldwide. Consequence for the reader: the ladder's only external check is that final peer review, and nothing in the repository issues a certificate, a grade, or a letter at the end. The readme also says the curriculum is not merely for career training or professional development, and it carries a content policy: if you show your coursework publicly you may share only the files you are allowed to, and you are expected to respect the code of conduct you signed at the start of each course.

Two years and twenty hours a week, computed in a spreadsheet you copy

The duration estimate is arithmetic rather than a claim: about two years if you plan carefully, at roughly twenty hours a week of study. To turn that into a date you copy a linked spreadsheet, enter your start date and expected weekly hours in the Timeline sheet, and later record real course completion dates in the Curriculum Data sheet so the estimate updates as you go. Consequence for the reader: the pace assumption is yours to defend, and the number most people will quote, twenty hours a week, is a planning input, not a measurement of how long anyone actually took. The readme is explicit that learners can work through the curriculum alone or in groups, in order or out of order, so the twenty hour figure describes a schedule, not a measurement taken from anyone.

The readme warns you against the very spreadsheet it hands you

The spreadsheet sits under a warning in the same page. It is called a useful tool for estimating the time you need, with the caveat that it may not always be up to date with the curriculum, and the instruction that follows is to use the OSSU CS website or the repository to see what courses to do. The community section repeats the pattern for a wider audience, warning that a few third party, deprecated, or outdated materials turn up when you search for OSSU and telling readers to ignore them. The named offenders are specific: an unmaintained and deprecated Firebase app, with a FAQ entry explaining why it is broken, an unmaintained and deprecated Trello board, and third party Notion templates. Consequence for the reader: anything you find outside the website and the repository may be a known-stale copy, and the plan you build can be quietly wrong if it was built from a schedule the curriculum has since changed.

Free material, except the part where somebody grades your work

The cost position is stated with a qualifier rather than a promise. All or nearly all course material is available for free, but some courses may charge money for assignments, tests, or projects to be graded. The readme points out that Coursera and edX both run financial assistance schemes, and leaves the decision to your own time and budget with the line that you cannot purchase success. Consequence for the reader: the curriculum document itself costs nothing, and the repository is MIT licensed, so the money question is entirely about the outside courses that carry the actual teaching. Because the charge lands on the graded portion rather than on the lectures, the bill arrives at the point where you submit work, which is also the point where you are least inclined to stop.

Core CS is meant to be walked in order, with math as the sanctioned parallel track

The process section recommends doing all of the Core CS courses, skipping one only when you are certain you have already learned the material, and working through them in order from top to bottom for simplicity. It then concedes the realistic case: some students study several courses at once to vary the material in a day, and a popular option is to take the math courses in parallel with the introductory courses. Prerequisites are listed per course so you can judge whether you are prepared. Consequence for the reader: the ordering is the pedagogy, and a learner who collects courses by interest alone will reach a later subject without the earlier foundation, with the prerequisite list as the only warning. The parallel option is the one sanctioned exception, and it is narrow: it pairs math with the introductory courses, not any two subjects of your choosing.

Advanced CS collapses to one subject, and how deep is deep is left to you

Advanced CS is not a checklist. The advice is to pick one subject, with advanced programming given as the example, and take every course filed under that heading, or to create your own custom subject, in which case the Discord community may offer feedback on the plan. The curriculum's table of contents shows the shape of it: advanced programming, advanced systems, advanced theory, advanced information security, and advanced math. Consequence for the reader: the repository supplies structure and a social review of a plan you write yourself, but it does not say how many courses make a subject finished or where a reasonable stopping point is. A custom subject is checked by peers in chat rather than against a written requirement, which makes that the loosest part of an otherwise prescriptive plan.

Editorial conclusion

Use ossu/computer-science when you want a broad, sequenced grounding and you are willing to enforce the order yourself, because the sequence is the design and nothing in the repository checks that you followed it. Do not use it as a hiring credential: the readme says outright that it is not for career training, and the only assessed step is a final project evaluated by peers rather than graded by anyone. Before you start, verify three things on your own: that the courses you plan to take are still open for enrollment, since the four criteria are a filter applied when a course is written into the list and nobody re-checks it for you; that the prerequisites for Core CS really are met, because the page states Core CS assumes high school math; and that the duration estimate is a starting point rather than a promise, because the readme itself warns the spreadsheet can fall out of date with the curriculum.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository