mirrors/computer-science
mirrors
/
computer-science
mirror of https://github.com/ossu/computer-science.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
computer-science/README.md

18 KiB
Raw Blame History

Open Source Society University (OSSU)

Open Source Society University

Path to a self-taught education in Computer Science!

Awesome Open Source Society University - Computer Science

Contents

About

This is a solid path for those of you who want to complete a Computer Science course on your own time, at little to no cost, with courses from the best universities in the world.

In our curriculum, we give preference to MOOC (Massive Open Online Course) style courses because these courses were created with our style of learning in mind.

Motivation & Preparation

Here are two interesting links that can make all the difference in your journey.

The first one is a motivational video that shows a guy that went through the "MIT Challenge", which consists of learning the entire 4-year MIT curriculum for Computer Science in 1 year.

The second link is a MOOC that will teach you learning techniques used by experts in art, music, literature, math, science, sports, and many other disciplines. These are fundamental abilities to succeed in our journey.

Are you ready to get started?

Curriculum

Core CS

Core programming

Courses Duration Effort
Introduction to Computer Science - CS50 12 weeks 10-20 hours/week
How to Code: Systematic Program Design (XSeries) 15 weeks 5 hours/week
Object Oriented Programming in Java 6 weeks 4-6 hours/week
Programming Languages, Part A 4 weeks 8-16 hours/week
Programming Languages, Part B 3 weeks 8-16 hours/week
Programming Languages, Part C 3 weeks 8-16 hours/week

Core math

Courses Duration Effort
Calculus One 16 weeks 8-10 hours/week
Calculus Two: Sequences and Series 7 weeks 9-10 hours/week
Introduction to Probability - The Science of Uncertainty 18 weeks 12 hours/week
Discrete Mathematics 11 weeks 3-5 hours/week
Linear Algebra - Foundations to Frontiers 15 weeks 8 hours/week

Core systems

Courses Duration Effort
Build a Modern Computer from First Principles: From Nand to Tetris 6 weeks 7-13 hours/week
Build a Modern Computer from First Principles: Nand to Tetris Part II 6 weeks 12-18 hours/week
Databases 12 weeks 8-12 hours/week
Introduction to Computer Networking - 4–12 hours/week

Core theory

Courses Duration Effort
Divide and Conquer, Sorting and Searching, and Randomized Algorithms 4 weeks 4-8 hours/week
Graph Search, Shortest Paths, and Data Structures 4 weeks 4-8 hours/week
Greedy Algorithms, Minimum Spanning Trees, and Dynamic Programming 4 weeks 4-8 hours/week
Shortest Paths Revisited, NP-Complete Problems and What To Do About Them 4 weeks 4-8 hours/week
Automata Theory 8 weeks 10 hours/week

Core applications

Courses Duration Effort
Machine Learning 11 weeks 4-6 hours/week
Computer Graphics 6 weeks 12 hours/week
Cryptography I 6 weeks 5-7 hours/week

Advanced programming

Courses Duration Effort
Software Testing 4 weeks 6 hours/week
Software Debugging 8 weeks 6 hours/week
Introduction to Parallel Programming 12 weeks -
Software Architecture & Design 8 weeks 6 hours/week

Electives

Courses Duration Effort
Cryptography II 6 weeks 6-8 hours/week
Compilers 9 weeks 6-8 hours/week
Introduction to Natural Language Processing 12 weeks -

Specializations

After finishing the courses above, start your specializations on the topics that you have more interest.

The following platforms currently offer specializations:

edX: xSeries

Coursera: Specializations

Udacity: Nanodegree

FutureLearn: Collections

keep learning

How to use this guide

Order of the classes

This guide was developed to be flexible. Ideally, it can be consumed in a linear approach, i.e. you complete one course at a time, but in reality different people have different preferences with regard to how many courses they wish to take at once, and different courses are available at different times and have wildly different time requirements.

Therefore, many students will take the courses in a non-linear order, based on availability and how much time they have to devote to each class.

Any course that is part of 'Core CS' section should be available either regularly, in self-paced format, or in archived form. Some of the electives are only available once in a while.

How to track and show your progress

  1. Create an account in Trello.
  2. Copy this board to your personal account. See how to copy a board here.

Now that you have a copy of our official board, you just need to pass the cards to the Doing column or Done column as you progress in your study.

We also have labels to help you have more control through the process. The meaning of each of these labels is:

  • Main Curriculum: cards with that label represent courses that are listed in our curriculum.
  • Extra Courses: cards with that label represent courses that was added by the student.
  • Doing: cards with that label represent courses the student is current doing.
  • Done: cards with that label represent courses finished by the student. Those cards should also have the link for at least one project/article built with the knowledge acquired in such course.
  • Section: cards with that label represent the section that we have in our curriculum. Those cards with the Section label are only to help the organization of the Done column. You should put the Course's cards below its respective Section's card.
  • Extra Sections: cards with that label represent sections that was added by the student.

The intention of this board is to provide our students a way to track their progress, and also the ability to show their progress through a public page for friends, family, employers, etc. You can change the status of your board to be public or private.

Should I take all courses?

If you are serious about getting an online education comparable to a bachelor's degree in Computer Science, you should absolutely take all of the courses under the 'Core CS' section.

These courses are equivalent to about 3/4 of a full bachelor's degree in CS. So if you want to really complete your studies, then you should select one of the specializations to finish out your program, such as one in Artificial Intelligence or Big Data.

Duration of the project

If you are able to devote 18-20 hours per week to this curriculum, taking 1-3 clases at a time, you could hypothetically finish the Core CS section in under 2 years. A specialization would then take you a few more months.

It will probably take longer if you go slower, but regardless, your reward will be proportional to your effort.

You must focus on your habit, and forget about goals. Try to invest 1 ~ 2 hours every day studying this curriculum. If you do this, inevitably you'll finish this curriculum.

See more about "Commit to a process, not a goal" here.

Project Based

Here in OSS University, you do not need to take exams, because we are focused on real projects!

In order to show everyone that you successfully finished a course, you should create a real project.

"What does it mean?"

After you finish a course, you should think about a real world problem that you can solve using the acquired knowledge in the course. You don't need to create a big project, but you must create something to validate and consolidate your knowledge, and also to show to the world that you are capable to create something useful with the concepts that you learned.

The projects of all students will be listed in this file. Submit your project's information in that file after you conclude it.

Put the OSSU-CS badge in the README of your repository! Open Source Society University - Computer Science

  • Markdown: [![Open Source Society University - Computer Science](https://img.shields.io/badge/OSSU-computer--science-blue.svg)](https://github.com/open-source-society/computer-science)
  • HTML: <a href="https://github.com/open-source-society/computer-science"><img alt="Open Source Society University - Computer Science" src="https://img.shields.io/badge/OSSU-computer--science-blue.svg"></a>

You can create this project alone or with other students!

Project Suggestions

  • Projects: A list of practical projects that anyone can solve in any programming language.
  • app-specs: A curated list of applications specifications and implementations to practice new technologies, improve your portfolio and sharpen your skills.
  • FreeCodeCamp: Course that teaches you fullstack JavaScript development through a bunch of projects.
  • JavaScript Projects: List of projects related with the JavaScript Path.

And you should also...

Be creative!

This is a crucial part of your journey through all those courses.

You need to have in mind that what you are able to create with the concepts that you learned will be your certificate and this is what really matters!

In order to show that you really learned those things, you need to be creative!

Here are some tips about how you can do that:

  • Articles: create blog posts to synthesize/summarize what you learned.
  • GitHub repository: keep your course's files organized in a GH repository, so in that way other students can use it to study with your annotations.

Cooperative work

We love cooperative work! Use our channels to communicate with other fellows to combine and create new projects!

Which programming languages should I use?

My friend, here is the best part of liberty! You can use any language that you want to complete the

The important thing for each course is to internalize the core concepts and to be able to use them with whatever tool (programming language) that you wish.

Content Policy

You must share only files that you are allowed to! Do NOT disrespect the code of conduct that you signed in the beginning of some courses.

Be creative in order to show your progress! 😄

Stay tuned

Watch this repository for futures improvements and general information.

Prerequisite

The only things that you need to know are how to use Git and GitHub. Here are some resources to learn about them:

Note: Just pick one of the courses below to learn the basics. You will learn a lot more once you get started!

Change Log

Curriculum Version: 6.0

To show respect to all of our students, we will keep a CHANGELOG file that contains all the alterations that our curriculum may suffer.

Now we have a stable version of the curriculum, which won't change anymore, only in exceptional cases (outdated courses, broken links, etc).

Our students can trust in this curriculum because it has been carefully planned and covers all the core topics that a conventional Computer Science course covers.

We also include modern topics, making this course one of the best options for those who want to become a Computer Scientist and/or a Software Engineer/Developer.

How to collaborate

You can open an issue and give us your suggestions as to how we can improve this guide, or what we can do to improve the learning experience.

You can also fork this project and send a pull request to fix any mistakes that you have found.

If you want to suggest a new resource, send a pull request adding such resource to the extras section.

The extras section is a place where all of us will be able to submit interesting additional articles, books, courses and specializations, keeping our curriculum as immutable and concise as possible.

Let's do it together! 😄

Community

Subscribe to /r/opensourcesociety!

Join us in our group!

You can also interact through GitHub issues.

We also have a chat room! Join the chat at https://gitter.im/open-source-society/computer-science

Add Open Source Society University to your Facebook profile!

PS: A forum is an ideal way to interact with other students as we do not lose important discussions, which usually occur in communication via chat apps. Please use our subreddit/group for important discussions.

Team

References