he4rt/4noobs: a link index of beginner tutorials, not a curriculum
Repositório listando 4noobs de todas as categorias e funcionalidades possíveis.
At a glance
- What is it?
- The repository holds no tutorial code at all. It is a Portuguese-language table of links to community-written beginner guides, split across nine categories, plus the template and cover art a contributor needs to add one.
- Who is it for?
- Adopt he4rt/4noobs if you read Portuguese, are at the start of a language, and want a shortlist of community written guides before you commit to one. Do not adopt it as a learning path, a reference, or a substitute for official documentation: the nine categories are link tables, the rows carry no difficulty ordering and no version numbers, and every guide lives in somebody else repository.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 72 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.
Star history
- he4rt/4noobs4,400 ★ · +13
| Repository | 2026-09-23 | 2026-11-14 |
|---|---|---|
| he4rt/4noobs | 4.4k | 4.4k |
13 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository is a markdown table, not a body of teaching material
Open the repository expecting a curriculum and you will find a single README.MD at the top level, alongside .github/, .gitignore and Templates/. Everything a reader consumes lives inside that one markdown file as a set of tables. Each row has four columns: a language or topic name, a one line description in Portuguese, a list of contributor handles, and a link cell whose text is a clickable arrow pointing at a separate GitHub repository. There is no prose chapter, no exercise and no sample project stored here.
That shape matters for anyone deciding whether to use it. A tutorial table is a directory of someone else's writing. When a row says the C++ guide aims to teach the language in an uncomplicated way, the teaching happens in the linked repository, not here. Reading 4noobs gives you a map of where tutorials live, which for a beginner deciding between C, Go and Python is a real answer, and for someone past the basics it is an index with nothing inside it.
The description of the repository says it centralizes tutorials developed by the community for people starting out in technology. Centralize here means link, not copy. The top-level layout holds no submodule, no vendored directory and no script that fetches the linked repositories, so what you clone is the index alone.
Nine categories, and an index that must be edited by hand when one is added
The README carries a numbered table of contents with nine entries: programming languages, frameworks, automation frameworks, tools, operating systems, design, databases, programming paradigms, and assorted topics. A comment sits directly above that list stating the rule: if another category is added, it has to be placed there as well. So the taxonomy is maintained by editing a markdown anchor list by hand, and the failure mode is a section that exists but cannot be reached from the contents.
The category names carry information too. Frameworks and automation frameworks are separate categories. Operating systems and design sit in the same index as programming languages.
The language table runs from Assembly, described as the language most interesting for reverse engineering, through Bash, C, C++, C#, Clojure, Crystal, CSS, Dart, Elixir, Go, HTML, XML, Java, Javascript, Markdown, OCaml, PHP, Python and R, and also covers making your own programming language. Several rows credit more than one contributor, and CSS credits five handles, so ownership of a row is shared while ownership of the linked repository sits with whoever wrote it.
Contribution runs through CONTRIBUTING.md and a README template
The repository does document how to add a tutorial, in four steps stated in the README. Think of a topic that would have helped you when you were starting. Write it plainly and directly, with practical examples. Follow the guidance in the CONTRIBUTING.md file and use the template that lives in Templates/README.md. Feel free to reuse the headers and cover images carrying the He4rt visual identity from the Templates/capas directory.
So the install path for a contributor is a fork and a pull request against the master branch, not a package manager. Nothing is fetched from a registry and there is no CLI. The README points at the Discord invite as the way to join the community, and the header links to Twitter, Instagram, LinkedIn and a WhatsApp group for the same purpose.
The template matters more than it looks. Because every linked guide is a separate repository with its own history, its own language and its own pace, the template is the only device holding the set together visually. The same template is what makes a link row in the index recognisable as part of one series rather than a random tutorial someone found.
Every link points off site, so quality lives where the index cannot see it
The limit of this project is structural. The index row carries a name, a sentence of description, contributor handles and a URL. It carries no last updated date, no version, no difficulty level and no review status. If a linked tutorial describes an approach that has since been deprecated, the row looks exactly the same as one describing a current practice.
A reader looking at the Clojure row learns that it is an elegant functional language based on Lisp and a partner of the JVM, which is a claim about the language, not a claim about the tutorial. Reading a table of those sentences tells you the community's framing of each topic and very little about whether the code in there still runs.
There is a second gap. The index carries no version of its own. A link that rots is a broken table row, and the only mechanism for repairing it is an ordinary pull request. A link that still resolves says nothing about the age of the tutorial behind it, and the index carries no field in which that age could be recorded.
Markdown gets a row next to Assembly, which tells you how to read the table
Markdown sits in the programming languages table with a description aimed at giving beginners the basics so they can apply them across projects and give a README a better look. That row is a useful calibration for the whole index: the 15 rows above it range from systems work to formatting syntax, and the audience is always someone at the first step. CSS credits five contributor handles, Bash two, C two, so a single row can be maintained by several people at once.
The same shape holds elsewhere. Assembly is framed around reverse engineering. R is framed around data analysis and visualisation. Crystal is introduced as a language for humans and computers with interactions similar to Ruby's. These are orientations rather than syllabi, which is exactly what a link table can carry in a single cell and no more.
Read the index as a map of starting points chosen by working developers, not as a sequence. Nothing in the repository orders the rows by difficulty or by dependency, so the sequence is yours to build. If you need a path that assumes each step follows the last, this table cannot give you one.
How 4noobs differs from official documentation and from paid courses
The difference from official documentation is authorship and language. Official docs for a language are written by the people who build it, updated whenever behaviour changes, and organised so that a reference lookup has a predictable address. A 4noobs row is written by a volunteer, published in Portuguese, and reachable only at a URL that the index does not control.
The difference from a paid course is that there is no sequence, no project and no feedback loop. A structured course decides what you see next and checks whether you understood. 4noobs offers a set of independent guides and leaves the ordering to you, which suits someone who already knows what they want to build and needs one reference in their own language.
Both alternatives win on the axis 4noobs gives up: currency and structure. That trade is worth making for a first hour with an unfamiliar language, and worth reversing once you are past the basics and start depending on behaviour the tutorial does not cover.
Reading the README as a snapshot of one community, in one language
The whole artefact is Portuguese. Descriptions, contribution instructions and the category names are written for Brazilian readers, and the contributor handles and cover art carry a single community's visual identity. For an English speaking developer the tables still parse fine, since a language name is a language name, but the sentences describing each topic need translating and the tutorials themselves will need a machine translation pass.
The index also says what it is for, plainly: people beginning in technology. It does not claim to cover advanced topics, and the category list stays at the level of frameworks, tools and paradigms rather than production operations. That narrowness is a feature. An index that tried to cover everything would be unmaintainable, and this one stays legible by refusing.
The repository is not archived and the last push was on 2026-09-05. Treat that as evidence the index file is still edited, not as evidence that any tutorial behind a link is current, and check the commit history of a linked guide before you plan a project around it.
Editorial conclusion
Adopt he4rt/4noobs if you read Portuguese, are at the start of a language, and want a shortlist of community written guides before you commit to one. Do not adopt it as a learning path, a reference, or a substitute for official documentation: the nine categories are link tables, the rows carry no difficulty ordering and no version numbers, and every guide lives in somebody else repository. Before anything else, open two or three of the linked tutorials and check their commit dates and the language versions they target, because a row that looks current in the index can point at a guide written against an older toolchain. If your language already has good documentation in your own language, skip the index entirely. If you only need one concept explained in Portuguese, the single linked repository is the whole cost, and nothing else in this repository is required. What 4noobs does well is the first five minutes of a decision: more than twenty language rows, each with a named author, saved you from searching for a beginner guide yourself.
Frequently asked questions
What does the he4rt/4noobs repository actually contain?
A README.MD organised as nine tables of links to beginner tutorials written by the community, plus a Templates directory holding a README template and cover images. No tutorial text is stored in the repository itself.
How do I contribute a tutorial to he4rt/4noobs?
Pick a topic that would have helped you when starting out, write it simply with practical examples, then follow CONTRIBUTING.md and use the template in Templates/README.md. You can reuse the headers and covers from Templates/capas.
Which programming languages are covered by he4rt/4noobs?
The language table includes Assembly, Bash, C, C++, C#, Clojure, Crystal, CSS, Dart, Elixir, Go, HTML, XML, Java, Javascript, Markdown, OCaml, PHP, Python and R, plus a guide on creating programming languages.
Is he4rt/4noobs a structured learning path?
No. The rows are independent links to separate repositories, and the README gives no ordering by difficulty or prerequisite. A comment in the index notes that any new category must be added to the table of contents by hand.
What language are the he4rt/4noobs tutorials written in?
Portuguese. Every topic description and the contribution instructions in the README are in Portuguese, and each tutorial lives in its own repository linked from the index tables.
Is he4rt/4noobs still being updated?
The repository is not archived and the index file is still being edited, but it records no date for any individual tutorial it links to.
Official sources
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.
[](https://hysenlabs.com/projects/he4rt-4noobs)Star history chart for your README
[](https://hysenlabs.com/projects/he4rt-4noobs)Was this useful?