charlax/professional-programming: A Curated Map of Engineering Knowledge, Not a Codebase
A collection of learning resources for curious software engineers
At a glance
- What is it?
- This is a GitHub repository that collects learning resources for software engineers, organized by topic. It is not software you run, but a reference list with a specific editorial point of view.
- Who is it for?
- Adopt this repository if you are a curious engineer who wants a structured, opinionated reading list to fill gaps in your knowledge, especially if you value a single maintainer's curated picks over a community-driven wiki. Do not adopt it if you expect an interactive tool, a searchable database, or a maintained codebase, because it is a curated reading list with no releases.
- 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 19 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
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
- charlax/professional-programming51,678 ★ · +248
| Repository | 2026-08-18 | 2026-11-14 |
|---|---|---|
| charlax/professional-programming | 51.4k | 51.7k |
248 Stars in the last 88 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What This Repository Actually Is
Despite being listed as a Python project, charlax/professional-programming contains no application code. It is centred on an extensive Markdown README that acts as a curated index of learning resources for software engineers, alongside directories such as antipatterns/, cheatsheets/, list-of-links/ and training/. The README opens with a quote from Abraham Lincoln about sharpening the axe, which sets the tone: this is about deliberate preparation, not quick fixes. The repository describes itself as a collection of learning resources for curious software engineers. The primary language field says Python, but that likely refers to some auxiliary script, not the content itself. For practical purposes, this is a document, not a program.
The Topic Taxonomy Is the Real Product
The README's table of contents is the core feature. It lists more than 100 topics, from Accounting to Writing, with nested subcategories. For example, under Databases you get Internals, NoSQL, and Postgres. Under Releasing & deploying you get Versioning, Checklists, Feature flags, and Testing in production. This structure is not random. It reflects a mental model of what a professional engineer should know, one that goes far beyond coding syntax. The presence of topics like Accounting, Business, and Buy vs. Build suggests the maintainer believes engineers need commercial awareness. The inclusion of Chess and Humor shows a lighter side, but most topics are serious and technical. This taxonomy is the repository's main value, because it helps you discover what you do not know you do not know.
How the Content Is Organized and What It Includes
The README is divided into major sections. The first is 'Principles', which likely contains the maintainer's core beliefs about software development. Then come 'Must-read books' and 'Must-read articles', which are probably the highest-priority recommendations. After that, 'Other general material and list of resources' collects additional lists, books, articles, axioms, and courses. The bulk of the document is the 'Topics' section, where each topic has its own list of links. The README also includes sections for presentation resources, keeping up-to-date, and concepts. The structure suggests a deliberate progression: start with principles, read the must-reads, then dive into specific topics as needed. The inclusion of 'Other lists' indicates the maintainer is not trying to be exhaustive but rather to point you to other good sources.
How You Get It Running (or Not)
There is no installation or setup. You do not run this repository. You clone it or view it on GitHub. The default branch is 'master', and the repository is not archived, and the last push was on 2026-10-27. To use it, you simply open the README.md file. You can browse it on the GitHub web interface, or clone it locally with 'git clone https://github.com/charlax/professional-programming.git'. If you clone it, you can search the text with grep, or use a tool like ripgrep to find topics. The README's table of contents is generated with doctoc, as indicated by the comments at the top. This means the structure is maintained programmatically, but the content itself is manually curated.
Maintenance and Upgrade Cost
The repository has no releases, which is typical for a documentation-only project. The last push was on 2026-10-27, so it is still being updated. The README itself is a static file, so there is no upgrade cost in the traditional sense. However, the cost is in link rot. Over time, external links may break, and without regular maintenance, the resource list becomes stale. The MIT license means you can fork it and maintain your own version if you wish, but that is a significant effort. The license also means you can reuse the content, but it does not guarantee that the linked resources themselves are freely available. You should check each link before relying on it, especially for time-sensitive topics like Generative AI or Kubernetes.
Limitations: When This Repository Is the Wrong Tool
The biggest limitation is that it is a list, not a learning platform. There are no interactive elements and no way to track your progress. You cannot search the repository as a database, and there is no API. The curation is subjective, based on one person's experience. What works for that person may not work for you. If you want a guided curriculum, this is not it.
Alternatives and How They Differ
A direct alternative is the 'Awesome' list ecosystem, such as 'awesome-sysadmin' or 'awesome-selfhosted'. Those lists are also curated Markdown files, but they are often community-driven, with many contributors, and they focus on specific domains. The difference is that professional-programming is a single maintainer's broad view of the entire profession, while Awesome lists are usually narrower and more frequently updated. Another alternative is a structured learning platform like Exercism or freeCodeCamp, which offer interactive exercises and a curriculum. Those are actual applications, not static lists. The key difference is that professional-programming gives you a map, while platforms give you a path. The map is useful if you know how to navigate, but a path may be better for beginners.
Who Should Use It and What to Verify First
This repository is for engineers who want to broaden their knowledge beyond their daily work. It is especially useful for those who are curious about topics outside their immediate specialty, like a backend engineer wanting to learn about typography or accounting. It is also useful for mentors who want to recommend resources to juniors. Before you rely on it, verify the freshness of the links, especially in fast-moving areas like AI and cloud. Check the last commit date on GitHub to see if the maintainer is still active. Also, consider whether you prefer a curated list or a community-driven one. If you want a single person's opinionated picks, this is it. If you want a living, collaborative resource, look elsewhere.
Editorial conclusion
Adopt this repository if you are a curious engineer who wants a structured, opinionated reading list to fill gaps in your knowledge, especially if you value a single maintainer's curated picks over a community-driven wiki. Do not adopt it if you expect an interactive tool, a searchable database, or a maintained codebase, because it is a curated reading list with no releases. Before relying on it, verify that the links you plan to use are still alive, since external links can break over time. The repository's real value is its topic taxonomy, which you can mine for your own study plan, but you must treat it as a snapshot, not a living service.
Frequently asked questions
what is professional programming
In this repository, professional programming is a curated reading list, described as a collection of full-stack resources for programmers. It is organised into sections for Principles, Must-read books, Must-read articles, other general material, the Topics section, presentation resources, keeping up to date, Concepts, and the author's other lists.
According to Professional Programming, do coders make a lot of money?
The table of contents has no heading on pay. It does carry a Career growth heading with two subtopics, Choosing your next/first opportunity and Getting to Staff Eng, alongside headings for Business, Accounting, Marketing, and Product management for software engineers.
According to Professional Programming, what's harder, C++ or Python?
The table of contents has no ranking of languages by difficulty. The relevant headings are Programming languages, which carries Python and JavaScript as subtopics along with Garbage collection, plus Programming paradigm, Functional programming (FP), Low-level, assembly, Compilers, and Type system.
According to Professional Programming, is programming still worth it in 2026?
The table of contents has no section on the labour market or on any particular year. What it offers on the human side is Attitude, habits, mindset with a Procrastination subtopic, Work ethics, productivity and work/life balance, Learning and memorizing, and Career growth.
According to Professional Programming, is coding a dead-end job?
Its table of contents has no section on that question; it is a list of resources rather than an argument. For career shaped material it points to Choosing your next/first opportunity, Getting to Staff Eng, Interviewing, Public speaking, and Personal productivity.
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/charlax-professional-programming)Star history chart for your README
[](https://hysenlabs.com/projects/charlax-professional-programming)Was this useful?