Open-source project
Universidade-Livre/ciencia-da-computacao avatar
Universidade-Livre/ciencia-da-computacao

ciencia-da-computacao: a grid of external courses where most books are not free

🎓 Um caminho para a educação autodidata em Ciência da Computação!

21,041 stars1,692 forksUnknownMIT

At a glance

What is it?
This project teaches nothing itself. It curates free, openly watchable courses from Brazilian universities and institutes, orders them by prerequisite, and moves everything that does not fit into extras. The gap between free to watch and free to finish is where the money and the personal discipline have to come from.
Who is it for?
This guide fits a self-directed student in Brazil who can read Portuguese, who can hold themselves to a sequence over years, and who would rather assemble courses from several institutions than follow one degree program. It does not fit a learner who needs the material itself in one place, who wants accredited credit, or who needs someone checking their work.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 177 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Universidade-Livre/ciencia-da-computacao21,041 ★ · +211
Star history
Repository2026-09-212026-11-14
Universidade-Livre/ciencia-da-computacao20.8k21k

211 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Nothing here teaches computer science, it curates other people's courses

The repository is a curriculum document, not courseware. Courses are selected primarily from open content produced by various Brazilian universities and institutes, and the organized list of disciplines is the entire deliverable. That choice shapes everything a student inherits. The material lives on someone else's platform, at that provider's pace, under that provider's prerequisites and rules, and this project controls only the selection, the ordering, and the admission criteria. There is no fallback copy of any course. Read every entry as a link to an external course rather than as a unit of study material, and plan on the possibility that a course in the middle of the sequence retires or changes its syllabus, because the grid would simply stop pointing at what it pointed at last week.

Free to watch is the filter, and it is not the same as free to finish

Four conditions decide whether a course enters the grid: it must be free or openly watchable, it must have a pedagogical method, it must carry community recognition of quality on the topic, and it must line up with what a computer science curriculum is expected to contain. The cost condition is where readers get surprised. The guide says every course can be completed for free, and in the same breath notes that some of those courses charge for diplomas, certificates, activities, or optional extras. It also states that every discipline has a recommended reading list and that most of those books are not free, while linking to Coursera financial aid as one mitigation. Budget for books and certificates rather than assuming the whole path costs nothing.

Extras is where quality material goes when the grid has no slot

The overflow has an address. Recommended courses of good quality that do not fit the grid are collected in extras/courses.md, and books that do not fit land in extras/books.md. That keeps the main sequence short, but it also means the extras list is where an interest goes when the curriculum has nowhere to put it. If your subject is a specialization, check the specializations/ directory as well. Changes to the grid itself go through the issue tracker and CONTRIBUTING.md.

Prerequisites are the only ordering rule you are actually given

Students may take disciplines individually or in a group, and may follow the established order or not, with one condition: curricular prerequisites must be respected. The statement that everything can be completed for free is about access to course material, not about a certificate you leave with. So the burden of sequencing is entirely on the reader. A topic taken out of order does not announce itself at the moment you skip it, and the cost appears much later as a hole in a subject whose earlier step was never done, which makes that prerequisite sentence the one line in this document worth reading twice.

Study habits are treated as prerequisites too, and can be skipped

Before the sequence, the guide has a section on study techniques, organization, and learning, recommending material on memory and study techniques, including a learning-to-learn course. It frames self-direction carefully: being self-taught is not about being alone and not about having no link to an institution, it is about taking responsibility for your own education, which requires knowing how to study, how much to study, and how to organize it. Those topics are marked as useful rather than essential, and a reader is invited to skip them at the start and return later. The framing is consistent with the rest of the plan: nothing is enforced, so the habits have to be self-imposed too.

Guidelines were consulted, and the text admits they were not fully implemented

The curriculum was built against external references, and it names them. The listed basis is the SBC's 2017 Referenciais de Formação for undergraduate computing courses and the UFRGS curricular guidelines for computing and informatics, together with the curricular grids of other Brazilian higher education institutions. The wording is explicit that these were taken into account without being implemented completely as suggested, and that suggestions for improvement are still accepted. Read that as a scope statement rather than a footnote. This is not an accredited program and does not claim equivalence with a degree, so anyone who needs formal credit has to check the relevant referential directly and translate this grid themselves.

Support is a Telegram server and an issue tracker, not a mentor

The named channels are a Telegram server for students, GitHub issues for problems with the course and for proposing curriculum changes, and social accounts for the project. The detail lives in files at the top level: HELP.md for the FAQ and the server, CONTRIBUTING.md for how to help, CODE_OF_CONDUCT.md, FAQ.md, and an .all-contributorsrc. Issues being the place where curriculum changes are proposed has a practical benefit, since you can read the arguments before making your own. The channels named are community ones, so they reduce the isolation of self-study rather than supply the guidance a structured program would.

Portuguese is the boundary, and there is no version to pin

Language is a hard filter. The stated aim is a complete computer science education using online material in Brazilian Portuguese, which is what makes the plan usable for readers in Brazil and largely unusable for an English-only learner. The header points at the sindresorhus/awesome list and at the ossu computer-science guide. On versioning, there are no releases at all, and the branch received its last push on 2026-05-20 under an MIT license whose copyright reads 2021 Universidade Brasileira Livre. Corrections and additions therefore land in the same Markdown file with no tag, so keep a copy of the grid you started from.

Editorial conclusion

This guide fits a self-directed student in Brazil who can read Portuguese, who can hold themselves to a sequence over years, and who would rather assemble courses from several institutions than follow one degree program. It does not fit a learner who needs the material itself in one place, who wants accredited credit, or who needs someone checking their work. Before enrolling, read the four admission criteria for courses and accept that they exclude material you might have wanted, confirm you can afford the books and any paid certificate or optional extra, and look at the extras and specializations folders to see whether your interest has a slot or not. The MIT license carries a 2021 copyright from Universidade Brasileira Livre, there are no releases to pin, and the last push on the branch was on 2026-05-20, so keep your own copy of the grid you start from.

Frequently asked questions

What does the ciencia-da-computacao curriculum actually cover?

It collects the contents that would be seen in a computer science course, arranged in a structured grid, and built on the fundamental concepts of computing rather than on training for specific technologies or market-facing job skills. The courses themselves come from open content at Brazilian universities and institutes.

Is the IT course path in ciencia-da-computacao hard?

On who the plan suits, the README states that it targets students with discipline, commitment and good study habits, mostly independent but supported by a community of students across Brazil, and that curricular prerequisites must be respected even when the order is followed loosely.

Does ciencia-da-computacao list 10 IT professions?

The plan explicitly says it is not designed as training for specific technologies or for professional skills aimed at the market. It positions itself as a self-directed education founded on fundamental computing concepts, with extra material held in extras/ and specializations/.

Does Universidade-Livre cover the three types of IT?

The README organizes the plan around computer science courses rather than types of IT. Its admission criteria for a course are that it be free or openly watchable, have a pedagogical method, have community recognition of quality on the subject, and match what a computer science curriculum is expected to contain.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Universidade-Livre/ciencia-da-computacao on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/universidade-livre-ciencia-da-computacao.svg)](https://hysenlabs.com/projects/universidade-livre-ciencia-da-computacao)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/universidade-livre-ciencia-da-computacao.svg)](https://hysenlabs.com/projects/universidade-livre-ciencia-da-computacao)

Was this useful?