Every Programmer Should Know: A Curated Link List With an Opinionated Edge
GitHub describes it as A collection of (mostly) technical things every software developer should know about. The metadata lists the CC-BY-4.0 license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- This GitHub repository is a hand-picked collection of links, books, and courses covering computer science fundamentals. It is not a tutorial or a textbook, but a starting point for developers who want a broad, human-curated map of what to learn next.
- Who is it for?
- Adopt this repository if you are a self-directed developer who wants a broad, opinionated reading list without the noise of automated aggregators. Skip it if you need structured lessons, code examples, or a maintained curriculum, because the repository is a static list with no built-in progress tracking and its last push was on 2025-12-29.
- Can I use it commercially?
- Yes, with credit. CC-BY-4.0 allows commercial use as long as you credit the authors and indicate what you changed. It is written for creative content, so check how it applies to any code.
- Is it still maintained?
- Activity is slowing. The repository last received commits 10 months 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 15, 2026, and from our analysis. They are not legal advice.
Star history
- mtdvio/every-programmer-should-know100,669 ★ · +420
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| mtdvio/every-programmer-should-know | 100.2k | 100.7k |
420 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What This Repository Actually Is
The repository mtdvio/every-programmer-should-know is a single README file that acts as a curated list of links. It is not a book, a course, or a tool. The README describes it as "a collection of (mostly) technical things every software developer should know." The author is explicit about its nature: it is "highly opinionated" and "not backed by science." The list covers topics like algorithms, data structures, numbers, strings, latency, time, memory, distributed systems, machine learning, regular expressions, security, and UX. Each topic has a handful of links to external resources, including books, videos, courses, and articles. For a developer looking for a starting point, this repository serves as a map, not a destination.
The Mechanism: A Hand-Curated Index With No Automation
The repository has no code, no build system, and no package. It is a Markdown file with sections and bullet points. The mechanism is simple: the author selects resources and organizes them by topic. The README includes a note that contributions are welcome, pointing to a CONTRIBUTING.md file. There is no search function, no tagging, and no filtering. The order of topics is arbitrary, as the author states it "comes in no particular order." This is a deliberate choice. The value is in the curation itself, the author's judgment about what is worth reading. The lack of automation means the list is static, which is both a strength and a weakness, as discussed later.
Getting Started: No Installation, Just a Browser
There is nothing to install or configure. To use this repository, you clone it or simply view the README on GitHub. The links are external, so you need an internet connection. The README includes a link to a quiz at mylevel.dev, created by the same author, which claims to measure your developer level against a cross-industry benchmark in 10 minutes. That quiz is separate from the repository. For a practical start, open the README, pick a topic you are weak in, and click a link. For example, under "Algorithms," there is a Big O Cheatsheet and a link to Grokking Algorithms. There is no recommended order, so you have to decide for yourself. The repository does not track progress, so you might want to keep your own notes.
What It Covers Well and What It Misses
The repository covers core computer science topics that many working developers never formally studied. The "Falsehoods" section, linking to Awesome Falsehoods, is a standout because it addresses common assumptions about strings, addresses, names, and timezones. The "Distributed Systems" section includes classic papers like Lamport's "Time, Clocks and the Ordering of Events" and Jepsen analyses, which are essential for anyone working with distributed databases. However, the coverage is uneven. Machine Learning has a single link to Andrew Ng's Coursera specialization. The repository is not a comprehensive curriculum; it is a personal selection. The author admits it is opinionated, so expect gaps.
The Limitations: Staleness and Link Rot
The repository's biggest weakness is that it is static. The last push was on 2025-12-29, and the repository has no GitHub releases. External links can break over time. For example, the video "Map of Computer Science" on YouTube might be removed, and the EDX course might change its URL. As a result, some resources may become outdated or inaccessible. If you rely on this list for learning, you may encounter dead ends. The repository is also not a substitute for hands-on practice. It points to books and videos, but it does not include exercises or projects. For a developer who learns by doing, this list is only a complement.
Alternatives: Roadmaps and Curated Lists With a Different Approach
A direct alternative is the developer-roadmap repository by kamranahmedse, which is linked in the README under "Introduction." That repository provides visual roadmaps for becoming a frontend, backend, or DevOps engineer, with a structured path and skill trees. Unlike every-programmer-should-know, which is a flat list of topics, developer-roadmap organizes learning into a sequential order with dependencies. Another alternative is the Awesome Falsehoods list, which is a specialized collection of falsehoods, whereas this repository covers many topics. If you want a broader but more structured approach, the Computer Science Roadmap at roadmap.sh is also linked. The key difference is that these alternatives offer a path, while every-programmer-should-know offers a menu.
Licence and Contribution: CC-BY-4.0 and an Open Invitation
The repository is licensed under CC-BY-4.0, which means you can share and adapt the content as long as you give credit. This is a permissive licence for a collection of links, but it does not apply to the external resources themselves. Each linked book, video, or article has its own licence. The README encourages contributions, with a CONTRIBUTING.md file. If you want to add a resource, you should read that file first. The maintenance cost is low for a user, but for a contributor, the cost is in keeping links current and relevant. If you fork it, you take on that responsibility.
Editorial conclusion
Adopt this repository if you are a self-directed developer who wants a broad, opinionated reading list without the noise of automated aggregators. Skip it if you need structured lessons, code examples, or a maintained curriculum, because the repository is a static list with no built-in progress tracking and its last push was on 2025-12-29. Before relying on it, verify that the external links still work, especially the YouTube videos and course pages, and check the CONTRIBUTING.md if you plan to add resources. The repository's value is as a curated index, not as a definitive source, so treat each link as a lead to investigate further.
Frequently asked questions
What is every-programmer-should-know about?
It is a collection of mostly technical things every software developer should know, offered as resources the author can recommend regardless of skill level or tech stack. The entries are grouped under headings from Algorithms and Strings through Latency, Memory, Distributed Systems and Security, and the file says they come in no particular order.
What does the every-programmer-should-know repository actually contain?
Four entries at the top level: a .github directory, CONTRIBUTING.md, LICENSE and README.md. The README is the whole project, a categorised list of links to other people's material, and the file states that it is highly opinionated and not backed by science.
Is the every-programmer-should-know list still being updated?
The last commit to the master branch landed on 2025-12-29, the project is not archived, and it publishes no GitHub releases. Since no code lives here, no build or test would tell you when one of the linked pages has moved.
Does every-programmer-should-know tell me what order to learn things in?
No, and the file is upfront about it. The entries come in no particular order, and a note at the top says you do not need to know all of it by heart to be a programmer. Contributions are invited through CONTRIBUTING.md.
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/mtdvio-every-programmer-should-know)Star history chart for your README
[](https://hysenlabs.com/projects/mtdvio-every-programmer-should-know)Was this useful?